diff --git a/fern/products/cli-api-reference/cli-changelog/2026-02-24.mdx b/fern/products/cli-api-reference/cli-changelog/2026-02-24.mdx
index 9d69375a5..492c904c2 100644
--- a/fern/products/cli-api-reference/cli-changelog/2026-02-24.mdx
+++ b/fern/products/cli-api-reference/cli-changelog/2026-02-24.mdx
@@ -1,3 +1,35 @@
+## 3.86.0
+**`(feat):`** Add Python library docs generation. You can now generate reference documentation
+for Python libraries directly from source code. Configure a `libraries` section in `docs.yml`
+pointing to a GitHub repository, and run `fern generate --docs` to produce MDX pages with
+full module, class, and function documentation.
+
+The CLI sends the repository URL to the Fern registry (FDR), which clones the repo, parses
+the Python source into a library IR, and uploads the result to S3. The CLI then downloads
+the IR and runs a local MDX generator that produces per-module pages with summary tables,
+detailed API signatures, cross-linked types, and a `_navigation.yml` file for automatic
+navigation integration.
+
+Configuration example in `docs.yml`:
+```yaml
+libraries:
+  my-sdk:
+    input:
+      git: https://github.com/acme/sdk-python
+    output:
+      path: ./static/sdk-docs
+    lang: python
+```
+
+Reference the generated docs in your navigation with:
+```yaml
+- library: my-sdk
+  title: Python SDK Reference
+```
+
+Use `--library <name>` to generate docs for a single library, or omit it to generate all configured libraries.
+
+
 ## 3.85.6
 **`(chore):`** Complete document-level `webhook-signature` configuration parsing. Adds validation for webhook
 signature configs (algorithms, encodings, timestamp settings, JWKS consistency).
diff --git a/fern/products/dashboard/pages/overview.mdx b/fern/products/dashboard/pages/overview.mdx
index 16222388f..3f0e2c198 100644
--- a/fern/products/dashboard/pages/overview.mdx
+++ b/fern/products/dashboard/pages/overview.mdx
@@ -144,5 +144,12 @@ Manage your documentation site and team collaboration:
   >
     Restrict access to your docs site with a shared password.
   </Card>
+  <Card
+    title="Unpublish a site"
+    icon="regular eye-slash"
+    href="/learn/docs/preview-publish/publishing-your-docs#unpublishing-your-docs"
+  >
+    Temporarily take a site offline without deleting it.
+  </Card>
 </CardGroup>
 
diff --git a/fern/products/docs/pages/getting-started/publishing-your-docs.mdx b/fern/products/docs/pages/getting-started/publishing-your-docs.mdx
index a6d005ff6..cf79485cf 100644
--- a/fern/products/docs/pages/getting-started/publishing-your-docs.mdx
+++ b/fern/products/docs/pages/getting-started/publishing-your-docs.mdx
@@ -191,7 +191,24 @@ If you need access to your docs offline or would like to host your docs on your
 
 ## Unpublishing your docs
 
-If you need to take down your docs site, you can't directly unpublish it. However, you can replace your content with an empty site to remove all your documentation.
+You can unpublish a docs site directly from the [Fern Dashboard](https://dashboard.buildwithfern.com). Unpublishing makes the domain no longer publicly accessible, but does not delete the site — you can republish it at any time.
+
+<Steps>
+<Step title="Navigate to your site settings">
+Open the [Fern Dashboard](https://dashboard.buildwithfern.com) and go to the **Settings** page for the site you want to unpublish.
+</Step>
+<Step title="Unpublish the site">
+Click the **Unpublish** button. Your site's domain will no longer be publicly accessible.
+</Step>
+</Steps>
+
+<Note>
+Unpublishing is useful for creating draft sites or temporarily hiding a site from public view. Since the site is not deleted, you can republish it whenever you're ready.
+</Note>
+
+<Accordion title="Alternative: Replace content with an empty site">
+
+If you prefer, you can also replace your content with an empty site to remove all documentation while keeping the domain active.
 
 <Steps>
 <Step title="Clear your navigation">
@@ -208,4 +225,5 @@ navigation: []
 Publish the updated configuration by running `fern generate --docs`. This will remove all content from your site, and users visiting any page will see a 404 error.
 </Step>
 </Steps>
+</Accordion>