diff --git a/plugins/backstage-plugin-coder/docs/README.md b/plugins/backstage-plugin-coder/docs/README.md
index 1aac4a05..95019233 100644
--- a/plugins/backstage-plugin-coder/docs/README.md
+++ b/plugins/backstage-plugin-coder/docs/README.md
@@ -1,11 +1,22 @@
-# Plugin API Reference – Coder for Backstage
+# Documentation Directory – `backstage-plugin-coder` v0.3.0
-For users who need more information about how to extend and modify the Coder plugin. For general setup, please see our main [README](../README.md).
+This document lists core information for the Backstage Coder plugin. It is intended for users who have already set up the plugin and are looking to take it further.
-All documentation reflects version `v0.2.0` of the plugin. Note that breaking API changes may continue to happen for minor versions until the plugin reaches version `v1.0.0`.
+For general setup, please see our [main README](../README.md).
-## Documentation directory
+## Documentation listing
-- [Components](./components.md)
-- [Custom React hooks](./hooks.md)
-- [Important types](./types.md)
+### Guides
+
+- [Using the Coder API from Backstage](./guides/coder-api.md)
+ - [Advanced use cases for the Coder API](./guides//coder-api-advanced.md)
+
+### API reference
+
+- [Components](./api-reference/components.md)
+- [Custom React hooks](./api-reference/hooks.md)
+- [Important types](./api-reference/types.md)
+
+## Notes about semantic versioning
+
+We fully intend to follow semantic versioning with the Coder plugin for Backstage. Expect some pain points as we figure out the right abstractions needed to hit version 1, but we will try to minimize breaking changes as much as possible as the library gets ironed out.
diff --git a/plugins/backstage-plugin-coder/docs/catalog-info.md b/plugins/backstage-plugin-coder/docs/api-reference/catalog-info.md
similarity index 100%
rename from plugins/backstage-plugin-coder/docs/catalog-info.md
rename to plugins/backstage-plugin-coder/docs/api-reference/catalog-info.md
diff --git a/plugins/backstage-plugin-coder/docs/components.md b/plugins/backstage-plugin-coder/docs/api-reference/components.md
similarity index 100%
rename from plugins/backstage-plugin-coder/docs/components.md
rename to plugins/backstage-plugin-coder/docs/api-reference/components.md
diff --git a/plugins/backstage-plugin-coder/docs/hooks.md b/plugins/backstage-plugin-coder/docs/api-reference/hooks.md
similarity index 100%
rename from plugins/backstage-plugin-coder/docs/hooks.md
rename to plugins/backstage-plugin-coder/docs/api-reference/hooks.md
diff --git a/plugins/backstage-plugin-coder/docs/types.md b/plugins/backstage-plugin-coder/docs/api-reference/types.md
similarity index 100%
rename from plugins/backstage-plugin-coder/docs/types.md
rename to plugins/backstage-plugin-coder/docs/api-reference/types.md
diff --git a/plugins/backstage-plugin-coder/docs/guides/coder-api-advanced.md b/plugins/backstage-plugin-coder/docs/guides/coder-api-advanced.md
new file mode 100644
index 00000000..fb90ebe6
--- /dev/null
+++ b/plugins/backstage-plugin-coder/docs/guides/coder-api-advanced.md
@@ -0,0 +1,72 @@
+# Working with the Coder API - advanced use cases
+
+This guide covers some more use cases that you can leverage for more advanced configuration of the Coder API from within Backstage.
+
+## Changing fallback auth component behavior
+
+By default, `CoderProvider` is configured to display a fallback auth UI component when two cases are true:
+
+1. The user is not authenticated
+2. There are no official Coder components are being rendered to the screen.
+
+
+
+All official Coder plugin components are configured to let the user add auth information if the user isn't already authenticated, so the fallback component only displays when there would be no other way to add the information.
+
+However, depending on your use cases, `CoderProvider` can be configured to change how it displays the fallback, based on the value of the `fallbackAuthUiMode` prop.
+
+```tsx
+
+
+
+```
+
+There are three values that can be set for the mode:
+
+- `restrained` (default) - The auth fallback will only display if the user is not authenticated, and there would be no other way for the user to add their auth info.
+- `assertive` - The auth fallback will always display when the user is not authenticated, regardless of what Coder component are on-screen. But the fallback will **not** appear if the user is authenticated.
+- `hidden` - The auth fallback will never appear under any circumstances. Useful if you want to create entirely custom components and don't mind wiring your auth logic manually via `useCoderAuth`.
+
+## Connecting a custom query client to the Coder plugin
+
+By default, the Coder plugin uses and manages its own query client. This works perfectly well if you aren't using React Query for any other purposes, but if you are using it throughout your Backstage deployment, it can cause issues around redundant state (e.g., not all cached data being vacated when the user logs out).
+
+To prevent this, you will need to do two things:
+
+1. Pass in your custom React Query query client into the `CoderProvider` component
+2. "Group" your queries with the Coder query key prefix
+
+```tsx
+const yourCustomQueryClient = new QueryClient();
+
+
+
+;
+
+// Ensure that all queries have the correct query key prefix
+import { useQuery } from '@tanstack/react-react-query';
+import {
+ CODER_QUERY_KEY_PREFIX,
+ useCoderQuery,
+} from '@coder/backstage-plugin-coder';
+
+function CustomComponent() {
+ const query1 = useQuery({
+ queryKey: [CODER_QUERY_KEY_PREFIX, 'workspaces'],
+ queryFn: () => {
+ // Get workspaces here
+ },
+ });
+
+ // useCoderQuery automatically prefixes all query keys with
+ // CODER_QUERY_KEY_PREFIX if it's not already the first value of the array
+ const query2 = useCoderQuery({
+ queryKey: ['workspaces'],
+ queryFn: () => {
+ // Get workspaces here
+ },
+ });
+
+ return
Main component content
;
+}
+```
diff --git a/plugins/backstage-plugin-coder/docs/guides/coder-api.md b/plugins/backstage-plugin-coder/docs/guides/coder-api.md
new file mode 100644
index 00000000..04e8d10d
--- /dev/null
+++ b/plugins/backstage-plugin-coder/docs/guides/coder-api.md
@@ -0,0 +1,262 @@
+# Coder API - Quick-start guide
+
+## Overview
+
+The Coder plugin makes it easy to bring the entire Coder API into your Backstage deployment. This guide covers how to get it set up so that you can start accessing Coder from Backstage.
+
+Note: this covers the main expected use cases with the plugin. For more information and options on customizing your Backstage deployment further, see our [Advanced API guide](./coder-api-advanced.md).
+
+### Before you begin
+
+Please ensure that you have the Coder plugin fully installed before proceeding. You can find instructions for getting up and running in [our main README](../../README.md).
+
+### Important hooks for using the Coder API
+
+The Coder plugin exposes three (soon to be four) main hooks for accessing Coder plugin state and making queries/mutations
+
+- `useCoderAuth` - Provides methods and state values for interacting with your current Coder auth session from within Backstage.
+
+ ```tsx
+ function SessionTokenInputForm() {
+ const [sessionTokenDraft, setSessionTokenDraft] = useState('');
+ const coderAuth = useCoderAuth();
+
+ const onSubmit = (event: FormEvent) => {
+ coderAuth.registerNewToken(sessionToken);
+ setSessionTokenDraft('');
+ };
+
+ return (
+
+ );
+ }
+ ```
+
+- `useCoderQuery` - Makes it simple to query data from the Coder API and share it throughout your application.
+
+ ```tsx
+ function WorkspacesList() {
+ // Return type matches the return type of React Query's useQuerys
+ const workspacesQuery = useCoderQuery({
+ queryKey: ['workspaces'],
+ queryFn: ({ coderApi }) => coderApi.getWorkspaces({ limit: 5 }),
+ });
+ }
+ ```
+
+- `useCoderMutation` (coming soon) - Makes it simple to mutate data via the Coder API.
+- `useCoderApi` - Exposes an object with all available Coder API methods. None of the state in this object is tied to React render logic - it can be treated as a "function bucket". Once `useCoderMutation` is available, the main value of this hook will be as an escape hatch in the rare situations where `useCoderQuery` and `useCoderMutation` don't meet your needs. Under the hood, both `useCoderQuery` and `useCoderMutation` receive their `coderApi` context value from this hook.
+
+ ```tsx
+ function HealthCheckComponent() {
+ const coderApi = useCoderApi();
+
+ const processWorkspaces = async () => {
+ const workspacesResponse = await coderApi.getWorkspaces({
+ limit: 10,
+ });
+
+ processHealthChecks(workspacesResponse.workspaces);
+ };
+ }
+ ```
+
+Internally, the Coder plugin uses [React Query/TanStack Query v4](https://tanstack.com/query/v4/docs/framework/react/overview). In fact, `useCoderQuery` and `useCoderMutation` are simply wrappers over `useQuery` and `useMutation`. Both simplify the process of wiring up the hooks' various properties to the Coder auth, while exposing a more convenient way of accessing the Coder API object.
+
+If you ever need to coordinate queries and mutations, you can use `useQueryClient` from React Query - no custom plugin-specific hook needed.
+
+The bottom of this document has examples of both queries and mutations.
+
+### Grouping queries with the Coder query key prefix
+
+The plugin exposes a `CODER_QUERY_KEY_PREFIX` constant that you can use to group all Coder queries. `useCoderQuery` automatically injects this value into all its `queryKey` arrays. However, if you need to escape out with `useQuery`, you can import the constant and manually include it as the first value of your query key.
+
+In addition, all official Coder plugin components use this prefix internally.
+
+```tsx
+// All grouped queries can be invalidated at once from the query client
+const queryClient = useQueryClient();
+const invalidateAllCoderQueries = () => {
+ queryClient.invalidateQuery({
+ queryKey: [CODER_QUERY_KEY_PREFIX],
+ });
+};
+
+// The prefix is only needed when NOT using useCoderQuery
+const customQuery = useQuery({
+ queryKey: [CODER_QUERY_KEY_PREFIX, 'workspaces'],
+ queryFn: () => {
+ // Your custom API logic
+ },
+});
+
+// When the user unlinks their session token, all queries grouped under
+// CODER_QUERY_KEY_PREFIX are vacated from the active query cache
+function LogOutButton() {
+ const { unlinkToken } = useCoderAuth();
+
+ return (
+
+ );
+}
+```
+
+## Recommendations for accessing the API
+
+1. If querying data, prefer `useCoderQuery`. It automatically wires up all auth logic to React Query (which includes pausing queries if the user is not authenticated). It also lets you access the Coder API via its query function. `useQuery` works as an escape hatch if `useCoderQuery` doesn't meet your needs, but it requires more work to wire up correctly.
+2. If mutating data, you will need to call `useMutation`, `useQueryClient`, and `useCoderApi` in tandem\*.
+
+We highly recommend **not** fetching with `useState` + `useEffect`, or with `useAsync`. Both face performance issues when trying to share state. See [ui.dev](https://www.ui.dev/)'s wonderful [_The Story of React Query_ video](https://www.youtube.com/watch?v=OrliU0e09io) for more info on some of the problems they face.
+
+\* `useCoderMutation` can be used instead of all three once that hook is available.
+
+### Comparing query caching strategies
+
+| | `useAsync` | `useQuery` | `useCoderQuery` |
+| ------------------------------------------------------------------ | ---------- | ---------- | --------------- |
+| Automatically handles race conditions | ✅ | ✅ | ✅ |
+| Can retain state after component unmounts | 🚫 | ✅ | ✅ |
+| Easy, on-command query invalidation | 🚫 | ✅ | ✅ |
+| Automatic retry logic when a query fails | 🚫 | ✅ | ✅ |
+| Less need to fight dependency arrays | 🚫 | ✅ | ✅ |
+| Easy to share state for sibling components | 🚫 | ✅ | ✅ |
+| Pre-wired to Coder auth logic | 🚫 | 🚫 | ✅ |
+| Can consume Coder API directly from query function | 🚫 | 🚫 | ✅ |
+| Automatically groups Coder-related queries by prefixing query keys | 🚫 | 🚫 | ✅ |
+
+## Authentication
+
+All API calls to **any** of the Coder API functions will fail if you have not authenticated yet. Authentication can be handled via any of the official Coder components that can be imported via the plugin. However, if there are no Coder components on the screen, the `CoderProvider` component will automatically\* inject a fallback auth button for letting the user add their auth info.
+
+https://github.com/coder/backstage-plugins/assets/28937484/0ece4410-36fc-4b32-9223-66f35953eeab
+
+Once the user has been authenticated, all Coder API functions will become available. When the user unlinks their auth token (effectively logging out), all cached queries that start with `CODER_QUERY_KEY_PREFIX` will automatically be vacated.
+
+\* This behavior can be disabled. Please see our [advanced API guide](./coder-api-advanced.md) for more information.
+
+## Component examples
+
+Here are some full code examples showcasing patterns you can bring into your own codebase.
+
+Note: To keep the examples simple, none of them contain any CSS styling or MUI components.
+
+### Displaying recent audit logs
+
+```tsx
+import React from 'react';
+import { useCoderQuery } from '@coder/backstage-plugin-coder';
+
+function RecentAuditLogsList() {
+ const auditLogsQuery = useCoderQuery({
+ queryKey: ['audits', 'logs'],
+ queryFn: ({ coderApi }) => coderApi.getAuditLogs({ limit: 10 }),
+ });
+
+ return (
+ <>
+ {auditLogsQuery.isLoading &&
Loading…
}
+ {auditLogsQuery.error instanceof Error && (
+
Encountered the following error: {auditLogsQuery.error.message}
+
+All official Coder plugin components are configured to let the user add auth information if the user isn't already authenticated, so the fallback component only displays when there would be no other way to add the information.
+
+However, depending on your use cases, `CoderProvider` can be configured to change how it displays the fallback, based on the value of the `fallbackAuthUiMode` prop.
+
+```tsx
+