Adding a page

There's no "new page" button — this is a file-backed wiki, not a database. Adding a page is two edits:

1. Write the data file. Create content/docs/pages/<slug>.ts exporting a DocPage:

   import type { DocPage } from "../types";
   
   export const mySlug: DocPage = {
     slug: ["my-slug"],
     title: "My Page",
     emoji: "📄",
     summary: "One line for the search palette.",
     body: `# My Page\n\nMarkdown goes here.`,
   };
   

   slug is an array because pages can nest — ["team", "onboarding"] renders at /team/onboarding. Most pages are one segment.

2. Register it in content/docs/index.ts: import it and add it to a section's pages array in DOCS_SECTIONS (or start a new section — sections are what the sidebar's collapsible groups render).

That's it. The sidebar, the breadcrumb, the ⌘K search, and the page route all read from DOCS_SECTIONS/DOCS_PAGE_BY_SLUG — there's nothing else to wire up.

Body format

body is markdown, rendered by components/docs/DocsMarkdown.tsx (react-markdown + remark-gfm, so tables and task lists work). It is not sanitized against untrusted input — every page here is written by someone with repo write access, the same trust boundary as the rest of the codebase.

Favorites and search

Favorites are per-browser, stored in localStorage (see lib/docs/favorites.ts) — starring a page doesn't touch a file or a database, and won't show up for anyone else. Search (⌘K) is a client-side filter over every registered page's title and summary — nothing to index.

If this needs to stop being private

Right now /docs is noindexed and robots.txt-disallowed, but not passphrase-gated — anyone with the URL can read it. If it starts holding anything sensitive, the pattern to copy is bankGate() in middleware.ts: a signed cookie, checked before the mount, redirecting to a login page with ?next= set to where the visitor was headed.