blume 0.3.0 → 0.4.0

package/docs/configuration/customization.mdx

@@ -5,9 +5,7 @@ description: Override components, add interactive islands, mount custom pages, i
 
 ## Component overrides
 
-Add a `components.ts` (or `components.tsx`) to your project root and export
-`defineComponents`. The `mdx` map either **replaces** a built-in component or
-**adds** a new one — available in every `.mdx` page with no import.
+Add a `components.ts` (or `components.tsx`) to your project root and export `defineComponents`. The `mdx` map either **replaces** a built-in component or **adds** a new one — available in every `.mdx` page with no import.
 
 ```ts components.ts lineNumbers
 import { defineComponents } from "blume";
@@ -22,8 +20,7 @@ export default defineComponents({
 });
 ```
 
-Keys are the names you write in MDX (`<Callout>`, `<Pricing>`). Use the `.tsx`
-filename when you import React components.
+Keys are the names you write in MDX (`<Callout>`, `<Pricing>`). Use the `.tsx` filename when you import React components.
 
 ### Reference form
 
@@ -42,28 +39,21 @@ export default defineComponents({
 });
 ```
 
-The **descriptor** form adds a hydration mode so an interactive
-React/Vue/Svelte component ships its JavaScript and comes alive on the client.
-Without a `client` mode a framework component renders as static HTML — Blume
-prints a build warning when it spots one, since that's usually a mistake.
+The **descriptor** form adds a hydration mode so an interactive React/Vue/Svelte component ships its JavaScript and comes alive on the client. Without a `client` mode a framework component renders as static HTML — Blume prints a build warning when it spots one, since that's usually a mistake.
 
-| `client`    | Hydrates                                                         |
-| ----------- | ---------------------------------------------------------------- |
-| `"load"`    | Immediately on page load                                         |
-| `"idle"`    | When the main thread is idle                                     |
-| `"visible"` | When scrolled into view                                          |
-| `"media"`   | When a `media` query matches (add `media: "(min-width: 40rem)"`) |
-| `"only"`    | Client only, never server-rendered                               |
+| `client` | Hydrates |
+| --- | --- |
+| `"load"` | Immediately on page load |
+| `"idle"` | When the main thread is idle |
+| `"visible"` | When scrolled into view |
+| `"media"` | When a `media` query matches (add `media: "(min-width: 40rem)"`) |
+| `"only"` | Client only, never server-rendered |
 
-For interactive components you use across many pages, the [`islands`
-group](/docs/content/islands#registering-islands-in-componentsts) is a shorthand
-for the descriptor form with `client: "visible"`.
+For interactive components you use across many pages, the [`islands` group](/docs/content/islands#registering-islands-in-componentsts) is a shorthand for the descriptor form with `client: "visible"`.
 
 ### Typing an override
 
-When you replace a built-in, import its prop type from `blume/components` so your
-component matches the contract — the types are derived from the components
-themselves, so they never drift:
+When you replace a built-in, import its prop type from `blume/components` so your component matches the contract — the types are derived from the components themselves, so they never drift:
 
 ```tsx components/Callout.tsx
 import type { CalloutProps } from "blume/components";
@@ -73,14 +63,11 @@ export default function Callout(props: CalloutProps) {
 }
 ```
 
-Prop types are exported for the content components (`CalloutProps`, `CardProps`,
-`TabsProps`, `StepsProps`, `BadgeProps`, and more).
+Prop types are exported for the content components (`CalloutProps`, `CardProps`, `TabsProps`, `StepsProps`, `BadgeProps`, and more).
 
 ## Layout slots
 
-The `layout` map replaces a piece of Blume's chrome with your own component. Each
-override receives the same props as the built-in it replaces, so you can wrap the
-default or start from scratch.
+The `layout` map replaces a piece of Blume's chrome with your own component. Each override receives the same props as the built-in it replaces, so you can wrap the default or start from scratch.
 
 ```ts components.ts
 import { defineComponents } from "blume";
