Enhance README and guide generator to support nested directories for dynamic guides

- Updated README.md to include instructions for configuring remote guides from nested directories, detailing the use of `targetFilename` for top-level page generation.
- Modified guide-generator.js to add new dynamic guides for 'Prefix Cache Storage' and 'Prefix Cache Storage - CPU', including sidebar positions and descriptions.

Signed-off-by: Pete Cheslock <[email protected]>

Author: petecheslock

README.md

@@ -97,12 +97,55 @@ git push                           # Triggers automatic deployment
 - Component descriptions and version tags
 - **Components** sync from their individual release tags
 - **Guides** sync from the llm-d/llm-d release tag
+- **Architecture docs** sync from the llm-d/llm-d release tag
 - **Community docs** always sync from `main` branch (latest)
 
+### Understanding Versioned vs. Always-Current Content
+
+The remote content system supports two sync strategies:
+
+**Versioned Content** (syncs from release tags):
+- **Guides** (`docs/guide/`) - Uses `RELEASE_INFO.version` from `components-data.yaml`
+- **Architecture** (`docs/architecture/`) - Uses `RELEASE_INFO.version` from `components-data.yaml`
+- **Components** (`docs/architecture/Components/`) - Each component uses its own `version` field from `components-data.yaml`
+- **Infrastructure Providers** (`docs/guide/InfraProviders/`) - Uses `RELEASE_INFO.version` from `components-data.yaml`
+
+These docs are pinned to specific release tags (e.g., `v0.3.1`) to ensure documentation matches the released code. When you update `release.version` in `components-data.yaml`, all versioned content automatically syncs from the new tag.
+
+**Always-Current Content** (syncs from `main` branch):
+- **Community docs** (`docs/community/`) - Contributing guidelines, Code of Conduct, Security Policy, SIGs
+- These are configured via `COMMON_REPO_CONFIGS['llm-d-main'].branch = 'main'` in `component-configs.js`
+
+Community documentation stays current with the latest policies and processes, independent of releases. The `branch` field in `COMMON_REPO_CONFIGS` controls this behavior.
+
+**How it works:**
+- `generateRepoUrls()` in `component-configs.js` prefers `version` over `branch` when both exist
+- Versioned content sources call `findRepoConfig('llm-d')` and use `RELEASE_INFO.version`
+- Community sources call `findRepoConfig('llm-d')` and use `repoConfig.branch` (which is `'main'`)
+- This separation lets you cut releases without worrying about stale community policies
+
 ### Testing content from a feature branch
 
 To preview remote docs from a work-in-progress branch (for example `liu-cong-debug`), temporarily set `release.version` in `remote-content/remote-sources/components-data.yaml` to that branch name. Run `npm start` or `npm run build` to pull the branch content into the site. When testing is done, change `release.version` back to the released tag so production remains on the official docs.
 
+### Supporting remote guides from nested directories
+
+Dynamic guides are configured in `remote-content/remote-sources/guide/guide-generator.js`. Each entry in `DYNAMIC_GUIDES` points at a `README.md` inside `guides/<dirName>/` in the main repo. By default, the generator mirrors the directory structure when it creates docs: `dirName: 'some-folder/sub-guide'` produces `some-folder/sub-guide.md` under `docs/guide/Installation`, and the sidebar groups pages under a folder.
+
+If you want to surface a nested source as a top-level page, add an optional `targetFilename` to the guide definition. Example:
+
+```javascript
+{
+  dirName: 'prefix-cache-storage/cpu',
+  title: 'Prefix Cache Storage - CPU',
+  description: '…',
+  sidebarPosition: 5,
+  targetFilename: 'prefix-cache-storage-cpu.md'
+}
+```
+
+With `targetFilename`, the generator still reads `guides/prefix-cache-storage/cpu/README.md`, but it writes the output to `docs/guide/Installation/prefix-cache-storage-cpu.md`, letting the page appear alongside other top-level guides. Leave `targetFilename` out to keep the default nested behavior.
+
 **Manual updates:** You can also manually edit `components-data.yaml` if needed.
 
 ### Adding New Components

remote-content/remote-sources/guide/guide-generator.js

@@ -73,36 +73,43 @@ const DYNAMIC_GUIDES = [
     description: 'Well-lit path for intelligent inference scheduling with load balancing',
     sidebarPosition: 3
   },
+  {
+    dirName: 'prefix-cache-storage',
+    title: 'Prefix Cache Storage',
+    description: 'Well-lit path for separating prefill and decode operations',
+    sidebarPosition: 4
+  },
+  {
+    dirName: 'prefix-cache-storage/cpu',
+    title: 'Prefix Cache Storage - CPU',
+    description: 'Well-lit path for separating prefill and decode operations',
+    sidebarPosition: 5,
+    targetFilename: 'prefix-cache-storage-cpu.md'
+  },
   {
     dirName: 'pd-disaggregation', 
     title: 'Prefill/Decode Disaggregation',
     description: 'Well-lit path for separating prefill and decode operations',
-    sidebarPosition: 4
+    sidebarPosition: 6
   },
   {
     dirName: 'precise-prefix-cache-aware',
     title: 'Precise Prefix Cache Aware Routing',
     description: 'Feature guide for precise prefix cache aware routing',
-    sidebarPosition: 5
+    sidebarPosition: 7
   },
   {
     dirName: 'wide-ep-lws',
     title: 'Wide Expert Parallelism with LeaderWorkerSet',
     description: 'Well-lit path for wide expert parallelism using LeaderWorkerSet',
-    sidebarPosition: 6
+    sidebarPosition: 8
   },
   {
     dirName: 'simulated-accelerators',
     title: 'Accelerator Simulation',
     description: 'Feature guide for llm-d accelerator simulation',
-    sidebarPosition: 7
-  },
-  {
-    dirName: 'predicted-latency-based-scheduling',
-    title: 'Predicted Latency Based Load Balancing',
-    description: 'Well-lit path for predicted latency based load balancing',
-    sidebarPosition: 8
-  },
+    sidebarPosition: 9
+  }
 ];
 
 /**
@@ -147,6 +154,7 @@ function createGuidePlugins() {
   // Add dynamic guides
   DYNAMIC_GUIDES.forEach((guide) => {
     const sourceFile = `guides/${guide.dirName}/README.md`;
+    const targetFilename = guide.targetFilename || `${guide.dirName}.md`;
 
     plugins.push([
       'docusaurus-plugin-remote-content',
@@ -166,7 +174,7 @@ function createGuidePlugins() {
               sidebarLabel: guide.title,
               sidebarPosition: guide.sidebarPosition,
               filename: sourceFile,
-              newFilename: `${guide.dirName}.md`,
+              newFilename: targetFilename,
               repoUrl,
               branch: releaseVersion,
               content,