blume 0.5.0 → 0.5.2

package/dist/types/core/schema.d.ts

@@ -2041,16 +2041,6 @@ export declare const blumeConfigSchema: z.ZodObject<{
         }>, "many">>;
         /** Explicit sidebar override; when omitted the sidebar is generated. */
         sidebar: z.ZodOptional<z.ZodArray<z.ZodType<SidebarItemConfig, z.ZodTypeDef, SidebarItemConfig>, "many">>;
-        sidebarVariants: z.ZodDefault<z.ZodArray<z.ZodObject<{
-            items: z.ZodDefault<z.ZodArray<z.ZodType<SidebarItemConfig, z.ZodTypeDef, SidebarItemConfig>, "many">>;
-            path: z.ZodString;
-        }, "strict", z.ZodTypeAny, {
-            path: string;
-            items: SidebarItemConfig[];
-        }, {
-            path: string;
-            items?: SidebarItemConfig[] | undefined;
-        }>, "many">>;
         tabs: z.ZodOptional<z.ZodArray<z.ZodObject<{
             icon: z.ZodOptional<z.ZodString>;
             items: z.ZodOptional<z.ZodArray<z.ZodObject<{
@@ -2127,10 +2117,6 @@ export declare const blumeConfigSchema: z.ZodObject<{
             }[];
             kind: "version" | "dropdown" | "language" | "product";
         }[];
-        sidebarVariants: {
-            path: string;
-            items: SidebarItemConfig[];
-        }[];
         sidebar?: SidebarItemConfig[] | undefined;
         tabs?: {
             path: string;
@@ -2175,10 +2161,6 @@ export declare const blumeConfigSchema: z.ZodObject<{
                 tag?: string | undefined;
             }[] | undefined;
         }[] | undefined;
-        sidebarVariants?: {
-            path: string;
-            items?: SidebarItemConfig[] | undefined;
-        }[] | undefined;
         tabs?: {
             path: string;
             label: string;
@@ -2811,10 +2793,6 @@ export declare const blumeConfigSchema: z.ZodObject<{
             }[];
             kind: "version" | "dropdown" | "language" | "product";
         }[];
-        sidebarVariants: {
-            path: string;
-            items: SidebarItemConfig[];
-        }[];
         sidebar?: SidebarItemConfig[] | undefined;
         tabs?: {
             path: string;
@@ -3195,10 +3173,6 @@ export declare const blumeConfigSchema: z.ZodObject<{
                 tag?: string | undefined;
             }[] | undefined;
         }[] | undefined;
-        sidebarVariants?: {
-            path: string;
-            items?: SidebarItemConfig[] | undefined;
-        }[] | undefined;
         tabs?: {
             path: string;
             label: string;

package/dist/types/core/types.d.ts

@@ -168,11 +168,6 @@ export interface NavSelector {
     kind: "dropdown" | "language" | "product" | "version";
     items: NavSelectorItem[];
 }
-/** Sidebar tree used when the current route belongs to a nav partition. */
-export interface NavSidebarVariant {
-    path: string;
-    sidebar: NavNode[];
-}
 /** Chrome overrides used when the current route belongs to a nav partition. */
 export interface NavChromeVariant {
     path: string;
@@ -184,7 +179,6 @@ export interface Navigation {
     selectors: NavSelector[];
     chromeVariants: NavChromeVariant[];
     sidebar: NavNode[];
-    sidebarVariants: NavSidebarVariant[];
     /** Repo URL for the header link, or null when hidden (`navigation.repo`). */
     repoUrl?: string | null;
 }

package/dist/types/migrate/mintlify/config.d.ts

@@ -1,2 +1,16 @@
 import type { BlumeConfig } from "../../core/schema.ts";
+type JsonObject = Record<string, unknown>;
+export interface MintlifyRedirectPartition {
+    /** Static redirects Blume can honor, translated to Blume's `from`/`to` shape. */
+    kept: NonNullable<BlumeConfig["redirects"]>;
+    /** Source paths of dynamic redirects dropped because Blume can't model them. */
+    dropped: string[];
+}
+/**
+ * Split a spec's redirects into the static ones Blume emits and the dynamic
+ * (wildcard/param) ones it drops. Keeping a dynamic redirect crashes the Astro
+ * build, so the migrator surfaces the dropped sources as a warning instead.
+ */
+export declare const partitionMintlifyRedirects: (spec: JsonObject) => MintlifyRedirectPartition;
 export declare const loadMintlifyConfig: (root: string, file: string) => Promise<BlumeConfig>;
+export {};

package/docs/01-quickstart.mdx

@@ -51,7 +51,9 @@ Go from an empty folder to a running docs site in a few commands. Blume needs **
   </Step>
 </Steps>
 
-:::tip Blume works with any package manager and never requires you to set up Astro or Tailwind yourself. :::
+:::tip
+Blume works with any package manager and never requires you to set up Astro or Tailwind yourself.
+:::
 
 ## Write your first page
 
@@ -65,7 +67,9 @@ description: Welcome to my docs.
 
 Welcome! Use **Markdown** and built-in components — no imports required:
 
-:::note Blume ships callouts, cards, tabs, steps, and more. :::
+:::note
+Blume ships callouts, cards, tabs, steps, and more.
+:::
 ```
 
 Save it, and the dev server reloads instantly. Navigation, search, and page metadata are inferred from your files as you add them — keep writing, and the site keeps up.

package/docs/02-deployment.mdx

@@ -86,7 +86,9 @@ On **Vercel**, **Netlify**, and **Cloudflare Pages**, Blume picks the matching a
 
 A server build includes everything a static build does, plus any Astro endpoints or middleware you add. The `node` adapter produces a standalone server you can run directly.
 
-:::note Server features have their own configuration — for example, Ask AI needs a model API key. See the [AI guide](/docs/configuration/ai) for setup. :::
+:::note
+Server features have their own configuration — for example, Ask AI needs a model API key. See the [AI guide](/docs/configuration/ai) for setup.
+:::
 
 ## Redirects
 

package/docs/advanced/api-reference.mdx

@@ -14,7 +14,9 @@ openapi: {
 
 That mounts the reference at `/reference` (an overview page) with each operation at `/reference/<tag>/<operation>`, and adds a header tab. The `spec` is either an `http(s)` URL or a path to a local file in your project. Blume parses it with [Scalar's OpenAPI parser](https://github.com/scalar/scalar) — Swagger 2.0 and OpenAPI 3.0 specs are upgraded to 3.1 automatically.
 
-:::note Operations are indexed for search by their **summary and tag**. The rendered schema tables and code samples aren't full-text indexed; search matches an operation's title and section, then links to its own page. :::
+:::note
+Operations are indexed for search by their **summary and tag**. The rendered schema tables and code samples aren't full-text indexed; search matches an operation's title and section, then links to its own page.
+:::
 
 ## A local spec
 
@@ -94,4 +96,6 @@ asyncapi: {
 }
 ```
 
-:::warning Scalar's AsyncAPI support is still a work in progress — it renders channels, operations, messages, and a Models section, but there's **no interactive playground** for events yet. It improves upstream over time. :::
+:::warning
+Scalar's AsyncAPI support is still a work in progress — it renders channels, operations, messages, and a Models section, but there's **no interactive playground** for events yet. It improves upstream over time.
+:::

package/docs/advanced/bridge.mdx

@@ -26,7 +26,9 @@ Bridge mode is entirely automatic, gated on two conditions:
 
 With both true, Blume treats the Mintlify config as its source of truth for that run.
 
-:::note Bridge mode applies to `blume build` too, not just `blume dev` — you can produce a static site from an unconverted Mintlify project. Only `blume dev` prints the detection notice. :::
+:::note
+Bridge mode applies to `blume build` too, not just `blume dev` — you can produce a static site from an unconverted Mintlify project. Only `blume dev` prints the detection notice.
+:::
 
 ## What happens under the hood
 

package/docs/advanced/custom-pages.mdx

@@ -260,7 +260,9 @@ import data from "blume:data";
 </RootLayout>
 ```
 
-:::note `RootLayout` is part of the generated runtime, so its props can change between releases. When you want a layout that's fully yours, [`blume eject`](/docs/configuration/customization#eject) turns `.blume/` into a standard Astro project you own outright. :::
+:::note
+`RootLayout` is part of the generated runtime, so its props can change between releases. When you want a layout that's fully yours, [`blume eject`](/docs/configuration/customization#eject) turns `.blume/` into a standard Astro project you own outright.
+:::
 
 ## 404 page
 

package/docs/advanced/migrate.mdx

@@ -18,7 +18,9 @@ The `<tool>` is the framework you're coming from:
 | [Nextra](#nextra) | `content/` or `pages/` + `_meta` | `blume migrate nextra` |
 | [Starlight](#starlight) | `src/content/docs` + `astro.config.*` | `blume migrate starlight` |
 
-:::warning A migration **rewrites files in place** — pages, config, navigation, and assets. Commit (or stash) your work first so you can review the diff and roll back cleanly. :::
+:::warning
+A migration **rewrites files in place** — pages, config, navigation, and assets. Commit (or stash) your work first so you can review the diff and roll back cleanly.
+:::
 
 ## What a migration does
 
@@ -62,7 +64,9 @@ Reads `docs.json` (or legacy `mint.json`) and rewrites every page **in place**
 - Fonts map to [`theme.fonts`](/docs/configuration/theming) when the family is one of Blume's curated Google Fonts (`fonts.family`, or a `heading`/`body` split); a family outside that set is warned about, not guessed. Header links (`navbar.links`/`navbar.primary`) and footer socials (`footer.socials`) have no `blume.config` equivalent yet, so they're reported as warnings rather than dropped silently — re-add them with [`navigation.tabs`](/docs/content/navigation) or a Header/Footer [layout override](/docs/advanced/custom-pages). The contextual page menu and last-updated timestamp are already Blume defaults.
 - Field components — [`<ParamField>`, `<ResponseField>`, `<RequestField>`](/docs/content/components#api-fields) — render natively via Blume's compat components, so hand-written CLI/SDK/endpoint field docs carry over unchanged. Any remaining component with no Blume equivalent (e.g. `<Update>`) is flagged for manual review.
 
-:::tip Want to preview Blume against a Mintlify codebase **without** rewriting anything? Run `blume dev` with no config and Blume serves `docs.json` as-is in [Bridge mode](/docs/advanced/bridge). Migrate when you're ready to commit. :::
+:::tip
+Want to preview Blume against a Mintlify codebase **without** rewriting anything? Run `blume dev` with no config and Blume serves `docs.json` as-is in [Bridge mode](/docs/advanced/bridge). Migrate when you're ready to commit.
+:::
 
 ### Fumadocs
 

package/docs/configuration/ai.mdx

@@ -125,7 +125,9 @@ ai: {
 
 Set `apiKeyEnv` (and, for the named providers, `baseUrl`) on any backend to point at a different env var or proxy.
 
-:::note **Inkeep** answers from the content you've indexed in the Inkeep dashboard — it runs its own retrieval — so Blume leaves it ungrounded. Every other backend is [grounded](#grounding) in this site's pages. :::
+:::note
+**Inkeep** answers from the content you've indexed in the Inkeep dashboard — it runs its own retrieval — so Blume leaves it ungrounded. Every other backend is [grounded](#grounding) in this site's pages.
+:::
 
 Keys are read with `process.env`, which covers the Node, Vercel, and Netlify adapters. On Cloudflare, expose the key through the platform's [runtime binding](https://docs.astro.build/en/guides/integrations-guide/cloudflare/#environment-variables-and-secrets). Enabling Ask AI also turns on React for the in-page island — see [Customization](/docs/configuration/customization#interactive-islands).
 

package/docs/configuration/analytics.mdx

@@ -7,7 +7,9 @@ Blume injects analytics for you from a single `analytics` block in `blume.config
 
 Analytics loads in **production builds only**. The scripts are emitted by `blume build`, never by `blume dev`, so local traffic never reaches your dashboards and you don't need a separate "development" project.
 
-:::note Analytics is opt-in. With no `analytics` block, Blume injects nothing. :::
+:::note
+Analytics is opt-in. With no `analytics` block, Blume injects nothing.
+:::
 
 ## Vercel Web Analytics
 

package/docs/configuration/export.mdx

@@ -30,7 +30,9 @@ Any format you omit (or set to `false`) is left out of the menu. With both off
 
 Because it prints the live, fully-styled page, the result keeps crisp, selectable text, real fonts, and syntax-highlighted code. It needs no dependencies and works the same in dev, in production, and on static hosts.
 
-:::note PDF export goes through the browser's native print dialog, so the exact "Save as PDF" wording and options depend on the browser. Enable **Background graphics** in the dialog to keep code-block and callout backgrounds. :::
+:::note
+PDF export goes through the browser's native print dialog, so the exact "Save as PDF" wording and options depend on the browser. Enable **Background graphics** in the dialog to keep code-block and callout backgrounds.
+:::
 
 ## EPUB
 
@@ -42,4 +44,6 @@ To keep the file readable on a device with no stylesheet or JavaScript of its ow
 
 Both formats export the **single page** a reader is viewing — not the whole site — which matches where the action lives, beneath that page's table of contents.
 
-:::note In an EPUB there's no JavaScript to switch tabs, so tabbed content — like [package-install](/docs/content/syntax) blocks and code groups — is expanded to show every panel at once. Client-rendered embeds such as Mermaid diagrams aren't included. :::
+:::note
+In an EPUB there's no JavaScript to switch tabs, so tabbed content — like [package-install](/docs/content/syntax) blocks and code groups — is expanded to show every panel at once. Client-rendered embeds such as Mermaid diagrams aren't included.
+:::

package/docs/configuration/seo.mdx

@@ -94,7 +94,9 @@ seo:
 ---
 ```
 
-:::note OG rendering uses hex internally, so an `oklch` custom accent falls back to the default. Use a named accent (`blue`, `teal`, …) or a hex value for custom cards. :::
+:::note
+OG rendering uses hex internally, so an `oklch` custom accent falls back to the default. Use a named accent (`blue`, `teal`, …) or a hex value for custom cards.
+:::
 
 `seo.image` is frontmatter, so it only covers Markdown and MDX content. To give a custom [`.astro` page](/docs/advanced/custom-pages) its own social image — a marketing home or landing page, and the way to give the home page alone a bespoke share image — pass the `ogImage` prop to `PageLayout`.
 

package/docs/content/i18n.mdx

@@ -22,7 +22,9 @@ i18n: {
 
 Each locale has a `code` (used in URLs), a `label` (shown in the language switcher), and an optional `dir` for right-to-left scripts (`"ltr"` by default).
 
-:::tip Migrating from Mintlify? [`blume migrate mintlify`](/docs/advanced/migrate) reads `navigation.languages[]` and writes the `i18n` block for you — the `default: true` language becomes `defaultLocale`, and translated folders already match Blume's layout. :::
+:::tip
+Migrating from Mintlify? [`blume migrate mintlify`](/docs/advanced/migrate) reads `navigation.languages[]` and writes the `i18n` block for you — the `default: true` language becomes `defaultLocale`, and translated folders already match Blume's layout.
+:::
 
 ## Organize translated content
 
@@ -98,7 +100,9 @@ i18n: {
 
 Fallback pages are excluded from the search index and aren't advertised as real translations in `hreflang`, so untranslated content doesn't compete for ranking. They still appear in that locale's sidebar, so navigation stays complete — a reader can reach every page in any language.
 
-:::tip Start by translating your most important pages — the homepage, quickstart, and top guides — and let the rest fall back. You can fill in translations over time without breaking any links. :::
+:::tip
+Start by translating your most important pages — the homepage, quickstart, and top guides — and let the rest fall back. You can fill in translations over time without breaking any links.
+:::
 
 ## The language switcher
 

package/docs/content/islands.mdx

@@ -24,7 +24,9 @@ Here's a live counter: <Counter />
 
 The filename is the component name, so it **must be a PascalCase identifier** — letters, digits, and underscores only (`Counter.tsx` → `<Counter />`). Lowercase filenames, names with dashes/dots/spaces (like `Time-Picker.tsx`), and two islands that resolve to the same name are skipped with a build warning.
 
-:::note Islands are for **interactive** UI. For a static component you reuse across pages (a styled callout, a pricing table), use an [MDX override](/docs/configuration/customization) instead — it ships no JavaScript. :::
+:::note
+Islands are for **interactive** UI. For a static component you reuse across pages (a styled callout, a pricing table), use an [MDX override](/docs/configuration/customization) instead — it ships no JavaScript.
+:::
 
 ## Registering islands in `components.ts`
 
@@ -98,7 +100,9 @@ const on = ref(false);
 
 Props you pass in MDX (`<Counter start={5} />`) are forwarded to the component, and children (`<Counter>label</Counter>`) arrive as the default slot.
 
-:::tip Islands hydrate on the client, so anything you pass as a prop must be serializable — strings, numbers, plain objects, not functions. :::
+:::tip
+Islands hydrate on the client, so anything you pass as a prop must be serializable — strings, numbers, plain objects, not functions.
+:::
 
 ## Hooks
 

package/docs/content/meta.mdx

@@ -45,7 +45,9 @@ The `pages` array lists children by slug — the folder or file name with its nu
 - **`group`** — a collapsible `<details>` disclosure. Pair it with `collapsed` to set the initial state; a group containing the current page always starts open.
 - **`page`** — a single row that, when clicked, slides the sidebar into a sub-panel showing only that group's items, with a back arrow at the top. The panel is route-aware, so landing directly on a page inside the group opens straight to it.
 
-:::tip `page` mode keeps deep sections tidy — reach for it when a group has many children and you'd rather drill into it than scroll past it. :::
+:::tip
+`page` mode keeps deep sections tidy — reach for it when a group has many children and you'd rather drill into it than scroll past it.
+:::
 
 `display` works the same on a group in an [explicit sidebar](/docs/content/navigation#explicit-sidebar) config.
 

package/docs/content/syntax.mdx

@@ -242,7 +242,9 @@ config.title;
 ```
 ````
 
-:::note Hide the language icons or wrap long lines instead of scrolling with `markdown: { code: { icons: false, wrap: true } }` in `blume.config.ts`. :::
+:::note
+Hide the language icons or wrap long lines instead of scrolling with `markdown: { code: { icons: false, wrap: true } }` in `blume.config.ts`.
+:::
 
 ## Package install
 
@@ -288,60 +290,82 @@ Callouts pull a reader's attention to context, advice, or risk. Write them as `:
 
 Neutral, supporting context the reader should keep in mind.
 
-:::note Blume regenerates `.blume/` on every run — never edit it by hand. :::
+:::note
+Blume regenerates `.blume/` on every run — never edit it by hand.
+:::
 
 ```md
-:::note Blume regenerates `.blume/` on every run — never edit it by hand. :::
+:::note
+Blume regenerates `.blume/` on every run — never edit it by hand.
+:::
 ```
 
 ### Tip
 
 A helpful shortcut or best practice that isn't required but makes life easier.
 
-:::tip Set `deployment.site` so sitemaps and Open Graph images use absolute URLs. :::
+:::tip
+Set `deployment.site` so sitemaps and Open Graph images use absolute URLs.
+:::
 
 ```md
-:::tip Set `deployment.site` so sitemaps and Open Graph images use absolute URLs. :::
+:::tip
+Set `deployment.site` so sitemaps and Open Graph images use absolute URLs.
+:::
 ```
 
 ### Success
 
 Confirm a positive outcome or that a step completed as expected.
 
-:::success Your docs built successfully and are ready to deploy. :::
+:::success
+Your docs built successfully and are ready to deploy.
+:::
 
 ```md
-:::success Your docs built successfully and are ready to deploy. :::
+:::success
+Your docs built successfully and are ready to deploy.
+:::
 ```
 
 ### Warning
 
 Flag something that needs care to avoid a mistake or surprising behavior.
 
-:::warning[Heads up] Switching to `output: "server"` requires an adapter before you can deploy. :::
+:::warning[Heads up] Switching to `output: "server"` requires an adapter before you can deploy.
+:::
 
 ```md
-:::warning[Heads up] Switching to `output: "server"` requires an adapter before you can deploy. :::
+:::warning[Heads up] Switching to `output: "server"` requires an adapter before you can deploy.
+:::
 ```
 
 ### Danger
 
 Call out a destructive or breaking action that can't easily be undone.
 
-:::danger `blume eject` is a one-way step — the generated Astro project becomes yours. :::
+:::danger
+`blume eject` is a one-way step — the generated Astro project becomes yours.
+:::
 
 ```md
-:::danger `blume eject` is a one-way step — the generated Astro project becomes yours. :::
+:::danger
+`blume eject` is a one-way step — the generated Astro project becomes yours.
+:::
 ```
 
 ### Info
 
 An informational aside; an alias-friendly default that reads as neutral.
 
-:::info The core theme ships no client framework JS. :::
+:::info
+The core theme ships no client framework JS.
+:::
 
 ```md
-:::info The core theme ships no client framework JS. :::
+:::info
+The core theme ships no client framework JS.
+:::
 ```
 
 The names `caution`, `error`, `important`, and `warn` are accepted as aliases for `warning`, `danger`, `note`, and `warning` respectively.
@@ -364,7 +388,9 @@ $$
 $$
 ```
 
-:::note Math is opt-in because `$` is common in prose and code. Enable it with `markdown: { math: true }` in `blume.config.ts`. :::
+:::note
+Math is opt-in because `$` is common in prose and code. Enable it with `markdown: { math: true }` in `blume.config.ts`.
+:::
 
 ## Smart punctuation
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "blume",
-  "version": "0.5.0",
+  "version": "0.5.2",
   "description": "Documentation that's fast, AI-ready, and zero-config.",
   "keywords": [
     "astro",

package/src/astro/generate.ts

@@ -618,7 +618,6 @@ export const buildRuntimeData = (project: BlumeProject): string => {
               chromeVariants: [],
               selectors: [],
               sidebar: [],
-              sidebarVariants: [],
               tabs: [],
             }
           ),
@@ -974,6 +973,11 @@ export const generateRuntime = async (
   // entryId so i18n duplicates of one entry write a single file.
   const staged = collectStaged(project);
   const hasStaged = staged.size > 0;
+  // Only emit a project-scanning `docs` collection when a filesystem source
+  // actually feeds it. Bridge mode has just the staged Mintlify source, so the
+  // `docs` glob would otherwise scan (and watch) the whole project root for
+  // nothing — see contentConfigTemplate.
+  const hasFilesystemSource = project.sources.some((source) => !source.staged);
 
   const structural = await Promise.all([
     write(
@@ -1004,7 +1008,12 @@ export const generateRuntime = async (
     write(join(srcDir, "env.d.ts"), envTemplate()),
     write(
       join(srcDir, "content.config.ts"),
-      contentConfigTemplate({ config, context, staged: hasStaged })
+      contentConfigTemplate({
+        config,
+        context,
+        filesystem: hasFilesystemSource,
+        staged: hasStaged,
+      })
     ),
     write(
       join(srcDir, "pages", "[...slug].astro"),

package/src/astro/templates.ts

@@ -1,6 +1,6 @@
 import { existsSync, readFileSync } from "node:fs";
 
-import { dirname, join } from "pathe";
+import { dirname, isAbsolute, join, relative } from "pathe";
 
 import { askBackendRuntimeDep } from "../ai/ask.ts";
 import type { AskBackend } from "../ai/ask.ts";
@@ -392,18 +392,44 @@ export const contentConfigTemplate = (options: {
   staged?: boolean;
   /** Base dir for the staged collection; defaults to `<outDir>/content`. */
   stagedBase?: string;
+  /**
+   * Whether any filesystem (non-staged) source feeds the `docs` collection.
+   * When false (e.g. Mintlify bridge mode, where every page is staged), the
+   * collection globs nothing — see below.
+   */
+  filesystem?: boolean;
 }): string => {
   const { context, config } = options;
   const stagedBase = options.stagedBase ?? stagedContentDir(context.outDir);
 
   // Fold the content excludes into the glob as negative patterns so the `docs`
-  // collection never walks into ignored trees. This matters when `content.root`
-  // is the project root (Mintlify bridge mode, or a migrated `.`-rooted project):
-  // without it the collection would scan `node_modules`, `snippets`, etc.
-  const docsPattern = [
-    ...config.content.include,
-    ...(config.content.exclude ?? []).map((pattern) => `!${pattern}`),
-  ];
+  // collection doesn't ingest ignored trees (`node_modules`, `snippets`, the
+  // staged bodies under `.blume/content`, …) as entries. This matters when
+  // `content.root` is the project root (a migrated `.`-rooted project).
+  const outDirRel = relative(context.contentRoot, context.outDir);
+  const outDirIgnore =
+    outDirRel && !outDirRel.startsWith("..") && !isAbsolute(outDirRel)
+      ? [`!${outDirRel}/**`]
+      : [];
+
+  // With no filesystem source, no route renders through `docs`, so glob nothing.
+  // Beyond skipping wasted work, this is the only thing that keeps Astro's
+  // content-layer *watcher* out of `.blume/`: bridge mode roots the collection
+  // at the project dir (which contains `.blume/.astro/fonts`, rewritten on every
+  // request), and the watcher's match test is `picomatch.isMatch(path, pattern)`
+  // — with array-OR semantics, any `!ignored/**` negation *matches* unrelated
+  // files, so negative patterns can't exclude a subtree there. An empty pattern
+  // matches nothing, so the watcher stays silent. The collection is still
+  // declared below so `getCollection("docs")` / `getEntry` resolve (to empty).
+  const filesystem = options.filesystem ?? true;
+  const docsPattern = filesystem
+    ? [
+        ...config.content.include,
+        ...(config.content.exclude ?? []).map((pattern) => `!${pattern}`),
+        "!**/node_modules/**",
+        ...outDirIgnore,
+      ]
+    : [];
 
   // Non-filesystem sources render through a parallel `staged` collection backed
   // by materialized MDX, so the filesystem `docs` collection stays untouched.

package/src/cli/commands/init.ts

@@ -5,35 +5,10 @@ import { defineCommand } from "citty";
 import { basename, dirname, isAbsolute, join, relative } from "pathe";
 
 import { ensureGitignore } from "../../core/gitignore.ts";
-import { getBlumeVersion } from "../../core/version.ts";
+import { blumePackageJson, toPackageName } from "../../core/package-json.ts";
 import { eject } from "../../registry/eject.ts";
 import { logger } from "../log.ts";
 
-/**
- * Derive a valid npm package name from a directory name, falling back to
- * `docs` when nothing usable remains.
- */
-const toPackageName = (raw: string): string =>
-  raw
-    .toLowerCase()
-    .replaceAll(/[^a-z0-9._-]+/gu, "-")
-    .replaceAll(/^[-_.]+|[-_.]+$/gu, "") || "docs";
-
-const packageTemplate = (name: string, version: string): string => `{
-  "name": ${JSON.stringify(name)},
-  "private": true,
-  "type": "module",
-  "scripts": {
-    "dev": "blume dev",
-    "build": "blume build",
-    "doctor": "blume doctor"
-  },
-  "dependencies": {
-    "blume": "^${version}"
-  }
-}
-`;
-
 const TEMPLATES = ["docs", "api", "sdk", "changelog"] as const;
 type Template = (typeof TEMPLATES)[number];
 
@@ -221,7 +196,7 @@ export const initCommand = defineCommand({
     const starter = STARTERS[template];
     const createdPackage = await writeFileSafe(
       join(root, "package.json"),
-      packageTemplate(toPackageName(basename(root)), getBlumeVersion())
+      blumePackageJson(toPackageName(basename(root)))
     );
     await writeFileSafe(join(root, "blume.config.ts"), starter.config);
     await Promise.all(

package/src/core/graph.ts

@@ -96,7 +96,6 @@ export const buildContentGraph = (
         selectors: options.navigation.selectors,
         sharedFolderMeta: options.sharedFolderMeta,
         sidebar: options.navigation.sidebar,
-        sidebarVariants: options.navigation.sidebarVariants,
         tabs,
       });
     }
@@ -104,7 +103,6 @@ export const buildContentGraph = (
       chromeVariants: [],
       selectors: [],
       sidebar: [],
-      sidebarVariants: [],
       tabs: [],
     };
   } else {
@@ -114,7 +112,6 @@ export const buildContentGraph = (
       selectors: options.navigation.selectors,
       sharedFolderMeta: options.sharedFolderMeta,
       sidebar: options.navigation.sidebar,
-      sidebarVariants: options.navigation.sidebarVariants,
       tabs: options.navigation.tabs,
     });
   }

package/src/core/nav-diagnostics.ts

@@ -42,10 +42,7 @@ const collectIcons = (
       push(item.icon, `selector "${item.label}"`);
     }
   }
-  const sidebars = [
-    navigation.sidebar,
-    ...navigation.sidebarVariants.map((variant) => variant.sidebar),
-  ];
+  const sidebars = [navigation.sidebar];
   for (const sidebar of sidebars) {
     for (const node of flattenNodes(sidebar)) {
       push(node.icon, `"${node.label}"`);
@@ -140,10 +137,6 @@ const duplicateLabelDiagnostics = (navigation: Navigation): Diagnostic[] => {
   };
   const sidebars: { nodes: NavNode[]; where: string }[] = [
     { nodes: navigation.sidebar, where: "at the top level" },
-    ...navigation.sidebarVariants.map((variant) => ({
-      nodes: variant.sidebar,
-      where: `in the "${variant.path}" section`,
-    })),
   ];
   for (const { nodes, where } of sidebars) {
     checkLevel(nodes, where);
@@ -162,10 +155,7 @@ const hiddenInSidebarDiagnostics = (
   if (hidden.size === 0) {
     return [];
   }
-  const sidebars = [
-    navigation.sidebar,
-    ...navigation.sidebarVariants.map((variant) => variant.sidebar),
-  ];
+  const sidebars = [navigation.sidebar];
   const diagnostics: Diagnostic[] = [];
   const seen = new Set<string>();
   for (const sidebar of sidebars) {