Remove versioning for community doc

.agent/skills/docs/new-page.md

@@ -72,13 +72,13 @@ Grounded in the Diátaxis framework and comparable identity platforms (Auth0, Cl
 - **Match placement to what the reader is doing at that moment**, not just shared keywords — a reader debugging a token issue and one learning what tokens are may belong in different sections on the same subject.
 
 ### Step 1: Read the sidebar
-Read `docs/sidebars.ts` in full; for `docs/content/sdks/<sdk>/` pages, also read `docs/content/sdks/<sdk>/sidebar.ts`.
+Read `docs/sidebars.ts` in full; for `docs/content/sdks/<sdk>/` pages, also read `docs/content/sdks/<sdk>/sidebar.ts`; for `docs/community/` pages, read `docs/sidebarsCommunity.ts` instead.
 
 ### Step 2: Determine the target sidebar file
 | File path prefix | Edit this file |
 |---|---|
 | `docs/content/sdks/<sdk>/` | `docs/content/sdks/<sdk>/sidebar.ts` |
-| `docs/content/community/` | `docs/sidebars.ts` → `communitySidebar` |
+| `docs/community/` (unversioned) | `docs/sidebarsCommunity.ts` → `communitySidebar` |
 | Everything else | `docs/sidebars.ts` → `docsSidebar` |
 
 ### Step 3: Determine the target section

CONTRIBUTING.md

@@ -1 +1 @@
-Please refer to the [Contributing Guide](https://thunderid.dev/docs/next/community/overview) for guidelines on how to contribute to this project.
+Please refer to the [Contributing Guide](https://thunderid.dev/community/overview) for guidelines on how to contribute to this project.

README.md

@@ -76,9 +76,9 @@ Visit [Get ThunderID](https://thunderid.dev/docs/next/getting-started/get-thunde
 
 ## Contributing
 
-Please refer to the [Contributing Guide](https://thunderid.dev/docs/next/community/overview) for the different ways to contribute to this project and the relevant guidelines.
+Please refer to the [Contributing Guide](https://thunderid.dev/community/overview) for the different ways to contribute to this project and the relevant guidelines.
 
-For code contributions, refer to the [Contributing Code](https://thunderid.dev/docs/next/community/contributing/contributing-code/prerequisites) section for details on the prerequisites and instructions for running ThunderID in development mode.
+For code contributions, refer to the [Contributing Code](https://thunderid.dev/community/contributing/contributing-code/prerequisites) section for details on the prerequisites and instructions for running ThunderID in development mode.
 
 
 ## License

backend/AGENTS.md

@@ -2,7 +2,7 @@
 
 Read with the root [AGENTS.md](../AGENTS.md). The backend is a Go application under `backend/` (module `github.com/thunder-id/thunderid`): domain packages under `backend/internal/`, entry points under `backend/cmd/`, public packages under `backend/pkg/`.
 
-For the canonical, deeper reference (flat package/file layout, export rules, logging), see the [Backend Development overview](../docs/content/community/contributing/contributing-code/backend-development/overview.mdx).
+For the canonical, deeper reference (flat package/file layout, export rules, logging), see the [Backend Development overview](../docs/community/contributing/contributing-code/backend-development/overview.mdx).
 
 ## When to Load Other Guides
 

docs-internals/readme.md

@@ -5,7 +5,7 @@ specification and the threat model for each feature area. These documents are wr
 development starts and reviewed on their own, separate from the implementation.
 
 **The workflow lives in the contributor guide:
-[Propose a Design](https://thunderid.dev/docs/next/community/contributing/propose-a-design).** Read
+[Propose a Design](https://thunderid.dev/community/contributing/propose-a-design).** Read
 it first. It covers when the two documents are required, how the design discussion comes before them,
 how the pull request is reviewed, and what happens after it is merged.
 

docs/AGENTS.md

@@ -5,7 +5,7 @@ description: AI agents should use this file when creating and reviewing document
 
 # ThunderID Documentation — Agent Instructions
 
-Documentation content under `docs/content/` is handled by one skill, `docs` (`.agent/skills/docs/SKILL.md`), covering every stage: scaffolding, writing, and review. **Invoke it instead of creating, editing, or reviewing a doc page by hand** — it enforces the project's writing standards directly, so the rules live in one executable place, not duplicated in prose here. This applies even when the request doesn't name it: "write documentation for X," "document this feature," "add a section on Y," "review this page," and "does this doc meet standards" should all route to it, not to a manual edit or review.
+Documentation content under `docs/content/` and `docs/community/` is handled by one skill, `docs` (`.agent/skills/docs/SKILL.md`), covering every stage: scaffolding, writing, and review. **Invoke it instead of creating, editing, or reviewing a doc page by hand** — it enforces the project's writing standards directly, so the rules live in one executable place, not duplicated in prose here. This applies even when the request doesn't name it: "write documentation for X," "document this feature," "add a section on Y," "review this page," and "does this doc meet standards" should all route to it, not to a manual edit or review.
 
 The skill's `SKILL.md` is a dispatch table over its reference files, each covering one stage:
 

docs/blog/2026-09-02-thunderid-1-0.mdx

@@ -110,7 +110,7 @@ Configuration has its own tooling. A CLI covers installation through day-to-day
 
 ## Get involved
 
-<ProductName /> is open source, and the work around it is open too. Design discussions happen in public before anything is built. Proposals, decisions, and the reasoning behind them are all in the open. The [Community guide](/docs/v1.0.x/community/overview) covers how to get started, whether that is filing an issue, joining a discussion, or opening a pull request.
+<ProductName /> is open source, and the work around it is open too. Design discussions happen in public before anything is built. Proposals, decisions, and the reasoning behind them are all in the open. The [Community guide](/community/overview) covers how to get started, whether that is filing an issue, joining a discussion, or opening a pull request.
 
 One kind of feedback we especially want right now. If you are integrating <ProductName /> and something is harder than it should be, tell us. First integrations surface friction that nobody on the inside can see anymore.
 

docs/content/community/contributing/documentation-guide/advanced-topics.mdx → docs/community/contributing/documentation-guide/advanced-topics.mdx

@@ -412,6 +412,8 @@ This creates:
 - `versioned_sidebars/version-1.0.0-sidebars.json`: Versioned sidebars
 - Updates `versions.json`
 
+Only `docs/content/` is snapshotted. The community docs in `docs/community/` are served by a separate, unversioned plugin instance and stay outside every version.
+
 ### Version Configuration
 
 ```typescript title="docusaurus.config.ts"

docs/content/community/contributing/documentation-guide/writing-guide.mdx → docs/community/contributing/documentation-guide/writing-guide.mdx

@@ -26,13 +26,14 @@ Before writing <ProductName /> documentation, familiarize yourself with the offi
 <ProductName /> documentation is organized into separate sections, each with its own sidebar:
 
 ```text
-docs/content/
-├── guides/           # User guides and tutorials (docsSidebar)
-├── sdks/             # SDK documentation (per-SDK sidebars)
+docs/
+├── content/
+│   ├── guides/       # User guides and tutorials (docsSidebar)
+│   └── sdks/         # SDK documentation (per-SDK sidebars)
 └── community/        # Community and contributing docs (communitySidebar)
 ```
 
-Each section uses either **autogenerated** or **manual** sidebars defined in <RepoLink path="/blob/main/docs/sidebars.ts">`docs/sidebars.ts`</RepoLink>.
+Each section uses either **autogenerated** or **manual** sidebars defined in <RepoLink path="/blob/main/docs/sidebars.ts">`docs/sidebars.ts`</RepoLink>, except the community section, which has its own <RepoLink path="/blob/main/docs/sidebarsCommunity.ts">`docs/sidebarsCommunity.ts`</RepoLink>.
 
 ## Diagrams
 
@@ -704,14 +705,14 @@ Manual sidebars give you complete control over:
 
 ## Adding Community Documentation
 
-Community documentation (contributing guides, design docs, etc.) lives in `docs/content/community/` and uses an **autogenerated sidebar**.
+Community documentation (contributing guides, design docs, etc.) lives in `docs/community/`, outside `docs/content/`. It is served from `/community/` by its own docs plugin instance and is **not versioned**, because it describes how to contribute to the project as it is today rather than how a released version behaves.
 
 ### Creating Community Docs
 
 1. Navigate to the community directory:
 
 ```bash
-cd docs/content/community
+cd docs/community
 ```
 
 2. Create a new guide or directory:
@@ -741,10 +742,10 @@ Our community guidelines...
 Same as guide categories, use `_category_.json`:
 
 ```bash
-mkdir docs/content/community/design-principles
+mkdir docs/community/design-principles
 ```
 
-```json title="docs/content/community/design-principles/_category_.json"
+```json title="docs/community/design-principles/_category_.json"
 {
   "position": 2,
   "label": "Design Principles",

docs/content/deployment/observability.mdx

@@ -304,4 +304,4 @@ If no spans appear, check the following:
 ## Next Steps
 
 - See [Observability Configuration](../../deployment/configuration#observability-configuration) for the full list of settings for each output backend.
-- See the [Observability Contributing Guide](../../community/contributing/contributing-code/backend-development/observability) to learn how to add instrumentation to new <ProductName /> components.
+- See the [Observability Contributing Guide](/community/contributing/contributing-code/backend-development/observability) to learn how to add instrumentation to new <ProductName /> components.

docs/docusaurus.config.ts

@@ -1,6 +1,7 @@
 // Copyright 2026 The ThunderID Authors
 // SPDX-License-Identifier: Apache-2.0
 
+import type {Options as DocsOptions} from '@docusaurus/plugin-content-docs';
 import type * as Preset from '@docusaurus/preset-classic';
 import type {Config} from '@docusaurus/types';
 import {themes as prismThemes} from 'prism-react-renderer';
@@ -45,6 +46,23 @@ const baseUrl =
 // eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
 const siteUrl = process.env.DOCUSAURUS_URL || productConfig.documentation.deployment.production.url;
 
+// Replace {{ProductName}}, {{productSlug}}, and local-URL placeholders inside code blocks at
+// build time. Shared by every docs plugin instance.
+const docsRehypePlugins: DocsOptions['rehypePlugins'] = [
+  [
+    rehypeProductName,
+    {
+      productName: productConfig.project.name,
+      productSlug: productConfig.project.name.toLowerCase(),
+      replacements: {
+        '{{ConsoleUrl}}': productConfig.local.consoleUrl,
+        '{{WayFinderSampleUrl}}': productConfig.local.samples.wayfinderUrl,
+        '{{WayFinderMailUrl}}': productConfig.local.samples.wayfinderMailUrl,
+      },
+    },
+  ],
+];
+
 const config: Config = {
   title: productConfig.project.name,
   tagline: productConfig.project.description,
@@ -167,6 +185,20 @@ j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
     personaPlugin,
     './plugins/docusaurus-plugin-llms-txt',
     './plugins/docusaurus-plugin-markdown-export',
+    // Community docs are a separate, unversioned plugin instance. They describe how to
+    // contribute to the project as it stands today, so they are not snapshotted per
+    // release and are served from /community/ instead of /docs/<version>/community/.
+    [
+      '@docusaurus/plugin-content-docs',
+      {
+        id: 'community',
+        path: 'community',
+        routeBasePath: 'community',
+        sidebarPath: './sidebarsCommunity.ts',
+        editUrl: productConfig.project.source.github.editUrls.content,
+        rehypePlugins: docsRehypePlugins,
+      } satisfies DocsOptions,
+    ],
   ],
 
   presets: [
@@ -201,21 +233,7 @@ j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
               badge: false,
             },
           },
-          // Replace {{ProductName}}, {{productSlug}}, and local-URL placeholders inside code blocks at build time.
-          rehypePlugins: [
-            [
-              rehypeProductName,
-              {
-                productName: productConfig.project.name,
-                productSlug: productConfig.project.name.toLowerCase(),
-                replacements: {
-                  '{{ConsoleUrl}}': productConfig.local.consoleUrl,
-                  '{{WayFinderSampleUrl}}': productConfig.local.samples.wayfinderUrl,
-                  '{{WayFinderMailUrl}}': productConfig.local.samples.wayfinderMailUrl,
-                },
-              },
-            ],
-          ],
+          rehypePlugins: docsRehypePlugins,
         },
         blog: {
           path: 'blog',
@@ -310,6 +328,7 @@ j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
         {
           type: 'docSidebar',
           sidebarId: 'communitySidebar',
+          docsPluginId: 'community',
           position: 'right',
           label: 'Community',
         },

docs/plugins/docusaurus-plugin-markdown-export/index.js

@@ -17,6 +17,10 @@ const {processMarkdownFile} = require('./mdxProcessor');
  *     → build/docs/v1.0.x/getting-started/foo.md
  *     → served at /docs/v1.0.x/getting-started/foo.md
  *
+ *   community/overview.mdx (permalink /community/overview)
+ *     → build/community/overview.md
+ *     → served at /community/overview.md
+ *
  * Deriving the output path from `doc.permalink` (rather than re-deriving a
  * slug from the source file path) keeps this in lockstep with
  * docusaurus-plugin-llms-txt, including for index/category-root docs whose
@@ -73,12 +77,14 @@ module.exports = function pluginMarkdownExport(context) {
 
     async allContentLoaded({allContent}) {
       const docsPlugin = allContent?.['docusaurus-plugin-content-docs'];
-      const docsContent = docsPlugin?.default;
-      if (!docsContent?.loadedVersions) {
+      // Collect every docs plugin instance: the versioned "default" one and the
+      // unversioned "community" one, which has a single "current" version.
+      const versions = Object.values(docsPlugin ?? {}).flatMap((instance) => instance?.loadedVersions ?? []);
+      if (versions.length === 0) {
         console.warn('[markdown-export] docs plugin content not found; skipping');
         return;
       }
-      loadedVersions = docsContent.loadedVersions;
+      loadedVersions = versions;
     },
 
     async postBuild({outDir}) {