docs: fix Fern versioned plugin docs

Author: andreatgretel

fern/AGENTS.md

@@ -23,6 +23,10 @@ Use hybrid versioning. A version YAML may reuse older page files for unchanged c
 
 Example: a `v0.5.9` nav entry can point to `./v0.5.8/pages/concepts/columns.mdx`. Users still see the page under the active `v0.5.9` URL because Fern routes by version slug and nav title, not by source file path.
 
+Before editing a file under an older shared tree such as `fern/versions/v0.5.8/pages/...`, check every `fern/versions/*.yml` file that points at it. If the content describes a newer release, copy it into `latest/pages/...` and the target `vX.Y.Z/pages/...` tree, then retarget only those nav entries.
+
+Dev Notes are versioned. Do not add a new release-specific post to an older frozen nav or page tree. If a post says "As of Data Designer vX.Y.Z", it belongs in `latest.yml` and `vX.Y.Z.yml`, not in older version navs.
+
 Do not call a version frozen if its YAML points at shared pages that may change later. If a page's content must remain release-specific, copy it into `fern/versions/vX.Y.Z/pages/...` and point that version's YAML to the copy.
 
 ## Release Prep

fern/README.md

@@ -77,6 +77,8 @@ Current Fern versions:
 fern/versions/
 ├── latest.yml          ← rolling nav file
 ├── latest/pages/...    ← latest-only page overrides
+├── v0.6.0.yml          ← release nav file
+├── v0.6.0/pages/...    ← v0.6.0-only page overrides
 ├── v0.5.9.yml          ← release nav file
 ├── v0.5.9/pages/...    ← v0.5.9-only page overrides
 ├── v0.5.8.yml          ← first migrated release nav file
@@ -85,11 +87,13 @@ fern/versions/
 └── older/pages/...     ← links to the MkDocs archive
 ```
 
-`docs.yml` registers `slug: latest`, `slug: v0.5.9`, `slug: v0.5.8`, and `slug: older-versions`. The `latest` and `v0.5.9` nav files intentionally reuse the migrated `v0.5.8/pages/` tree for most content so the first Fern-native versions do not duplicate every page. Add version-specific page copies only when content diverges.
+`docs.yml` registers `slug: latest`, `slug: v0.6.0`, `slug: v0.5.9`, `slug: v0.5.8`, and `slug: older-versions`. The `latest`, `v0.6.0`, and `v0.5.9` nav files intentionally reuse the migrated `v0.5.8/pages/` tree for unchanged content so Fern-native versions do not duplicate every page. Add version-specific page copies only when content diverges.
 
 Fern version URLs are based on the active version entry, not the source file path. A `v0.5.9` page can point at `./v0.5.8/pages/...` and still render under `/nemo/datadesigner/v0.5.9/...`; users do not see the reused source path.
 
-Dev Notes are versioned: `latest.yml` can include posts from `main` that are not in old release navs yet. Frozen release navs (`v0.5.9.yml`, `v0.5.8.yml`) should include only posts available at that release point.
+Before editing a file under an older shared tree such as `fern/versions/v0.5.8/pages/...`, check every `fern/versions/*.yml` file that points at it. If the content describes a newer release, copy it into `latest/pages/...` and the target `vX.Y.Z/pages/...` tree, then retarget only those nav entries.
+
+Dev Notes are versioned: `latest.yml` can include posts from `main` that are not in old release navs yet. Frozen release navs (`v0.6.0.yml`, `v0.5.9.yml`, `v0.5.8.yml`) should include only posts available at that release point. If a Dev Note says "As of Data Designer vX.Y.Z", do not add it to an older frozen nav or an older shared page tree.
 
 Released versions older than `v0.5.8` stay on the MkDocs archive at `https://nvidia-nemo.github.io/DataDesigner/<version>/`. The Fern version picker includes an "Older versions" page linking to those archives.
 
@@ -130,6 +134,7 @@ fern/
 ├── code-reference/            ← gitignored; populated by `make generate-fern-api-reference`
 └── versions/
     ├── latest.yml             ← rolling navigation tree
+    ├── v0.6.0.yml             ← release navigation tree
     ├── v0.5.9.yml             ← release navigation tree
     ├── v0.5.8.yml             ← navigation tree
     ├── older.yml              ← older versions landing page

fern/docs.yml

@@ -45,9 +45,12 @@ experimental:
   - ./components
   basepath-aware: true
 versions:
-- display-name: "Latest · v0.5.9"
+- display-name: "Latest · v0.6.0"
   path: versions/latest.yml
   slug: latest
+- display-name: "v0.6.0"
+  path: versions/v0.6.0.yml
+  slug: v0.6.0
 - display-name: "v0.5.9"
   path: versions/v0.5.9.yml
   slug: v0.5.9
@@ -76,7 +79,7 @@ redirects:
     destination: "/nemo/datadesigner/older-versions"
 
   # ---- Historical MkDocs archives ----
-  # Fern only has real v0.5.8/v0.5.9 entries today. Older released docs remain on the
+  # Fern only has real version entries starting at v0.5.8. Older released docs remain on the
   # legacy MkDocs gh-pages archive, so version-prefixed Fern URLs for those
   # releases should leave the Fern site rather than showing current content.
   - source: "/nemo/datadesigner/v0.5.7"

fern/versions/latest.yml

@@ -132,11 +132,11 @@ navigation:
   - section: Plugins
     contents:
       - page: Overview
-        path: ./v0.5.8/pages/plugins/overview.mdx
+        path: ./latest/pages/plugins/overview.mdx
       - page: Example Plugin
-        path: ./v0.5.8/pages/plugins/example.mdx
+        path: ./latest/pages/plugins/example.mdx
       - page: FileSystemSeedReader Plugins
-        path: ./v0.5.8/pages/plugins/filesystem_seed_reader.mdx
+        path: ./latest/pages/plugins/filesystem_seed_reader.mdx
       - page: Discover
         path: ./v0.5.8/pages/plugins/discover.mdx
   - section: Code Reference
@@ -169,6 +169,8 @@ navigation:
     contents:
       - page: Overview
         path: ./latest/pages/devnotes/index.mdx
+      - page: Have It Your Way
+        path: ./latest/pages/devnotes/posts/have-it-your-way.mdx
       - page: VLM Long Document Understanding
         path: ./latest/pages/devnotes/posts/vlm-long-document-understanding.mdx
       - page: Push Datasets to Hugging Face Hub

fern/versions/latest/pages/devnotes/index.mdx

@@ -9,6 +9,14 @@ import { BlogCard, BlogGrid } from "@/components/BlogCard";
 Welcome to NeMo Data Designer Dev Notes — in-depth guides, benchmark write-ups, and insights from the team building NeMo Data Designer.
 
 <BlogGrid>
+  <BlogCard
+    href="/dev-notes/have-it-your-way"
+    title="Have It Your Way"
+    description="A plugin framework for the custom pieces every real project ends up needing."
+    date="May 5, 2026"
+    authors={["jgreco", "etramel"]}
+    image={<img src="/assets/have-it-your-way/data-designer-plugins-hero.png" alt="" loading="lazy" />}
+  />
   <BlogCard
     href="/dev-notes/vlm-long-document-understanding"
     title="Training a VLM to Understand Long Documents"