From d469dbf68addfcf1ec6d8f6d99dbe399a09231f3 Mon Sep 17 00:00:00 2001
From: Mathieu Legault <mathieu@legault.me>
Date: Thu, 11 Jun 2026 08:43:52 -0400
Subject: [PATCH 1/4] Add fern-docs agent skills bundle for the install-skills
 modal

Vendor the fern-docs skill from fern-api/skills into
fern/.well-known/skills/ so the docs publish uploads it (per fern-api/fern#16446,
ADR 0015) and serves it at /.well-known/skills/. This makes
`npx skills add https://buildwithfern.com/learn` work end-to-end and sources the
install-skills page-action modal's live skill list.

Bundle: index.json discovery manifest + fern-docs/SKILL.md + references/changelog.md.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 fern/.well-known/skills/fern-docs/SKILL.md    | 144 ++++++++++++++++++
 .../skills/fern-docs/references/changelog.md  | 141 +++++++++++++++++
 fern/.well-known/skills/index.json            |   9 ++
 3 files changed, 294 insertions(+)
 create mode 100644 fern/.well-known/skills/fern-docs/SKILL.md
 create mode 100644 fern/.well-known/skills/fern-docs/references/changelog.md
 create mode 100644 fern/.well-known/skills/index.json

diff --git a/fern/.well-known/skills/fern-docs/SKILL.md b/fern/.well-known/skills/fern-docs/SKILL.md
new file mode 100644
index 000000000..abc1ed4bf
--- /dev/null
+++ b/fern/.well-known/skills/fern-docs/SKILL.md
@@ -0,0 +1,144 @@
+---
+name: fern-docs
+description: >-
+  Author and edit Fern documentation: MDX pages, navigation, docs.yml config,
+  custom components, landing pages, and changelog entries. Use when working in a
+  Fern docs repo (a fern/ directory with docs.yml). Routes to a detailed
+  reference per task.
+---
+
+# Fern docs authoring
+
+Write and edit documentation on a Fern site. `SKILL.md` is the index: follow the
+principles and voice below, then read the `references/` file that matches the
+task before writing. Don't work from this page alone when a reference exists.
+
+## Fern resources
+
+Fern's configuration evolves. Look things up rather than guessing.
+
+- **Docs:** https://buildwithfern.com/learn/docs/getting-started/overview
+- **Page index:** https://buildwithfern.com/learn/llms.txt
+- **MCP server** — connect your agent to Fern's live docs and query it for any
+  syntax or behavior you're unsure of. The endpoint works with any MCP client;
+  for Claude Code:
+
+  ```bash
+  claude mcp add --transport http fern https://buildwithfern.com/learn/_mcp/server
+  ```
+
+## Routing
+
+| Task | Read |
+|------|------|
+| Writing or editing a changelog entry | `references/changelog.md` |
+
+## Core principles
+
+- **Write what the reader needs to succeed — no more.** Every sentence earns its place.
+- **Prefer editing over creating.** Search the repo for a page that already
+  covers the topic and update it instead of adding a duplicate.
+- **Make minimal, precise edits.** Don't rewrite a page when a paragraph fix will do.
+- **Push back when something seems wrong.** Explain why rather than complying silently.
+- **Ask when unclear.** Don't fill gaps with assumptions.
+- **Never fabricate.** If you don't know a config key or behavior, look it up
+  (MCP server or docs) or say so. Don't invent frontmatter or YAML fields.
+- **Cross-reference.** When you mention a concept documented elsewhere, link to it
+  so readers can find their way.
+
+## Voice
+
+Dry and direct. State requirements and behavior plainly.
+
+- **Cut hedges and nudges:** "just", "simply", "make sure you", "you'll want to".
+  Prefer "X requires Y" over "make sure you have Y so you can do X".
+- **Cut connective filler:** "so that", "in order to", "be sure to".
+- **Limit em dashes** to one per short paragraph; reach for a colon or
+  parentheses before a second.
+- **No conversational framing in callouts or steps.** "Localization requires the
+  latest CLI" beats "Localization is under active development, so make sure
+  you're on the latest CLI before configuring it."
+
+## Links
+
+Internal links are URL paths derived from **this repo's own `docs.yml` and page
+frontmatter** — not file paths on disk or relative paths. Nearly every edit
+touches a link, so get this right every time.
+
+A page URL is `<base-path>/<product-slug>/<rest>`:
+
+- **Base path** — the prefix in your docs URL (e.g. `/learn`, `/docs`; may be empty).
+- **Product slug** — the product's `slug` in `fern/docs.yml`. Omitted for a
+  product with no `slug:` (such as a default single Home product).
+- **`<rest>`** — found by step 1 or step 2 below.
+
+To find `<rest>`:
+
+1. **Open the target page and check its frontmatter for `slug:`.** A frontmatter
+   slug is **absolute within the product**: it *is* `<rest>` on its own, and it
+   replaces the entire section/folder hierarchy. The section's slug does not
+   appear. Do not walk the navigation.
+2. **Otherwise, walk `docs.yml`** within the product, from section through any
+   folders to the page. Each level contributes one slug:
+   - Its explicit `slug:` if set.
+   - Otherwise auto-derived from the display name: lowercased, spaces to
+     hyphens, special characters stripped (so `v3 (Latest)` becomes
+     `v-3-latest`). Auto-derivation isn't always obvious — verify, don't assume.
+   - In folder-based navigation, a page's slug comes from its **filename**, not
+     a display name (`quick-start.mdx` to `quick-start`).
+   - **Omit any level with `skip-slug: true`** — it contributes no segment.
+
+Example — page `./pages/ai/overview.mdx` under section "AI features", in product
+`docs`, base path `/learn`:
+
+- with frontmatter `slug: ai-ai` → `/learn/docs/ai-ai` (the `ai-features`
+  section slug is dropped)
+- with no frontmatter slug → `/learn/docs/ai-features/overview` (section
+  auto-slug `ai-features` + page auto-slug `overview`)
+
+Section slugs frequently differ from folder names, so never guess the URL from
+the directory layout. If you can't resolve a path from `docs.yml` and the page's
+frontmatter, say so rather than guessing.
+
+**Anchors** append `#heading`, and only resolve for real `##`/`###` Markdown
+headings — not for JSX title props like `<Step title>`, `<Tab title>`,
+`<Accordion title>`, or `<Card title>`.
+
+**Not internal links** (leave as-is): external `https://` URLs, image paths
+(`./images/...`), snippet includes (`<Markdown src="/snippets/..." />`), and
+same-page anchors (`#section`).
+
+## Cross-referencing
+
+When you document new functionality — a new page, or new behavior on an existing
+one — related pages usually need a pointer to it, or the new content is hard to
+find from where readers actually start. This applies to small edits too, not
+just new pages.
+
+- **One canonical home.** The full explanation lives on one page; every other
+  page that touches the topic links to it instead of restating it. If you're
+  copying more than a sentence or two onto another page, it belongs on the
+  canonical page.
+- **Find the targets.** Grep the docs for the feature name and one or two related
+  keywords, then read each hit and decide whether a pointer is warranted:
+
+  ```bash
+  grep -rln "<feature>\|<keyword>" fern --include="*.mdx"
+  ```
+
+  Common targets: pages for behavior the feature affects, adjacent feature pages,
+  and overview or landing pages.
+- **Use the lightest form that works:** an inline link inside an existing
+  sentence, then a `<Note>` for a secondary aside, then a new `##` section, then
+  a new page. Inline links and Notes add no maintenance surface; new pages and
+  sections do.
+- **Phrase inline links naturally — never "See [page]."** Put the link on a noun
+  phrase already in the sentence, not a tacked-on pointer sentence. Don't wrap a
+  lone link in a `<Tip>` whose only job is to host it.
+  - Good: "Each request counts against your [rate limit](...), which resets hourly."
+  - Bad: "Requests are rate limited. See the [rate limits reference](...) for details."
+  - Bad: a standalone `<Tip>` containing only "For more, see [rate limits](...)."
+- **Frame by function, not plumbing.** Contrast what each feature does ("X
+  decides A; Y decides B"), not that they share a config key or sit in the same
+  directory. If the only thing linking two features is the same YAML key, it's
+  not worth a cross-reference.
diff --git a/fern/.well-known/skills/fern-docs/references/changelog.md b/fern/.well-known/skills/fern-docs/references/changelog.md
new file mode 100644
index 000000000..85f35d5c5
--- /dev/null
+++ b/fern/.well-known/skills/fern-docs/references/changelog.md
@@ -0,0 +1,141 @@
+# Writing changelog entries
+
+A changelog entry announces a shipped change to users. Each entry is a dated
+`.mdx` file; the filename date is the title. This reference covers how to *write*
+an entry. For setup (folder location, `docs.yml` wiring, RSS, navigation), see
+the official docs: https://buildwithfern.com/learn/docs/configuration/changelogs
+
+## File and naming
+
+- Entries go directly in the `changelog/` folder inside `fern/`. The folder must
+  be named `changelog` exactly. **No subdirectories** — nested files are silently
+  ignored.
+- One entry per date, named by date. Supported filename formats: `YYYY-MM-DD`
+  (preferred, sorts cleanly), `MM-DD-YYYY`, `MM-DD-YY`. Always use `.mdx` (Fern
+  also accepts `.md`, but `.mdx` is the standard and unlocks the component
+  library).
+- Sort order comes from the **filename date**, not frontmatter. A wrong filename
+  date puts the entry in the wrong position.
+- The date is the title. **Do not add an h1.**
+- If a file already exists for that date, add your feature as a new `##` section
+  in it rather than creating a second file.
+
+## Frontmatter tags
+
+Every entry needs a `tags` array. Tags drive the changelog's filtering, so use
+specific, descriptive tags users would search for — by product area, feature,
+release stage, platform, or impact:
+
+```mdx
+---
+tags: ["voice-api", "breaking-change"]
+---
+```
+
+**Reuse existing tags** for consistency before adding a new one:
+
+```bash
+grep -rh "^tags:" changelog/ | sort | uniq -c | sort -rn
+```
+
+A near-duplicate tag (`auth` when `security` already exists) fragments the
+filter.
+
+## Entry format
+
+```mdx
+---
+tags: ["search"]
+---
+
+## Filter search results by section
+
+You can now scope a search to a single section of your docs. Visitors pick a
+section from the search bar, and results are limited to pages under it.
+
+- Available on all plans.
+- Configured per docs instance.
+
+<Button intent="none" outlined rightIcon="arrow-right" href="/docs/customization/search">Read the docs</Button>
+```
+
+- **One `##` per feature.** No h1.
+- **Lead with the capability** — "You can now…" — not the implementation.
+- **Keep it short:** 2–6 sentences. Bullets for detail lists, not the whole entry.
+- **End with a Button** linking to the relevant docs page (recommended).
+- For dashboard/UI changes, give the click-path (**Settings** > **Page access**)
+  before the Button.
+
+## The docs-link Button
+
+The `href` is a docs **URL path** built from `docs.yml`, not a file path:
+`<base-path>/<section-slug>/<page-slug>`.
+
+```mdx
+<!-- WRONG: file path on disk -->         href="/changelog/../pages/search/configuration"
+<!-- WRONG: guessed from folder names --> href="/docs/search-config/configuration"
+<!-- CORRECT: built from docs.yml -->     href="/docs/customization/search"
+```
+
+See the **Links** section of `SKILL.md` for how to construct the path (base
+path, product slug, frontmatter slugs, `skip-slug`) from this repo's `docs.yml`.
+
+## Voice
+
+Dry and direct. Cut hedges ("just", "simply", "make sure you") and filler ("in
+order to", "so that"). At most one em dash per short paragraph.
+
+## Options
+
+Beyond a plain entry, the changelog supports:
+
+- **Overview page** — an `overview.mdx` in the `changelog/` folder renders above
+  all entries. `overview.mdx` is a reserved filename, so it is never treated as a
+  dated entry.
+- **Components are available but avoid them.** `.mdx` entries *can* use Fern's
+  component library (`<Note>`, `<Card>`, `<Accordion>`, etc.), but stacked across
+  a list of short entries they create visual noise. House rule: prose + the
+  `<Button>` only. Reach for another component only when it's genuinely the only
+  way to convey something.
+- **Tab or section** — the changelog is wired in `docs.yml` either as a tab
+  (`tabs: { changelog: { changelog: ./changelog } }`) or as a section
+  (`navigation: [ { changelog: ./changelog, title: ..., slug: ... } ]`).
+- **RSS feed** — generated automatically; append `.rss` to the changelog path
+  (e.g. `https://yourdomain.com/docs/changelog.rss`). No config needed.
+- **Per-entry permalinks** — each entry gets `…/changelog/YYYY/M/D` (month and
+  day are not zero-padded).
+
+For exact `docs.yml` syntax, see the official docs linked above.
+
+## Gotchas
+
+- **Folder name is exact and flat.** Not `changelogs`, not nested — files in
+  subfolders are silently dropped with no error.
+- **Slug must be recognized.** `fern check` (`valid-changelog-slug`) errors
+  unless the changelog's effective slug is one of: `changelog`, `changelogs`,
+  `release-notes`, `releasenotes`, `whats-new`, `whatsnew`.
+- **A section changelog can't live inside an `api:` block** in `docs.yml`.
+- **Only `tags` is a supported frontmatter field.** `title`, `date`, `hidden`,
+  etc. are not — the date comes from the filename. Don't add undocumented keys.
+- **The tag filter UI only renders when entries have tags.** No tags, no filter.
+
+## What not to do
+
+- Don't use h1 (`#`) — the date is the title.
+- Don't describe implementation details; describe the user benefit.
+- Don't invent a tag when an existing one fits.
+- Don't write the Button `href` from the file path on disk.
+- Don't use components other than the `<Button>` — prose keeps the entry list clean.
+
+## Checklist
+
+Mechanics to verify before considering an entry done:
+
+- [ ] File is in `fern/changelog/`, named with a supported date format, no subfolder.
+- [ ] `.mdx` extension.
+- [ ] Frontmatter has a `tags` array and no unsupported fields.
+- [ ] Tags reused from the existing set where one fits.
+- [ ] No h1; each feature is an `##`.
+- [ ] Opens with the user capability; 2–6 sentences per feature.
+- [ ] Button present per feature, `href` a docs URL path (not a disk path).
+- [ ] Dashboard/UI changes include the click-path before the Button.
diff --git a/fern/.well-known/skills/index.json b/fern/.well-known/skills/index.json
new file mode 100644
index 000000000..922ce2e1f
--- /dev/null
+++ b/fern/.well-known/skills/index.json
@@ -0,0 +1,9 @@
+{
+  "skills": [
+    {
+      "name": "fern-docs",
+      "description": "Author and edit Fern documentation: MDX pages, navigation, docs.yml config, custom components, landing pages, and changelog entries. Use when working in a Fern docs repo (a fern/ directory with docs.yml). Routes to a detailed reference per task.",
+      "files": ["SKILL.md", "references/changelog.md"]
+    }
+  ]
+}

From 4245e5ddaf9b683228cfbb8f6cc0d62c9e611fef Mon Sep 17 00:00:00 2001
From: Mathieu Legault <mathieu@buildwithfern.com>
Date: Thu, 11 Jun 2026 10:00:19 -0400
Subject: [PATCH 2/4] Re-vendor fern-docs skill from fern-api/skills main

Picks up the merged changelog/products/cross-ref updates: adds
references/products.md, refreshes SKILL.md and changelog.md, and lists
the new reference in index.json so installs deliver the complete skill.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---
 fern/.well-known/skills/fern-docs/SKILL.md    |   4 +-
 .../skills/fern-docs/references/changelog.md  |   2 +-
 .../skills/fern-docs/references/products.md   | 121 ++++++++++++++++++
 fern/.well-known/skills/index.json            |   8 +-
 4 files changed, 131 insertions(+), 4 deletions(-)
 create mode 100644 fern/.well-known/skills/fern-docs/references/products.md

diff --git a/fern/.well-known/skills/fern-docs/SKILL.md b/fern/.well-known/skills/fern-docs/SKILL.md
index abc1ed4bf..0e813371d 100644
--- a/fern/.well-known/skills/fern-docs/SKILL.md
+++ b/fern/.well-known/skills/fern-docs/SKILL.md
@@ -17,7 +17,8 @@ task before writing. Don't work from this page alone when a reference exists.
 
 Fern's configuration evolves. Look things up rather than guessing.
 
-- **Docs:** https://buildwithfern.com/learn/docs/getting-started/overview
+- **Docs:** https://buildwithfern.com/learn/docs/getting-started/overview.md
+  (append `.md` to any docs URL for clean markdown to fetch)
 - **Page index:** https://buildwithfern.com/learn/llms.txt
 - **MCP server** — connect your agent to Fern's live docs and query it for any
   syntax or behavior you're unsure of. The endpoint works with any MCP client;
@@ -32,6 +33,7 @@ Fern's configuration evolves. Look things up rather than guessing.
 | Task | Read |
 |------|------|
 | Writing or editing a changelog entry | `references/changelog.md` |
+| Setting up a product switcher, adding a product, or refactoring nav into products | `references/products.md` |
 
 ## Core principles
 
diff --git a/fern/.well-known/skills/fern-docs/references/changelog.md b/fern/.well-known/skills/fern-docs/references/changelog.md
index 85f35d5c5..19e91aa79 100644
--- a/fern/.well-known/skills/fern-docs/references/changelog.md
+++ b/fern/.well-known/skills/fern-docs/references/changelog.md
@@ -3,7 +3,7 @@
 A changelog entry announces a shipped change to users. Each entry is a dated
 `.mdx` file; the filename date is the title. This reference covers how to *write*
 an entry. For setup (folder location, `docs.yml` wiring, RSS, navigation), see
-the official docs: https://buildwithfern.com/learn/docs/configuration/changelogs
+the official docs: https://buildwithfern.com/learn/docs/configuration/changelogs.md
 
 ## File and naming
 
diff --git a/fern/.well-known/skills/fern-docs/references/products.md b/fern/.well-known/skills/fern-docs/references/products.md
new file mode 100644
index 000000000..c9b21fa18
--- /dev/null
+++ b/fern/.well-known/skills/fern-docs/references/products.md
@@ -0,0 +1,121 @@
+# Products and the product switcher
+
+A product switcher lets one docs site host multiple products, each with its own
+`navigation`, `tabs`, `versions`, and API references. Use this when setting up
+product switching, adding a product to an existing switcher, or refactoring a
+single-product site into product format.
+
+**Prerequisite:** products are a Team/Enterprise feature. If the site isn't on
+one of those plans, the switcher won't render — direct the user to
+support@buildwithfern.com rather than debugging config.
+
+Canonical docs: https://buildwithfern.com/learn/docs/configuration/products.md
+(append `.md` to any Fern docs URL for clean markdown to fetch).
+
+## The model
+
+- Each **internal** product is a `.yml` file in `fern/products/` that holds that
+  product's `navigation` (and `tabs`, if used).
+- Each product is registered in the top-level `fern/docs.yml` under a `products:`
+  list.
+- The top-level `docs.yml` holds **no** `navigation:` or `tabs:` of its own once
+  products exist — that config lives in the product files.
+- **External** products link to a URL instead of site content. They're defined
+  entirely in `docs.yml` (no product `.yml`) and support no `navigation`/`tabs`.
+
+Paths inside a YAML file are **relative to that file**. Shared pages are
+referenced across products with `../pages/...`.
+
+## Register products in docs.yml
+
+```yaml
+products:
+  - display-name: Product A          # internal
+    path: ./products/product-a.yml
+    icon: fa-solid fa-leaf
+    slug: product-a                  # optional
+    subtitle: Product A subtitle     # optional
+
+  - display-name: Product C          # external
+    href: https://dashboard.example.com
+    subtitle: Product C subtitle
+    target: _blank                   # optional, opens in new tab
+```
+
+Per-product fields: `display-name` plus `path` (internal) or `href` (external).
+Optional for both: `image`, `icon`, `subtitle`. Internal-only: `slug`,
+`versions`. If both `image` and `icon` are set, `image` wins.
+
+**Icons** take three forms: a Font Awesome name (`fa-solid fa-rocket`), a
+relative image path (resolved against the YAML file it's written in — an icon in
+`fern/products/x.yml` resolves `./assets/i.svg` to `fern/products/assets/i.svg`),
+or an inline `"<svg>...</svg>"` string.
+
+## Product file
+
+Add the schema directive at the top for editor validation:
+
+```yaml
+# yaml-language-server: $schema=https://raw.githubusercontent.com/fern-api/fern/main/product-yml.schema.json
+navigation:
+  - section: Introduction
+    contents:
+      - page: Shared Resource
+        path: ../pages/shared-resource.mdx   # shared across products
+  - api: API Reference
+```
+
+With tabs, declare `tabs:` then a `navigation:` keyed by `tab:` — same shape as a
+single-product `docs.yml`, just moved into the product file.
+
+## Workflows
+
+**New switcher from scratch:** create `fern/products/`, add a `.yml` per product
+with its `navigation`/`tabs`, then add the `products:` list to `docs.yml`.
+
+**Add a product to an existing switcher:** create the new product `.yml`, then
+append one entry to the `products:` list. Existing products are untouched.
+
+**Refactor a single-product site into products** (most error-prone):
+
+1. Create `fern/products/` and a `.yml` per product.
+2. **Move** the existing top-level `navigation:` (and `tabs:`) out of `docs.yml`
+   and into the product file(s), splitting content across products as needed.
+3. Add the `products:` list to `docs.yml`.
+4. Confirm `docs.yml` no longer has a top-level `navigation:` or `tabs:`.
+5. Fix links: a product slug now prefixes every URL in that product (see below).
+
+## Footguns
+
+- **`navigation`/`tabs` must leave `docs.yml`.** Once products exist, top-level
+  `navigation:`/`tabs:` in `docs.yml` is wrong — it belongs in the product files.
+  For versioned products it moves one level deeper, into the *version* files, not
+  the product file.
+- **A product slug changes URLs.** Pages gain a `/<product-slug>/` segment, so
+  published URLs and existing internal links shift. Update internal links per the
+  **Links** section of `SKILL.md`, and set up [redirects](https://buildwithfern.com/learn/docs/seo/redirects.md)
+  for the old paths. A product with no `slug:` contributes no segment.
+- **Paths are relative to their own YAML file**, including icon image paths —
+  a frequent source of broken icons after moving files.
+- **External products** support `href`/`target` only — no `navigation`, `tabs`,
+  `slug`, or `versions`.
+
+## Related options
+
+Each extends the switcher; follow the link when a task needs it.
+
+- **[Versioning](https://buildwithfern.com/learn/docs/configuration/versions.md)** —
+  a `versions/` folder inside a product, one `.yml` per version holding that
+  version's `navigation`/`tabs`, registered under the product's `versions:` list.
+  The first version is the default and uses unversioned paths.
+- **[Site-level landing page](https://buildwithfern.com/learn/docs/configuration/site-level-settings.md)** —
+  a `landing-page:` in `docs.yml` that renders at the site root, independent of
+  any product.
+- **[Instance audiences](https://buildwithfern.com/learn/docs/configuration/site-level-settings.md)** —
+  tag products/versions with `audiences` to include or exclude them per
+  documentation instance.
+- **[Conditional content by product](https://buildwithfern.com/learn/docs/writing-content/components/if.md)** —
+  `<If products={["..."]}>…</If>` renders per current product.
+- **[Search scoping](https://buildwithfern.com/learn/docs/customization/search.md)**
+  and **[selector styling](https://buildwithfern.com/learn/docs/configuration/products.md)**
+  (`fern-product-selector`, `fern-version-selector` CSS classes).
diff --git a/fern/.well-known/skills/index.json b/fern/.well-known/skills/index.json
index 922ce2e1f..e66ad1597 100644
--- a/fern/.well-known/skills/index.json
+++ b/fern/.well-known/skills/index.json
@@ -3,7 +3,11 @@
     {
       "name": "fern-docs",
       "description": "Author and edit Fern documentation: MDX pages, navigation, docs.yml config, custom components, landing pages, and changelog entries. Use when working in a Fern docs repo (a fern/ directory with docs.yml). Routes to a detailed reference per task.",
-      "files": ["SKILL.md", "references/changelog.md"]
+      "files": [
+        "SKILL.md",
+        "references/changelog.md",
+        "references/products.md"
+      ]
     }
   ]
-}
+}
\ No newline at end of file

From 3b360714b0d7f5cb064a40626cc8c5e42d62b309 Mon Sep 17 00:00:00 2001
From: Mathieu Legault <mathieu@legault.me>
Date: Thu, 11 Jun 2026 17:31:59 -0400
Subject: [PATCH 3/4] Declare agent skills via docs.yml page-actions instead of
 well-known bundle

Replace the vendored fern/.well-known/skills/ bundle with a page-actions
config that points the Install-skills modal at fern-api/skills, so Fern's
own skills are installed directly from the source repo.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 fern/.well-known/skills/fern-docs/SKILL.md    | 146 ------------------
 .../skills/fern-docs/references/changelog.md  | 141 -----------------
 .../skills/fern-docs/references/products.md   | 121 ---------------
 fern/.well-known/skills/index.json            |  13 --
 fern/docs.yml                                 |  15 ++
 5 files changed, 15 insertions(+), 421 deletions(-)
 delete mode 100644 fern/.well-known/skills/fern-docs/SKILL.md
 delete mode 100644 fern/.well-known/skills/fern-docs/references/changelog.md
 delete mode 100644 fern/.well-known/skills/fern-docs/references/products.md
 delete mode 100644 fern/.well-known/skills/index.json

diff --git a/fern/.well-known/skills/fern-docs/SKILL.md b/fern/.well-known/skills/fern-docs/SKILL.md
deleted file mode 100644
index 0e813371d..000000000
--- a/fern/.well-known/skills/fern-docs/SKILL.md
+++ /dev/null
@@ -1,146 +0,0 @@
----
-name: fern-docs
-description: >-
-  Author and edit Fern documentation: MDX pages, navigation, docs.yml config,
-  custom components, landing pages, and changelog entries. Use when working in a
-  Fern docs repo (a fern/ directory with docs.yml). Routes to a detailed
-  reference per task.
----
-
-# Fern docs authoring
-
-Write and edit documentation on a Fern site. `SKILL.md` is the index: follow the
-principles and voice below, then read the `references/` file that matches the
-task before writing. Don't work from this page alone when a reference exists.
-
-## Fern resources
-
-Fern's configuration evolves. Look things up rather than guessing.
-
-- **Docs:** https://buildwithfern.com/learn/docs/getting-started/overview.md
-  (append `.md` to any docs URL for clean markdown to fetch)
-- **Page index:** https://buildwithfern.com/learn/llms.txt
-- **MCP server** — connect your agent to Fern's live docs and query it for any
-  syntax or behavior you're unsure of. The endpoint works with any MCP client;
-  for Claude Code:
-
-  ```bash
-  claude mcp add --transport http fern https://buildwithfern.com/learn/_mcp/server
-  ```
-
-## Routing
-
-| Task | Read |
-|------|------|
-| Writing or editing a changelog entry | `references/changelog.md` |
-| Setting up a product switcher, adding a product, or refactoring nav into products | `references/products.md` |
-
-## Core principles
-
-- **Write what the reader needs to succeed — no more.** Every sentence earns its place.
-- **Prefer editing over creating.** Search the repo for a page that already
-  covers the topic and update it instead of adding a duplicate.
-- **Make minimal, precise edits.** Don't rewrite a page when a paragraph fix will do.
-- **Push back when something seems wrong.** Explain why rather than complying silently.
-- **Ask when unclear.** Don't fill gaps with assumptions.
-- **Never fabricate.** If you don't know a config key or behavior, look it up
-  (MCP server or docs) or say so. Don't invent frontmatter or YAML fields.
-- **Cross-reference.** When you mention a concept documented elsewhere, link to it
-  so readers can find their way.
-
-## Voice
-
-Dry and direct. State requirements and behavior plainly.
-
-- **Cut hedges and nudges:** "just", "simply", "make sure you", "you'll want to".
-  Prefer "X requires Y" over "make sure you have Y so you can do X".
-- **Cut connective filler:** "so that", "in order to", "be sure to".
-- **Limit em dashes** to one per short paragraph; reach for a colon or
-  parentheses before a second.
-- **No conversational framing in callouts or steps.** "Localization requires the
-  latest CLI" beats "Localization is under active development, so make sure
-  you're on the latest CLI before configuring it."
-
-## Links
-
-Internal links are URL paths derived from **this repo's own `docs.yml` and page
-frontmatter** — not file paths on disk or relative paths. Nearly every edit
-touches a link, so get this right every time.
-
-A page URL is `<base-path>/<product-slug>/<rest>`:
-
-- **Base path** — the prefix in your docs URL (e.g. `/learn`, `/docs`; may be empty).
-- **Product slug** — the product's `slug` in `fern/docs.yml`. Omitted for a
-  product with no `slug:` (such as a default single Home product).
-- **`<rest>`** — found by step 1 or step 2 below.
-
-To find `<rest>`:
-
-1. **Open the target page and check its frontmatter for `slug:`.** A frontmatter
-   slug is **absolute within the product**: it *is* `<rest>` on its own, and it
-   replaces the entire section/folder hierarchy. The section's slug does not
-   appear. Do not walk the navigation.
-2. **Otherwise, walk `docs.yml`** within the product, from section through any
-   folders to the page. Each level contributes one slug:
-   - Its explicit `slug:` if set.
-   - Otherwise auto-derived from the display name: lowercased, spaces to
-     hyphens, special characters stripped (so `v3 (Latest)` becomes
-     `v-3-latest`). Auto-derivation isn't always obvious — verify, don't assume.
-   - In folder-based navigation, a page's slug comes from its **filename**, not
-     a display name (`quick-start.mdx` to `quick-start`).
-   - **Omit any level with `skip-slug: true`** — it contributes no segment.
-
-Example — page `./pages/ai/overview.mdx` under section "AI features", in product
-`docs`, base path `/learn`:
-
-- with frontmatter `slug: ai-ai` → `/learn/docs/ai-ai` (the `ai-features`
-  section slug is dropped)
-- with no frontmatter slug → `/learn/docs/ai-features/overview` (section
-  auto-slug `ai-features` + page auto-slug `overview`)
-
-Section slugs frequently differ from folder names, so never guess the URL from
-the directory layout. If you can't resolve a path from `docs.yml` and the page's
-frontmatter, say so rather than guessing.
-
-**Anchors** append `#heading`, and only resolve for real `##`/`###` Markdown
-headings — not for JSX title props like `<Step title>`, `<Tab title>`,
-`<Accordion title>`, or `<Card title>`.
-
-**Not internal links** (leave as-is): external `https://` URLs, image paths
-(`./images/...`), snippet includes (`<Markdown src="/snippets/..." />`), and
-same-page anchors (`#section`).
-
-## Cross-referencing
-
-When you document new functionality — a new page, or new behavior on an existing
-one — related pages usually need a pointer to it, or the new content is hard to
-find from where readers actually start. This applies to small edits too, not
-just new pages.
-
-- **One canonical home.** The full explanation lives on one page; every other
-  page that touches the topic links to it instead of restating it. If you're
-  copying more than a sentence or two onto another page, it belongs on the
-  canonical page.
-- **Find the targets.** Grep the docs for the feature name and one or two related
-  keywords, then read each hit and decide whether a pointer is warranted:
-
-  ```bash
-  grep -rln "<feature>\|<keyword>" fern --include="*.mdx"
-  ```
-
-  Common targets: pages for behavior the feature affects, adjacent feature pages,
-  and overview or landing pages.
-- **Use the lightest form that works:** an inline link inside an existing
-  sentence, then a `<Note>` for a secondary aside, then a new `##` section, then
-  a new page. Inline links and Notes add no maintenance surface; new pages and
-  sections do.
-- **Phrase inline links naturally — never "See [page]."** Put the link on a noun
-  phrase already in the sentence, not a tacked-on pointer sentence. Don't wrap a
-  lone link in a `<Tip>` whose only job is to host it.
-  - Good: "Each request counts against your [rate limit](...), which resets hourly."
-  - Bad: "Requests are rate limited. See the [rate limits reference](...) for details."
-  - Bad: a standalone `<Tip>` containing only "For more, see [rate limits](...)."
-- **Frame by function, not plumbing.** Contrast what each feature does ("X
-  decides A; Y decides B"), not that they share a config key or sit in the same
-  directory. If the only thing linking two features is the same YAML key, it's
-  not worth a cross-reference.
diff --git a/fern/.well-known/skills/fern-docs/references/changelog.md b/fern/.well-known/skills/fern-docs/references/changelog.md
deleted file mode 100644
index 19e91aa79..000000000
--- a/fern/.well-known/skills/fern-docs/references/changelog.md
+++ /dev/null
@@ -1,141 +0,0 @@
-# Writing changelog entries
-
-A changelog entry announces a shipped change to users. Each entry is a dated
-`.mdx` file; the filename date is the title. This reference covers how to *write*
-an entry. For setup (folder location, `docs.yml` wiring, RSS, navigation), see
-the official docs: https://buildwithfern.com/learn/docs/configuration/changelogs.md
-
-## File and naming
-
-- Entries go directly in the `changelog/` folder inside `fern/`. The folder must
-  be named `changelog` exactly. **No subdirectories** — nested files are silently
-  ignored.
-- One entry per date, named by date. Supported filename formats: `YYYY-MM-DD`
-  (preferred, sorts cleanly), `MM-DD-YYYY`, `MM-DD-YY`. Always use `.mdx` (Fern
-  also accepts `.md`, but `.mdx` is the standard and unlocks the component
-  library).
-- Sort order comes from the **filename date**, not frontmatter. A wrong filename
-  date puts the entry in the wrong position.
-- The date is the title. **Do not add an h1.**
-- If a file already exists for that date, add your feature as a new `##` section
-  in it rather than creating a second file.
-
-## Frontmatter tags
-
-Every entry needs a `tags` array. Tags drive the changelog's filtering, so use
-specific, descriptive tags users would search for — by product area, feature,
-release stage, platform, or impact:
-
-```mdx
----
-tags: ["voice-api", "breaking-change"]
----
-```
-
-**Reuse existing tags** for consistency before adding a new one:
-
-```bash
-grep -rh "^tags:" changelog/ | sort | uniq -c | sort -rn
-```
-
-A near-duplicate tag (`auth` when `security` already exists) fragments the
-filter.
-
-## Entry format
-
-```mdx
----
-tags: ["search"]
----
-
-## Filter search results by section
-
-You can now scope a search to a single section of your docs. Visitors pick a
-section from the search bar, and results are limited to pages under it.
-
-- Available on all plans.
-- Configured per docs instance.
-
-<Button intent="none" outlined rightIcon="arrow-right" href="/docs/customization/search">Read the docs</Button>
-```
-
-- **One `##` per feature.** No h1.
-- **Lead with the capability** — "You can now…" — not the implementation.
-- **Keep it short:** 2–6 sentences. Bullets for detail lists, not the whole entry.
-- **End with a Button** linking to the relevant docs page (recommended).
-- For dashboard/UI changes, give the click-path (**Settings** > **Page access**)
-  before the Button.
-
-## The docs-link Button
-
-The `href` is a docs **URL path** built from `docs.yml`, not a file path:
-`<base-path>/<section-slug>/<page-slug>`.
-
-```mdx
-<!-- WRONG: file path on disk -->         href="/changelog/../pages/search/configuration"
-<!-- WRONG: guessed from folder names --> href="/docs/search-config/configuration"
-<!-- CORRECT: built from docs.yml -->     href="/docs/customization/search"
-```
-
-See the **Links** section of `SKILL.md` for how to construct the path (base
-path, product slug, frontmatter slugs, `skip-slug`) from this repo's `docs.yml`.
-
-## Voice
-
-Dry and direct. Cut hedges ("just", "simply", "make sure you") and filler ("in
-order to", "so that"). At most one em dash per short paragraph.
-
-## Options
-
-Beyond a plain entry, the changelog supports:
-
-- **Overview page** — an `overview.mdx` in the `changelog/` folder renders above
-  all entries. `overview.mdx` is a reserved filename, so it is never treated as a
-  dated entry.
-- **Components are available but avoid them.** `.mdx` entries *can* use Fern's
-  component library (`<Note>`, `<Card>`, `<Accordion>`, etc.), but stacked across
-  a list of short entries they create visual noise. House rule: prose + the
-  `<Button>` only. Reach for another component only when it's genuinely the only
-  way to convey something.
-- **Tab or section** — the changelog is wired in `docs.yml` either as a tab
-  (`tabs: { changelog: { changelog: ./changelog } }`) or as a section
-  (`navigation: [ { changelog: ./changelog, title: ..., slug: ... } ]`).
-- **RSS feed** — generated automatically; append `.rss` to the changelog path
-  (e.g. `https://yourdomain.com/docs/changelog.rss`). No config needed.
-- **Per-entry permalinks** — each entry gets `…/changelog/YYYY/M/D` (month and
-  day are not zero-padded).
-
-For exact `docs.yml` syntax, see the official docs linked above.
-
-## Gotchas
-
-- **Folder name is exact and flat.** Not `changelogs`, not nested — files in
-  subfolders are silently dropped with no error.
-- **Slug must be recognized.** `fern check` (`valid-changelog-slug`) errors
-  unless the changelog's effective slug is one of: `changelog`, `changelogs`,
-  `release-notes`, `releasenotes`, `whats-new`, `whatsnew`.
-- **A section changelog can't live inside an `api:` block** in `docs.yml`.
-- **Only `tags` is a supported frontmatter field.** `title`, `date`, `hidden`,
-  etc. are not — the date comes from the filename. Don't add undocumented keys.
-- **The tag filter UI only renders when entries have tags.** No tags, no filter.
-
-## What not to do
-
-- Don't use h1 (`#`) — the date is the title.
-- Don't describe implementation details; describe the user benefit.
-- Don't invent a tag when an existing one fits.
-- Don't write the Button `href` from the file path on disk.
-- Don't use components other than the `<Button>` — prose keeps the entry list clean.
-
-## Checklist
-
-Mechanics to verify before considering an entry done:
-
-- [ ] File is in `fern/changelog/`, named with a supported date format, no subfolder.
-- [ ] `.mdx` extension.
-- [ ] Frontmatter has a `tags` array and no unsupported fields.
-- [ ] Tags reused from the existing set where one fits.
-- [ ] No h1; each feature is an `##`.
-- [ ] Opens with the user capability; 2–6 sentences per feature.
-- [ ] Button present per feature, `href` a docs URL path (not a disk path).
-- [ ] Dashboard/UI changes include the click-path before the Button.
diff --git a/fern/.well-known/skills/fern-docs/references/products.md b/fern/.well-known/skills/fern-docs/references/products.md
deleted file mode 100644
index c9b21fa18..000000000
--- a/fern/.well-known/skills/fern-docs/references/products.md
+++ /dev/null
@@ -1,121 +0,0 @@
-# Products and the product switcher
-
-A product switcher lets one docs site host multiple products, each with its own
-`navigation`, `tabs`, `versions`, and API references. Use this when setting up
-product switching, adding a product to an existing switcher, or refactoring a
-single-product site into product format.
-
-**Prerequisite:** products are a Team/Enterprise feature. If the site isn't on
-one of those plans, the switcher won't render — direct the user to
-support@buildwithfern.com rather than debugging config.
-
-Canonical docs: https://buildwithfern.com/learn/docs/configuration/products.md
-(append `.md` to any Fern docs URL for clean markdown to fetch).
-
-## The model
-
-- Each **internal** product is a `.yml` file in `fern/products/` that holds that
-  product's `navigation` (and `tabs`, if used).
-- Each product is registered in the top-level `fern/docs.yml` under a `products:`
-  list.
-- The top-level `docs.yml` holds **no** `navigation:` or `tabs:` of its own once
-  products exist — that config lives in the product files.
-- **External** products link to a URL instead of site content. They're defined
-  entirely in `docs.yml` (no product `.yml`) and support no `navigation`/`tabs`.
-
-Paths inside a YAML file are **relative to that file**. Shared pages are
-referenced across products with `../pages/...`.
-
-## Register products in docs.yml
-
-```yaml
-products:
-  - display-name: Product A          # internal
-    path: ./products/product-a.yml
-    icon: fa-solid fa-leaf
-    slug: product-a                  # optional
-    subtitle: Product A subtitle     # optional
-
-  - display-name: Product C          # external
-    href: https://dashboard.example.com
-    subtitle: Product C subtitle
-    target: _blank                   # optional, opens in new tab
-```
-
-Per-product fields: `display-name` plus `path` (internal) or `href` (external).
-Optional for both: `image`, `icon`, `subtitle`. Internal-only: `slug`,
-`versions`. If both `image` and `icon` are set, `image` wins.
-
-**Icons** take three forms: a Font Awesome name (`fa-solid fa-rocket`), a
-relative image path (resolved against the YAML file it's written in — an icon in
-`fern/products/x.yml` resolves `./assets/i.svg` to `fern/products/assets/i.svg`),
-or an inline `"<svg>...</svg>"` string.
-
-## Product file
-
-Add the schema directive at the top for editor validation:
-
-```yaml
-# yaml-language-server: $schema=https://raw.githubusercontent.com/fern-api/fern/main/product-yml.schema.json
-navigation:
-  - section: Introduction
-    contents:
-      - page: Shared Resource
-        path: ../pages/shared-resource.mdx   # shared across products
-  - api: API Reference
-```
-
-With tabs, declare `tabs:` then a `navigation:` keyed by `tab:` — same shape as a
-single-product `docs.yml`, just moved into the product file.
-
-## Workflows
-
-**New switcher from scratch:** create `fern/products/`, add a `.yml` per product
-with its `navigation`/`tabs`, then add the `products:` list to `docs.yml`.
-
-**Add a product to an existing switcher:** create the new product `.yml`, then
-append one entry to the `products:` list. Existing products are untouched.
-
-**Refactor a single-product site into products** (most error-prone):
-
-1. Create `fern/products/` and a `.yml` per product.
-2. **Move** the existing top-level `navigation:` (and `tabs:`) out of `docs.yml`
-   and into the product file(s), splitting content across products as needed.
-3. Add the `products:` list to `docs.yml`.
-4. Confirm `docs.yml` no longer has a top-level `navigation:` or `tabs:`.
-5. Fix links: a product slug now prefixes every URL in that product (see below).
-
-## Footguns
-
-- **`navigation`/`tabs` must leave `docs.yml`.** Once products exist, top-level
-  `navigation:`/`tabs:` in `docs.yml` is wrong — it belongs in the product files.
-  For versioned products it moves one level deeper, into the *version* files, not
-  the product file.
-- **A product slug changes URLs.** Pages gain a `/<product-slug>/` segment, so
-  published URLs and existing internal links shift. Update internal links per the
-  **Links** section of `SKILL.md`, and set up [redirects](https://buildwithfern.com/learn/docs/seo/redirects.md)
-  for the old paths. A product with no `slug:` contributes no segment.
-- **Paths are relative to their own YAML file**, including icon image paths —
-  a frequent source of broken icons after moving files.
-- **External products** support `href`/`target` only — no `navigation`, `tabs`,
-  `slug`, or `versions`.
-
-## Related options
-
-Each extends the switcher; follow the link when a task needs it.
-
-- **[Versioning](https://buildwithfern.com/learn/docs/configuration/versions.md)** —
-  a `versions/` folder inside a product, one `.yml` per version holding that
-  version's `navigation`/`tabs`, registered under the product's `versions:` list.
-  The first version is the default and uses unversioned paths.
-- **[Site-level landing page](https://buildwithfern.com/learn/docs/configuration/site-level-settings.md)** —
-  a `landing-page:` in `docs.yml` that renders at the site root, independent of
-  any product.
-- **[Instance audiences](https://buildwithfern.com/learn/docs/configuration/site-level-settings.md)** —
-  tag products/versions with `audiences` to include or exclude them per
-  documentation instance.
-- **[Conditional content by product](https://buildwithfern.com/learn/docs/writing-content/components/if.md)** —
-  `<If products={["..."]}>…</If>` renders per current product.
-- **[Search scoping](https://buildwithfern.com/learn/docs/customization/search.md)**
-  and **[selector styling](https://buildwithfern.com/learn/docs/configuration/products.md)**
-  (`fern-product-selector`, `fern-version-selector` CSS classes).
diff --git a/fern/.well-known/skills/index.json b/fern/.well-known/skills/index.json
deleted file mode 100644
index e66ad1597..000000000
--- a/fern/.well-known/skills/index.json
+++ /dev/null
@@ -1,13 +0,0 @@
-{
-  "skills": [
-    {
-      "name": "fern-docs",
-      "description": "Author and edit Fern documentation: MDX pages, navigation, docs.yml config, custom components, landing pages, and changelog entries. Use when working in a Fern docs repo (a fern/ directory with docs.yml). Routes to a detailed reference per task.",
-      "files": [
-        "SKILL.md",
-        "references/changelog.md",
-        "references/products.md"
-      ]
-    }
-  ]
-}
\ No newline at end of file
diff --git a/fern/docs.yml b/fern/docs.yml
index 1ad76ba12..da5314f00 100644
--- a/fern/docs.yml
+++ b/fern/docs.yml
@@ -166,6 +166,21 @@ theme:
   page-actions: toolbar
   footer-nav: minimal
 
+page-actions:
+  options:
+    skills:
+      title: Install agent skills
+      description: Skills for authoring Fern documentation, maintained in our open-source skills repo.
+      learn-more-url: https://buildwithfern.com/learn/docs/ai/agent-skills
+      repository: https://github.com/fern-api/skills
+      install-command: npx skills add fern-api/skills
+      skills:
+        - name: fern-docs
+          description: >-
+            Author and edit Fern documentation: MDX pages, navigation, docs.yml
+            config, custom components, landing pages, and changelog entries.
+          url: https://github.com/fern-api/skills/tree/main/skills/fern-docs
+
 settings:
   http-snippets:
     - curl

From b5b1d3e7dc459885979d120f98753d1bfa55d77c Mon Sep 17 00:00:00 2001
From: Mathieu Legault <mathieu@legault.me>
Date: Thu, 11 Jun 2026 21:21:22 -0400
Subject: [PATCH 4/4] Bump pinned Fern CLI to 5.47.1 for skills page-action
 support

The skills page-action config requires CLI >= 5.47.0; the repo pinned
5.7.5, which rejected page-actions.options.skills. Bumping also enables
a newer changelog-feed URL validation rule, so give the self-hosted
"Releases" changelog an explicit release-notes slug (with a redirect
from the old /releases URL and updated internal links).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 fern/docs.yml                                               | 2 ++
 fern/fern.config.json                                       | 2 +-
 fern/products/docs/docs.yml                                 | 1 +
 fern/products/docs/pages/self-hosted/self-hosted-set-up.mdx | 2 +-
 fern/products/docs/pages/self-hosted/self-hosted.mdx        | 2 +-
 5 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/fern/docs.yml b/fern/docs.yml
index da5314f00..0d78ac0aa 100644
--- a/fern/docs.yml
+++ b/fern/docs.yml
@@ -554,6 +554,8 @@ redirects:
   # Docs self-hosted / alternatives
   - source: /learn/docs/enterprise/self-hosted
     destination: /learn/docs/self-hosted/overview
+  - source: /learn/docs/self-hosted/releases
+    destination: /learn/docs/self-hosted/release-notes
   - source: /learn/docs/alternatives/mintlify
     destination: /learn/docs/getting-started/overview
 
diff --git a/fern/fern.config.json b/fern/fern.config.json
index 788fb6032..87b21f568 100644
--- a/fern/fern.config.json
+++ b/fern/fern.config.json
@@ -1,4 +1,4 @@
 {
   "organization": "fern",
-  "version": "5.7.5"
+  "version": "5.47.1"
 }
diff --git a/fern/products/docs/docs.yml b/fern/products/docs/docs.yml
index 6e636477e..e1aa072b7 100644
--- a/fern/products/docs/docs.yml
+++ b/fern/products/docs/docs.yml
@@ -405,6 +405,7 @@ navigation:
         path: ./pages/self-hosted/health-check-endpoints.mdx
       - changelog: ./pages/self-hosted/changelog
         title: Releases
+        slug: release-notes
   - section: Analytics & integrations
     slug: integrations
     collapsed: true
diff --git a/fern/products/docs/pages/self-hosted/self-hosted-set-up.mdx b/fern/products/docs/pages/self-hosted/self-hosted-set-up.mdx
index 8471f0996..965a50168 100644
--- a/fern/products/docs/pages/self-hosted/self-hosted-set-up.mdx
+++ b/fern/products/docs/pages/self-hosted/self-hosted-set-up.mdx
@@ -80,7 +80,7 @@ RUN fern-generate
 </Info>
 
 <Tip>
-See [recent releases](/learn/docs/self-hosted/releases) to pin to a specific version instead of `:latest`.
+See [recent releases](/learn/docs/self-hosted/release-notes) to pin to a specific version instead of `:latest`.
 </Tip>
 
 </Step>
diff --git a/fern/products/docs/pages/self-hosted/self-hosted.mdx b/fern/products/docs/pages/self-hosted/self-hosted.mdx
index 6f7518955..1382a3899 100644
--- a/fern/products/docs/pages/self-hosted/self-hosted.mdx
+++ b/fern/products/docs/pages/self-hosted/self-hosted.mdx
@@ -78,7 +78,7 @@ Fern provides your documentation site as a ready-to-run Docker container that yo
 1. **Upload your fern folder** - Add your documentation source files to the container
 1. **Run the container** - Start your local server using standard Docker commands
 1. **Deploy** - Set up your server environment and publish the documentation
-1. **Receive updated Docker images** - Fern [releases new versions of the Docker image](/learn/docs/self-hosted/releases) that your team can evaluate and deploy when ready. 
+1. **Receive updated Docker images** - Fern [releases new versions of the Docker image](/learn/docs/self-hosted/release-notes) that your team can evaluate and deploy when ready. 
 
 ### Architecture diagram