@@ -97,34 +84,28 @@ export default defineComponents({
 
 Wired slots:
 
-| Slot              | Replaces                                                 | Props                                                          |
-| ----------------- | -------------------------------------------------------- | -------------------------------------------------------------- |
-| `Layout`          | The entire page shell (`RootLayout`)                     | Everything the built-in layout receives, plus the `layout` map |
-| `Header`          | The top navigation bar                                   | `site`, `logo`, `navigation`, `route`, `searchEnabled`, …      |
-| `Logo`            | The brand link (mark + title) in the header              | `site`, `logo`                                                 |
-| `Search`          | The header search trigger + modal                        | `navigation`, `strings`, `locale`, `askEnabled`                |
-| `Sidebar`         | The primary navigation tree                              | `items`, `currentRoute`                                        |
-| `MobileNav`       | The nav inside the mobile drawer (defaults to `Sidebar`) | `items`, `currentRoute`                                        |
-| `Breadcrumbs`     | The breadcrumb trail                                     | `crumbs`                                                       |
-| `TableOfContents` | The on-this-page outline                                 | `headings`, `title`, `variant`                                 |
-| `Pagination`      | The prev/next footer links                               | `prev`, `next`, `strings`                                      |
-| `PageHeader`      | An injection point above the article (no built-in)       | `page`, `headings`, `route`                                    |
-| `PageFooter`      | An injection point below the article (no built-in)       | `page`, `headings`, `route`                                    |
-| `Footer`          | A site-wide footer after the content grid (no built-in)  | `site`, `navigation`, `ui`                                     |
-
-`PageHeader`, `PageFooter`, and `Footer` have no built-in component — they render
-nothing until you set them, which makes them handy injection points for a
-promo banner, a "last updated" note, or a marketing footer.
-
-Layout slots accept the same [three reference forms](#reference-form) as MDX
-overrides, so a slot can be a path string or a hydrated descriptor
-(`{ component, client }`) when you want an interactive header or footer.
+| Slot | Replaces | Props |
+| --- | --- | --- |
+| `Layout` | The entire page shell (`RootLayout`) | Everything the built-in layout receives, plus the `layout` map |
+| `Header` | The top navigation bar | `site`, `logo`, `navigation`, `route`, `searchEnabled`, … |
+| `Logo` | The brand link (mark + title) in the header | `site`, `logo` |
+| `Search` | The header search trigger + modal | `navigation`, `strings`, `locale`, `askEnabled` |
+| `Sidebar` | The primary navigation tree | `items`, `currentRoute` |
+| `MobileNav` | The nav inside the mobile drawer (defaults to `Sidebar`) | `items`, `currentRoute` |
+| `Breadcrumbs` | The breadcrumb trail | `crumbs` |
+| `TableOfContents` | The on-this-page outline | `headings`, `title`, `variant` |
+| `Pagination` | The prev/next footer links | `prev`, `next`, `strings` |
+| `PageHeader` | An injection point above the article (no built-in) | `page`, `headings`, `route` |
+| `PageFooter` | An injection point below the article (no built-in) | `page`, `headings`, `route` |
+| `Footer` | A site-wide footer after the content grid (no built-in) | `site`, `navigation`, `ui` |
+
+`PageHeader`, `PageFooter`, and `Footer` have no built-in component — they render nothing until you set them, which makes them handy injection points for a promo banner, a "last updated" note, or a marketing footer.
+
+Layout slots accept the same [three reference forms](#reference-form) as MDX overrides, so a slot can be a path string or a hydrated descriptor (`{ component, client }`) when you want an interactive header or footer.
 
 ## Interactive islands
 
-For interactive UI (React, Vue, or Svelte), drop a component into an `islands/`
-folder and use it in any MDX page — Blume hydrates it for you, no wrapper or
-registration needed:
+For interactive UI (React, Vue, or Svelte), drop a component into an `islands/` folder and use it in any MDX page — Blume hydrates it for you, no wrapper or registration needed:
 
 ```tsx islands/Counter.tsx lineNumbers
 import { useState } from "react";
@@ -139,51 +120,37 @@ export default function Counter() {
 Use it anywhere: <Counter />
 ```
 
-See [Islands](/docs/content/islands) for hydration strategies and framework
-setup.
+See [Islands](/docs/content/islands) for hydration strategies and framework setup.
 
 ## Custom pages
 
-Add `.astro` files under your `pages/` folder to mount fully custom routes
-alongside your docs — a landing page, a pricing page, or a hand-built index. They
-keep their location, so relative imports and `getStaticPaths` work as usual, and
-they can read your config, navigation, and routes from the `blume:data` module.
+Add `.astro` files under your `pages/` folder to mount fully custom routes alongside your docs — a landing page, a pricing page, or a hand-built index. They keep their location, so relative imports and `getStaticPaths` work as usual, and they can read your config, navigation, and routes from the `blume:data` module.
 
 See [Custom Pages](/docs/advanced/custom-pages) for the full guide.
 
 ## Registry
 
-`blume add` copies a Blume-maintained component into your project as **source** —
-you own it and can edit it freely. Run it with no arguments to list what's
-available:
+`blume add` copies a Blume-maintained component into your project as **source** — you own it and can edit it freely. Run it with no arguments to list what's available:
 
 ```bash
 blume add
 ```
 
-Install a layout slot (header, sidebar, breadcrumbs, table of contents,
-pagination, or feedback) or any content component (callout, card, tabs, steps,
-accordion, and more):
+Install a layout slot (header, sidebar, breadcrumbs, table of contents, pagination, or feedback) or any content component (callout, card, tabs, steps, accordion, and more):
 
 ```bash
 blume add callout
 blume add pagination
 ```
 
-The copy imports the rest of the framework from `blume/*`, so it renders exactly
-like the built-in until you change it. `blume add` prints the `defineComponents`
-snippet to register it — content components under `mdx`, layout pieces under
-`layout`.
+The copy imports the rest of the framework from `blume/*`, so it renders exactly like the built-in until you change it. `blume add` prints the `defineComponents` snippet to register it — content components under `mdx`, layout pieces under `layout`.
 
 ## Eject
 
-When you want full control, eject the generated runtime into a standalone Astro
-project:
+When you want full control, eject the generated runtime into a standalone Astro project:
 
 ```bash
 blume eject --yes
 ```
 
-Eject is a one-way step: the hidden `.blume/` runtime becomes a normal Astro app
-you own and can modify directly. The `blume` package stays importable, so you
-keep its components, theme, and Markdown processors.
+Eject is a one-way step: the hidden `.blume/` runtime becomes a normal Astro app you own and can modify directly. The `blume` package stays importable, so you keep its components, theme, and Markdown processors.

package/docs/configuration/export.mdx

@@ -3,11 +3,7 @@ title: Export
 description: Let readers download any page as a PDF or EPUB.
 ---
 
-Blume can add an **Export** action to the [page
-actions](/docs/content/navigation#page-actions) beneath the table of contents,
-letting readers save the page they're on as a **PDF** or an **EPUB**. It's off by
-default and entirely client-side — no server, and [static](/docs/deployment)
-builds stay static.
+Blume can add an **Export** action to the [page actions](/docs/content/navigation#page-actions) beneath the table of contents, letting readers save the page they're on as a **PDF** or an **EPUB**. It's off by default and entirely client-side — no server, and [static](/docs/deployment) builds stay static.
 
 ## Enable it
 
@@ -26,45 +22,24 @@ export: {
 },
 ```
 
-Any format you omit (or set to `false`) is left out of the menu. With both off —
-the default — the **Export** action doesn't appear at all.
+Any format you omit (or set to `false`) is left out of the menu. With both off — the default — the **Export** action doesn't appear at all.
 
 ## PDF
 
-**Export to PDF** opens your browser's print dialog with a print stylesheet that
-strips the site chrome — header, sidebars, navigation — down to just the article.
-Choose **Save as PDF** to finish.
+**Export to PDF** opens your browser's print dialog with a print stylesheet that strips the site chrome — header, sidebars, navigation — down to just the article. Choose **Save as PDF** to finish.
 
-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.
+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
 
-**Export to EPUB** generates a self-contained `.epub` of the current page in the
-browser and downloads it — ready for Apple Books, Calibre, or any e-reader. The
-generator is loaded only when a reader clicks Export, so it never weighs down the
-rest of your site.
+**Export to EPUB** generates a self-contained `.epub` of the current page in the browser and downloads it — ready for Apple Books, Calibre, or any e-reader. The generator is loaded only when a reader clicks Export, so it never weighs down the rest of your site.
 
-To keep the file readable on a device with no stylesheet or JavaScript of its
-own, Blume rewrites the page into clean, standalone HTML: syntax-highlighted code
-becomes plain monospace, decorative icons and copy buttons are dropped, and a
-built-in e-reader stylesheet handles spacing, code blocks, and tables.
+To keep the file readable on a device with no stylesheet or JavaScript of its own, Blume rewrites the page into clean, standalone HTML: syntax-highlighted code becomes plain monospace, decorative icons and copy buttons are dropped, and a built-in e-reader stylesheet handles spacing, code blocks, and tables.
 
 ## What gets exported
 
-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.
+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/index.mdx

@@ -5,9 +5,7 @@ sidebar:
   label: blume.config.ts
 ---
 
-Blume reads `blume.config.ts` from your project root. Wrap your config in
-`defineConfig` for autocomplete and type-checking — every field is optional, with
-a sensible default.
+Blume reads `blume.config.ts` from your project root. Wrap your config in `defineConfig` for autocomplete and type-checking — every field is optional, with a sensible default.
 
 ```ts blume.config.ts lineNumbers
 import { defineConfig } from "blume";
@@ -20,8 +18,7 @@ export default defineConfig({
 
 ## A complete example
 
-A broader example touching the most common options (see each feature's guide for
-the rest):
+A broader example touching the most common options (see each feature's guide for the rest):
 
 ```ts blume.config.ts lineNumbers
 import { defineConfig } from "blume";
@@ -90,25 +87,22 @@ export default defineConfig({
 
 ## Site
 
-| Option        | Default           | Description                                             |
-| ------------- | ----------------- | ------------------------------------------------------- |
-| `title`       | `"Documentation"` | Site name — shown in the header, page titles, OG cards. |
-| `description` | —                 | Default meta description, used for SEO and OG.          |
-| `logo`        | —                 | Brand logo shown beside the title in the header.        |
-| `banner`      | —                 | Site-wide announcement bar above the header.            |
+| Option | Default | Description |
+| --- | --- | --- |
+| `title` | `"Documentation"` | Site name — shown in the header, page titles, OG cards. |
+| `description` | — | Default meta description, used for SEO and OG. |
+| `logo` | — | Brand logo shown beside the title in the header. |
+| `banner` | — | Site-wide announcement bar above the header. |
 
 ### Logo
 
-Point `logo` at an SVG and Blume inlines it, so a `currentColor` logo follows
-the light and dark theme automatically:
+Point `logo` at an SVG and Blume inlines it, so a `currentColor` logo follows the light and dark theme automatically:
 
 ```ts blume.config.ts
 logo: "/logo.svg",
 ```
 
-The SVG can live at your project root or in `public/`. For raster images — or
-separate light and dark artwork — use the object form (these must live in
-`public/`):
+The SVG can live at your project root or in `public/`. For raster images — or separate light and dark artwork — use the object form (these must live in `public/`):
 
 ```ts blume.config.ts lineNumbers
 logo: {
@@ -123,9 +117,7 @@ logo: {
 
 ### Favicon
 
-There's no favicon option — Blume auto-detects one by filename, the way Next.js
-does. Drop an `icon` or `favicon` file (`.svg`, `.png`, or `.ico`) in your
-project root or `public/` directory and it becomes the browser tab icon:
+There's no favicon option — Blume auto-detects one by filename, the way Next.js does. Drop an `icon` or `favicon` file (`.svg`, `.png`, or `.ico`) in your project root or `public/` directory and it becomes the browser tab icon:
 
 ```
 my-docs/
@@ -134,17 +126,11 @@ my-docs/
 └─ docs/
 ```
 
-SVG wins over PNG over ICO when several are present, and a file in `public/` is
-preferred over one at the root. If Blume finds no icon, it falls back to its own
-mark.
+SVG wins over PNG over ICO when several are present, and a file in `public/` is preferred over one at the root. If Blume finds no icon, it falls back to its own mark.
 
 ### Apple touch icon
 
-The icon iOS uses when someone adds your site to their home screen is detected
-the same way. Drop an `apple-icon` file (`.png`, `.jpg`, or `.jpeg`) — or an
-`apple-touch-icon.png`, the name most favicon generators emit — in your project
-root or `public/` directory and Blume wires up `<link rel="apple-touch-icon">`
-for you. There's no default; if no file is found, no tag is emitted.
+The icon iOS uses when someone adds your site to their home screen is detected the same way. Drop an `apple-icon` file (`.png`, `.jpg`, or `.jpeg`) — or an `apple-touch-icon.png`, the name most favicon generators emit — in your project root or `public/` directory and Blume wires up `<link rel="apple-touch-icon">` for you. There's no default; if no file is found, no tag is emitted.
 
 ```
 my-docs/
@@ -153,14 +139,11 @@ my-docs/
 └─ docs/
 ```
 
-Put the file in `public/` rather than the project root: iOS ignores the inlined
-data URI Blume uses for a root-level icon, so only a `public/` file (served at
-`/apple-icon.png`) reliably reaches the home screen.
+Put the file in `public/` rather than the project root: iOS ignores the inlined data URI Blume uses for a root-level icon, so only a `public/` file (served at `/apple-icon.png`) reliably reaches the home screen.
 
 ### Banner
 
-Show a site-wide announcement bar above the header. Pass a string, or an object
-with a link and a dismiss button:
+Show a site-wide announcement bar above the header. Pass a string, or an object with a link and a dismiss button:
 
 ```ts blume.config.ts
 banner: "Docs are in beta — expect changes.",
@@ -175,15 +158,11 @@ banner: {
 },
 ```
 
-When `dismissible` is on, the bar shows a close button and stays hidden for that
-visitor afterward. The dismissal key defaults to the content text, so editing
-the message brings the banner back; set a stable `id` to keep it dismissed
-across edits.
+When `dismissible` is on, the bar shows a close button and stays hidden for that visitor afterward. The dismissal key defaults to the content text, so editing the message brings the banner back; set a stable `id` to keep it dismissed across edits.
 
 ## Content
 
-Where your content lives and how Blume discovers it. See [Pages](/docs/content) for
-how files become routes.
+Where your content lives and how Blume discovers it. See [Pages](/docs/content) for how files become routes.
 
 ```ts blume.config.ts lineNumbers
 content: {
@@ -191,35 +170,41 @@ content: {
 }
 ```
 
-| Option        | Default              | Description                                  |
-| ------------- | -------------------- | -------------------------------------------- |
-| `root`        | `"docs"`             | Folder Blume scans for content.              |
-| `include`     | `["**/*.{md,mdx}"]`  | Globs that match content files.              |
-| `exclude`     | `["**/_*", "**/.*"]` | Globs to ignore (underscore- and dot-files). |
-| `pages`       | `"pages"`            | Folder for custom `.astro` pages.            |
-| `defaultType` | `"doc"`              | Page `type` used when frontmatter omits it.  |
+| Option | Default | Description |
+| --- | --- | --- |
+| `root` | `"docs"` | Folder Blume scans for content. |
+| `include` | `["**/*.{md,mdx}"]` | Globs that match content files. |
+| `exclude` | `["**/_*", "**/.*"]` | Globs to ignore (underscore- and dot-files). |
+| `pages` | `"pages"` | Folder for custom `.astro` pages. |
+| `defaultType` | `"doc"` | Page `type` used when frontmatter omits it. |
+| `assets` | `[]` | Extra top-level directories served at the site root, alongside `public/`. |
+
+Assets normally live in `public/` — a file at `public/logo.png` is served at `/logo.png`. Use `assets` to serve additional root-level folders in place instead of moving them under `public/`. Each entry is a directory relative to your project root, served at the matching URL and copied into `dist/` on build:
+
+```ts blume.config.ts
+content: {
+  assets: ["images"], // /images/create.png → images/create.png
+}
+```
+
+This is mainly useful after migrating from a tool that serves assets from the project root (like Mintlify), so references such as `![](/images/create.png)` keep resolving without relocating every file.
 
 ## Last modified
 
-Show a "Last updated on …" line at the bottom of each page. Off by default; set
-`lastModified` to `true` to derive each page's date from its git history:
+Show a "Last updated on …" line at the bottom of each page. Off by default; set `lastModified` to `true` to derive each page's date from its git history:
 
 ```ts blume.config.ts
 lastModified: true,
 ```
 
-| Value                     | Description                                                    |
-| ------------------------- | -------------------------------------------------------------- |
-| `false`                   | Disabled (default).                                            |
-| `true`                    | Read the date from git history (commit dates).                 |
-| `{ type: "git" }`         | Same as `true`, written explicitly.                            |
+| Value | Description |
+| --- | --- |
+| `false` | Disabled (default). |
+| `true` | Read the date from git history (commit dates). |
+| `{ type: "git" }` | Same as `true`, written explicitly. |
 | `{ type: "frontmatter" }` | Never run git — use only the `lastModified` frontmatter field. |
 
-The git source reads the most recent commit that touched each file, so it works
-in any git repository — including monorepos — and needs the repo's history at
-build time (avoid a shallow `--depth 1` checkout in CI). A page's own
-`lastModified` frontmatter always wins, which is handy for pinning a date or for
-files that aren't committed yet:
+The git source reads the most recent commit that touched each file, so it works in any git repository — including monorepos — and needs the repo's history at build time (avoid a shallow `--depth 1` checkout in CI). A page's own `lastModified` frontmatter always wins, which is handy for pinning a date or for files that aren't committed yet:
 
 ```mdx page.mdx
 ---
@@ -228,14 +213,11 @@ lastModified: 2026-06-20
 ---
 ```
 
-When enabled, the date is also emitted as schema.org `dateModified` in the
-page's structured data.
+When enabled, the date is also emitted as schema.org `dateModified` in the page's structured data.
 
 ## SEO
 
-Open Graph images, RSS feeds, and JSON-LD structured data, grouped under `seo`.
-See the [SEO guide](/docs/configuration/seo) for metadata, frontmatter overrides, and
-the full reference.
+Open Graph images, RSS feeds, and JSON-LD structured data, grouped under `seo`. See the [SEO guide](/docs/configuration/seo) for metadata, frontmatter overrides, and the full reference.
 
 ```ts blume.config.ts lineNumbers
 seo: {
@@ -247,22 +229,21 @@ seo: {
 }
 ```
 
-| Option           | Default                 | Description                                             |
-| ---------------- | ----------------------- | ------------------------------------------------------- |
-| `og.enabled`     | auto                    | Per-page Open Graph images — on when a site URL is set. |
-| `rss.enabled`    | `true`                  | Build feeds for blog and changelog content.             |
-| `rss.types`      | `["blog", "changelog"]` | Content types that each get a feed.                     |
-| `rss.limit`      | `50`                    | Maximum items per feed.                                 |
-| `sitemap`        | `true`                  | Generate sitemap.xml (needs deployment.site).           |
-| `robots`         | `true`                  | Generate robots.txt with a Sitemap link.                |
-| `structuredData` | `true`                  | Emit schema.org JSON-LD in each page's head.            |
+| Option | Default | Description |
+| --- | --- | --- |
+| `og.enabled` | auto | Per-page Open Graph images — on when a site URL is set. |
+| `rss.enabled` | `true` | Build feeds for blog and changelog content. |
+| `rss.types` | `["blog", "changelog"]` | Content types that each get a feed. |
+| `rss.limit` | `50` | Maximum items per feed. |
+| `sitemap` | `true` | Generate sitemap.xml (needs deployment.site). |
+| `robots` | `true` | Generate robots.txt with a Sitemap link. |
+| `structuredData` | `true` | Emit schema.org JSON-LD in each page's head. |
 
 These work best with an absolute [`deployment.site`](/docs/deployment) for full URLs.
 
 ## Table of contents
 
-The on-this-page outline is on by default and lists `H2`–`H3` headings. Turn it
-off, or change the heading range, with `toc`:
+The on-this-page outline is on by default and lists `H2`–`H3` headings. Turn it off, or change the heading range, with `toc`:
 
 ```ts blume.config.ts
 export default defineConfig({
@@ -276,23 +257,22 @@ export default defineConfig({
 
 Each of these has its own guide. The config field is the entry point:
 
-| Field        | What it configures                                  | Guide                                      |
-| ------------ | --------------------------------------------------- | ------------------------------------------ |
-| `theme`      | Accent color, corner radius, fonts, light/dark mode | [Theming](/docs/configuration/theming)     |
-| `navigation` | Explicit sidebar and header tabs                    | [Navigation](/docs/content/navigation)     |
-| `search`     | Provider (Orama or Pagefind) and indexing           | [Search](/docs/configuration/search)       |
-| `markdown`   | Opt-in Markdown features like math                  | [Syntax](/docs/content/syntax)             |
-| `ai`         | `llms.txt`, Ask AI, and the MCP server              | [AI](/docs/configuration/ai)               |
-| `mcp`        | Hosted MCP server for coding agents                 | [AI](/docs/configuration/ai#mcp-server)    |
-| `analytics`  | Vercel, PostHog, and custom scripts                 | [Analytics](/docs/configuration/analytics) |
-| `seo`        | Metadata, OG images, feeds, structured data         | [SEO](/docs/configuration/seo)             |
-| `deployment` | Output mode, adapter, and site URL                  | [Deployment](/docs/deployment)             |
-| `redirects`  | Permanent and temporary redirects                   | [Deployment](/docs/deployment#redirects)   |
+| Field | What it configures | Guide |
+| --- | --- | --- |
+| `theme` | Accent color, corner radius, fonts, light/dark mode | [Theming](/docs/configuration/theming) |
+| `navigation` | Explicit sidebar and header tabs | [Navigation](/docs/content/navigation) |
+| `search` | Provider (Orama or Pagefind) and indexing | [Search](/docs/configuration/search) |
+| `markdown` | Opt-in Markdown features like math | [Syntax](/docs/content/syntax) |
+| `ai` | `llms.txt`, Ask AI, and the MCP server | [AI](/docs/configuration/ai) |
+| `mcp` | Hosted MCP server for coding agents | [AI](/docs/configuration/ai#mcp-server) |
+| `analytics` | Vercel, PostHog, and custom scripts | [Analytics](/docs/configuration/analytics) |
+| `seo` | Metadata, OG images, feeds, structured data | [SEO](/docs/configuration/seo) |
+| `deployment` | Output mode, adapter, and site URL | [Deployment](/docs/deployment) |
+| `redirects` | Permanent and temporary redirects | [Deployment](/docs/deployment#redirects) |
 
 ## Precedence
 
-Settings resolve from lowest to highest priority, so you only override what you
-need:
+Settings resolve from lowest to highest priority, so you only override what you need:
 
 <Steps>
   <Step title="Blume defaults">A sensible default for every field.</Step>