barakopress 0.7.0 → 0.9.0

package/README.md

@@ -1,8 +1,13 @@
 # barakoPress
 
-A blog engine for [barakoCMS](https://github.com/BaryoDev/barakoCMS), shipped as a package. Server
-rendered, cached until the CMS says otherwise, so ordinary traffic never reaches Postgres and a
-publish is live in one request.
+The renderer for barakoCMS sites: pages from blocks, collections and docs trees, cached until the CMS
+says otherwise.
+
+It ships as an npm package, `barakopress`, that a Next app mounts route by route, and as a container
+image, `ghcr.io/baryodev/barako-press`, that serves every site a [barakoCMS](https://github.com/BaryoDev/barakoCMS)
+instance knows. Pages are server rendered and cached per tenant, so ordinary traffic never reaches
+Postgres and a publish is live in one request. You own it and run it where you choose. Nothing is
+metered per seat, record or environment.
 
 It is an engine, not a site. Content types in barakoCMS are defined at runtime, so a client's posts
 are as likely to be an `article` with a `Headline` as the blog blueprint's `post` with a `Title`.
@@ -85,8 +90,8 @@ decision, not the engine's.
 | --- | --- | --- |
 | `app/page.tsx` | `default`, `generateMetadata` | `createHome(config, blocks)`, `createHomeMetadata(config)` |
 | `app/blog/[slug]/page.tsx` | `default`, `generateMetadata` | `createBlogPost(config)`, `createPostMetadata(config)` |
-| `app/authors/[slug]/page.tsx` | `default` | `createArchive(config, "author")` |
-| `app/categories/[slug]/page.tsx` | `default` | `createArchive(config, "category")` |
+| `app/authors/[slug]/page.tsx` | `default` | `createCollectionDetail(config, "author", { related: { collection: "post", via: "Author" } })` |
+| `app/categories/[slug]/page.tsx` | `default` | `createCollectionDetail(config, "category", { related: { collection: "post", via: "Category" } })` |
 | `app/feed.xml/route.ts` | `GET` | `createFeed(config)` |
 | `app/sitemap.ts` | `default` | `createSitemap(config)` |
 | `app/robots.ts` | `default` | `createRobots(config)` |
@@ -94,7 +99,7 @@ decision, not the engine's.
 | `app/[...path]/page.tsx` | `default`, `generateMetadata` | `createPage(config, blocks)`, `createPageMetadata(config)` |
 | `app/doctors/page.tsx` | `default` | `createCollectionIndex(config, "doctors")` |
 | `app/doctors/[slug]/page.tsx` | `default`, `generateMetadata`, `generateStaticParams` | `createCollectionDetail(config, "doctors")`, `createCollectionMetadata(config, "doctors")`, `createCollectionStaticParams(config, "doctors")` |
-| `app/api/blocks/route.ts` | `GET`, `OPTIONS` | `createBlockSchemaRoute(blocks)`, `createBlockSchemaPreflight()` |
+| `app/api/blocks/route.ts` | `GET`, `OPTIONS` | `createBlockSchemaRoute(config, blocks)`, `createBlockSchemaPreflight()` |
 | `app/api/blocks/bindings/route.ts` | `GET`, `OPTIONS` | `createBindingReportRoute(config, blocks)`, `createBindingReportPreflight()` |
 | `app/layout.tsx` | `default`, `generateMetadata` | `createSiteLayout(config, { blocks })`, `createSiteMetadata(config)` |
 | `app/%5Fshare/route.ts` | `GET` | `createSharePage(config)` |
@@ -104,508 +109,65 @@ decision, not the engine's.
 `HomeCollection`, or the post index when it picked neither, which is what `createBlogIndex` did and
 still does for a site that mounts that instead.
 
+`via` is the post's field that references the author or category. `createArchive(config, "author")`
+makes that same call and is `@deprecated` since 0.7.0, as is `createArchiveStaticParams`, which is
+`createCollectionStaticParams`.
+
 Mount only what you want. Nothing requires anything else. The paths only have to agree with the
 `routes` in your config, which is what every generated link is built from.
 
 `createBlogPostPreview` replaces `createBlogPost` when you want `?preview=TOKEN` to render a draft.
 It reads `searchParams`, which forces the route dynamic, so a site using `output: "export"` takes
-`createBlogPost` and gives up preview. `createPostStaticParams` and `createArchiveStaticParams` exist
-for that static case.
+`createBlogPost` and gives up preview. `createPostStaticParams` and `createCollectionStaticParams`
+exist for that static case.
+
+A site that draws its own post page keeps preview by giving the detail route its own view, and maps
+the item with the engine's own mapping:
+
+```tsx
+export default createCollectionDetail(config, POST_COLLECTION, {
+  preview: true,
+  view: ({ config, item, preview }) => <MyPost post={postFromItem(config, item)} preview={preview} />,
+});
+```
 
 The binding report says why a binding on a page did not resolve, so an editor fixes it in barakoBrew
 instead of asking whoever can read the server log. Ask for one page at a time, by `?slug=` or
 `?path=`, and each problem names the binding as typed, the reason (`unknown scope`, `unbound scope`
 or `no value`), and the block and field it came from. It reports the page as rendered, not as
-stored, so a `{{item.X}}` outside a repeat is reported as an unbound scope. Give it the same `query`
-option the page route has: off, which is the default, a `{{query.X}}` is an unbound scope for every
-visitor and the report says so, and a report that resolved one anyway would tell an editor a field
-works where it does not. It is never anonymous:
+stored, so a `{{item.X}}` outside a repeat is reported as an unbound scope. Give it the `query`
+option the page's route works out to. `createPage` and `createHome` default it by where they are
+mounted: off under a request-time site's `app/%5Fpress/[site]`, where a `{{query.X}}` is an unbound
+scope for every visitor, and on for a route outside it, such as a build-time site's
+`app/[...path]`. The report defaults to off wherever it is mounted, so for a page on a route outside
+the tenant segment pass `{ query: true }`, or the report calls a `{{query.X}}` that works on the page
+an unbound scope. It is never anonymous:
 the caller presents the tenant's key as `Authorization: Bearer`, derived from `PRESS_SECRET` and
 printed by `barakopress bindings-key <tenant>`. Answers are never cached.
 
 `Card` and `PostView` are exported too, for a site that wants its own page but the engine's markup.
 
-### Collections: any content type as a list and a detail page
-
-A hospital has departments and doctors, a law firm practice areas and people. Each is a collection: a
-content type with a route, a field map, references to other collections, a sort, and whether it has a
-feed. The blog is three collections that `defineConfig` derives from `types`, `fields` and `routes`
-(`post`, `author` and `category`), and `createBlogIndex`, `createBlogPost` and `createArchive` are thin
-wrappers over the collection screens. A site configured the old way changes nothing:
-`src/blog-wrappers.test.tsx` renders every blog factory, the feed, the sitemap and the metadata, and
-compares them and the requests they make with `test/blog-wrappers.golden.json`, which was written
-before collections existed.
-
-On a request-time site the map is the tenant's, from a json field `Collections` on its site settings,
-merged over the configured collections by key. A build-time site passes `collections` to
-`defineConfig` in the same shape:
-
-```json
-{
-  "departments": {
-    "type": "department", "route": "/departments",
-    "fields": { "title": "Name", "body": "About" },
-    "noun": ["department", "departments"]
-  },
-  "doctors": {
-    "type": "doctor", "route": "/doctors", "sort": "Name",
-    "fields": { "title": "Name", "summary": "Specialty", "image": "Photo" },
-    "references": { "Department": { "collection": "departments", "label": "in" } },
-    "noun": ["doctor", "doctors"]
-  }
-}
-```
-
-| Key | What |
-| --- | --- |
-| `type` | The content type. Required |
-| `route` | The index is served at the route and an item at `route/slug`. Absent, items are listed and never linked |
-| `fields` | `title` (required), `slug`, `summary`, `body` (markdown), `date`, `image`, `imageAlt`, `featured`, `tags`, `url`, `photo`, `progress`. Each is a field name or a list tried in order; `@createdAt` and `@updatedAt` read the entry itself. `photo` is a portrait drawn above the title, `image` the wide one, and `progress` is a number from 0 to 100 that `progressList` draws |
-| `references` | Reference fields, each naming the collection it points into and the word a card puts before the link. Resolved in the same request |
-| `sort` | Sent to the API, for example `-PublishedAt` |
-| `feed` | Whether `createFeed(config, key)` serves it |
-| `sitemap` | On unless `false`. A collection is paged to `pageSizes.sitemap` entries; the file stops at the standard's 50,000 URLs and says so in the log |
-| `index` | Whether the root catch-all serves an index at the route. On unless `false`; the derived `author` and `category` have it off, so `/authors` stays a 404 unless a route file mounts it |
-| `pageSize`, `label`, `noun` | Items on the index, its heading, and how a count reads |
-| `colorBy` | A choice field whose option colours the item. See below |
-| `related` | What an item page lists under the item: `"semantic"` for the items of this collection closest to it by meaning, `false` for none. Unset, the first collection that references this one |
-| `readingTime` | Whether an item page shows a read time worked out from its body. Off unless `true` |
-| `layout` | How an item page is drawn: `"list"`, the shell markup every collection has had, or `"article"`, the reading column the blog's posts are drawn in. See below |
-| `tree` | Set when the collection is a manual rather than a flat list: sections, an order, nesting, products. See below |
-
-A settings entry that does not read as a collection is left out whole: a type or field that is not a
-plain identifier, a route that is not a plain site path, or no title field. `post`, `author` and
-`category` are replaceable by key like any other collection, since every read goes through the
-collection's own field map. A build-time collection mounted at `/` throws in `defineConfig`. When two
-routes match, the longer one wins.
-
-A request-time site cannot add a route file per tenant, so the root catch-all from the pages section
-also serves every collection with a route: its index at the route, and an item one segment below. A
-route file wins where there is one. A collection's first segment is reserved from pages at the root.
-
-A detail page lists the items of the first collection that references it, so `/departments/cardiology`
-lists its doctors, the way an author's archive lists their posts. `listRelated(config, "doctors",
-department, { via: "Department" })` returns the same list; `listRelated(config, post)` still returns
-related posts by semantic search.
-
-With `related: "semantic"` it lists the items of its own collection nearest it by meaning instead, so
-an agency's case study gets the band a post has. That needs the CMS AI module: without it the search
-answers nothing and the page draws no band at all, which is the same way the post page degrades.
-`listRelatedItems(config, key, item)` returns that list on its own.
-
-**Filtering.** `listCollection(config, "doctors", { filter: { Department: "cardiology" } })` takes a
-reference field by the target's slug and any other field by the value it holds, a choice field by its
-option. The API takes five filters. `createCollectionIndex(config, key, { filter })` takes the same,
-and the `collection` block has `filterField` and `filterValue`.
-
-**A style per option.** With `colorBy: "AreaOfFocus"` on a `project` collection, the site settings
-`OptionStyles` entry says how each option of that field is shown:
-
-```json
-{
-  "OptionStyles": {
-    "project.AreaOfFocus": {
-      "Providing clean water": { "tone": "sky", "icon": "location", "label": "Water" }
-    }
-  }
-}
-```
-
-`tone` names a colour from `Colors`, a theme slot, or a colour written out, and each card, item page
-and collection block item carries it as a left border. `icon` is one of the engine's icon names, and
-`label` is the word a visitor reads in place of the option's own value; the value stays on the element
-as `data-option`, where a site's own CSS can still find it. A tone that does not resolve to something
-readable as a colour is dropped, a label past 40 characters is dropped, and an icon name nothing
-draws draws nothing, each on its own rather than losing the whole entry.
-
-`OptionColors` is the same thing said shorter, `{ "project.AreaOfFocus": { "Providing clean water":
-"sky" } }`, an option whose style is a tone and nothing else. A tenant that saved colours keeps them,
-and a style for the same option wins field by field. A build-time site passes `optionStyles`, or
-`optionColors`, in the same shapes.
-
-`Card` and `ItemView` are exported for a site that wants its own page, and `Card` still takes a `post`.
-`getItem`, `listCollection` and `getGlobals(config)`, the tenant's settings entry as stored, are
-exported too.
-
-**A long-form layout.** `layout: "article"` draws an item as a reading column: a back link, the title
-and standfirst, a byline from the collection's first reference, the date, a read time worked out from
-the body, the other references, the tags, the cover image, the prose and a band of neighbours under
-it. That is the page the blog's posts have always had, and it is a collection setting rather than a
-blog screen, so a law firm's briefings or a newsroom's features get it by asking. Styled inline from
-the theme, so it looks right whether or not the consumer imports `barakopress/styles.css`.
-`PostView` is a wrapper over the same layout and is `@deprecated` for 1.0.0.
-
-**Docs: a collection as a tree.** A manual is a collection plus four fields saying where each page
-sits. `tree` names them, and the settings beside them say what the sidebar and the switcher show:
-
-```json
-{
-  "docs": {
-    "type": "doc", "route": "/docs", "label": "Documentation", "layout": "article",
-    "fields": { "title": "Title", "slug": "Slug", "body": "Body" },
-    "tree": {
-      "section": "Section", "order": "Order", "parent": "Parent", "product": "Product",
-      "sections": ["Getting started", "Guides", "Reference"],
-      "searchPath": "/docs",
-      "editPath": "Source",
-      "editBase": "https://github.com/owner/repo/edit/master/",
-      "products": [
-        { "key": "cms", "label": "barakoCMS", "href": "/docs" },
-        { "key": "press", "label": "barakoPress", "href": "/docs/press" }
-      ]
-    }
-  }
-}
-```
-
-| Key | What |
-| --- | --- |
-| `section` | The field holding the heading a page is grouped under |
-| `order` | The field holding its position in that section. A page with none comes after those with one |
-| `parent` | The field holding the slug of the page it hangs under, or a reference to it. A parent nobody has leaves the page at the top of its section rather than dropping it |
-| `product` | The field naming the product it documents, matched against a product's `key`. One field name and not a list, since this one goes into an API filter |
-| `sections` | The sections in the order the sidebar shows them. One not named here follows those that are. Named rather than worked out, because no ordering of the pages says which section comes first |
-| `products` | What the switcher offers: a key, the word a reader sees, and where it goes. A destination that is not a site path or an http URL is dropped |
-| `searchPath` | Where the search box submits, and whether one is drawn at all. Unset, no box, because only the site knows which of its routes reads the query |
-| `editPath` | The field holding the page's path in whatever repository it is written in. Its slug when unset |
-| `editBase` | Where "edit this page" points, with that path appended. Unset, no such link is drawn |
-| `limit` | The most pages read to build the tree. 500 unless set, and 500 is the ceiling as well as the default |
-
-An item page in such a collection draws the sidebar with the page being read marked, the switcher,
-a search box, previous and next from the tree's reading order, and the edit link. The sidebar is a
-`details` element, so it collapses on a phone with no script. `collectionTree(config, key, { product })`
-and `treeNeighbours(order, slug)` return the same tree and the same neighbours for a site's own page.
-
-**Search.** `searchCollection(config, key, query)` goes through barakoCMS's `/api/public/{type}/search`,
-which matches only over the fields a type publishes, so a draft or a field held back from public
-delivery can never come back. `createCollectionIndex(config, key, { search: true })` answers `?q=` with
-what matched instead of the index; that reads the query, so the route is dynamic and `output: "export"`
-refuses it, which is why it is off unless asked for. The box is a `form`, the results are links, and
-the keyboard handling on top ("/" to focus, the arrow keys to walk the results, escape to clear) is the
-one client component in the package. The root catch-all answers `?q=` on a collection index too, but
-only where the route may be dynamic: a request-time site rewrites to a kept route, and a kept route
-asking for the query fails rather than bailing out, so there the index lists and a page of blocks
-holding the `search` block is where a reader searches.
-
-Which is why `searchPath` exists rather than the box pointing at the collection's own route. Only the
-site knows which of its routes reads the query, and a box submitting somewhere that ignores `q` sends
-a reader to an unfiltered index that looks like a search which matched everything. Name the route that
-answers, or name nothing and get no box.
-
-**As blocks.** `docsSidebar`, `docsSwitcher` and `search` draw the same three on a page of blocks, each
-taking a collection key. `search` takes a bindable `query`, so a landing page binds `{{query.q}}` and
-the route file passes the query with `createPage(config, blocks, { query: true })`.
-
-### Pages and navigation from the Pages module
-
-With `BarakoCMS.Pages` installed, the CMS owns the page tree: which pages are in the menu, their
-order, their nesting and each page's path. Mount it with `pages`:
-
-```ts
-export const config = defineConfig({ sites: {}, pages: "" });
-```
-
-`""` is the site root. `"/docs"` serves the CMS page at `/about` on `/docs/about`. Leaving `pages` out
-means the site has no page tree, and nothing below asks for one. Then one catch-all route,
-`app/[[...path]]/page.tsx`, or `app/[...path]/page.tsx` when `app/page.tsx` keeps `/`:
-
-```tsx
-import { createPage, createPageMetadata } from "barakopress";
-import { blocks, config } from "@/press.config";
-
-export default createPage(config, blocks);
-export const generateMetadata = createPageMetadata(config);
-export const revalidate = 300;
-```
-
-- `createPage` reads `GET /api/public/pages/resolve?path=` and renders the page's blocks, or its
-  body, with breadcrumbs above the title when the page has a parent. Mounted on a `[slug]` route
-  instead, it reads the page type by slug as before.
-- `createSiteLayout` draws `GET /api/public/pages/navigation` in the header. `Navigation` draws the
-  items in the order it received them and links to the paths it was given, under the mount. It does
-  not sort, nest, filter or derive a path. A menu that cannot be read is no menu, not a broken page,
-  and while holding the holding page is left out of it.
-- A miss asks `GET /api/public/redirects/resolve?path=` before it is a 404, because a catch-all is
-  where a rebuilt site's old URLs land. A 301 answers as a permanent redirect and anything else as a
-  temporary one. A destination that is not a site path or an http or https URL is ignored.
-- **Reserved slugs.** Next answers a static route before a catch-all, so a root page slugged `blog`
-  or `feed.xml` would silently never render. At the root mount, a path whose first segment is
-  reserved is a 404 and is never asked for, and it is left out of the sitemap and static params with
-  a warning. The list is the first segment of each configured route plus `api`, `feed.xml`,
-  `sitemap.xml`, `robots.txt`, `_next`, `_share` and `favicon.ico`; `reservedSlugs` adds to it. Give
-  barakoCMS the same list as `Modules:Pages:ReservedSlugs` and an editor is refused the slug on save.
-- **Contract.** Both bodies carry `contract`, and this renderer reads the range in `PAGES_CONTRACT`
-  (1 to 1). A body outside it logs a warning and reads as absent: no menu, no page. A public site does
-  not stop rendering because a menu shape moved.
-- The sitemap lists the pages in the menu, and `createPageStaticParams` returns their path segments on
-  a build-time site, because the module publishes no other public list of paths. A page outside the
-  menu renders on request.
-
-`Navigation`, `Breadcrumbs`, `getNavigation(config)`, `getPageByPath(config, path)`,
-`getRedirect(config, path)` and `pageHref(config, path)` are exported for a site that draws its own
-layout. Every read goes through the same tagged, cached, per tenant read as the rest of the site.
-
-### Pages built from blocks
-
-A page can hold an ordered list of blocks in a json field, each `{ "type": ..., "props": { ... } }`.
-The blueprint's `page` type has no such field, so add one:
-
-```bash
-curl -X POST "$CMS_URL/api/content-types/page/fields" -H "authorization: Bearer $TOKEN" \
-  -H 'content-type: application/json' -d '{"fieldName":"Blocks","displayName":"Blocks","type":"json"}'
-```
-
-A page with a non-empty list renders its blocks. A page without one renders its `Body` as before.
-Field names come from `pageFields` in the config, and the type from `types.page`.
-
-```json
-[
-  { "type": "richText", "props": { "markdown": "## Hello" } },
-  { "type": "columns", "props": { "columns": [
-      [{ "type": "image", "props": { "src": "https://example.com/a.png", "alt": "A" } }],
-      [{ "type": "callToAction", "props": { "heading": "Talk to us", "label": "Contact", "href": "/contact" } }]
-  ] } },
-  { "type": "collection", "props": { "collection": "post", "limit": 3, "heading": "Latest" } }
-]
-```
-
-Blocks come in four layers.
-
-**Layout primitives** hold blocks and no content: `section` (a tone, a width and a padding step),
-`stack`, `row` (side by side, wrapping on a phone), `grid`, `flow`, `panel` (a card with a tone and
-a frame), `stickyBar` (a band that stays put while the page moves under it, at the top or the
-bottom), `spacer` and `divider`.
-
-`row` and `grid` take one list per cell, which suits a designer placing each one. `flow` takes a
-single list and lays out whatever is in it, which is what a `repeat` and a preset's `slot` produce:
-a card per row that came back, however many that is. Its column count is a choice and not a number,
-because only a string field takes a binding, and a preset has to pass its own `columns` through.
-
-**Content primitives** hold content and no layout: `text` (a variant from the theme's type scale),
-`richText` (markdown), `image`, `video`, `embed` (an iframe, only for a host in `embedHosts`),
-`icon`, `button`, `link`, `list`, `disclosure` (a labelled section that opens; give several the
-same `group` and only one is open at a time), `comparisonTable` (rows typed as lines with `|`
-between the cells, drawn as a real table with a heading on every column and every row) and
-`progressBar` (how far along one thing is, as `role="progressbar"` so it is read and not only seen).
-
-A comparison's first line is the column headings and the first cell of every line after it is that
-row's heading. What goes in a cell is whatever the tenant types, ticks and dashes included: a mark
-chosen inside the engine would be one more piece of English in the markup.
-
-**Motion primitives** are drawn finished and animate only away from that: `reveal` (a wrapper whose
-content lifts and fades in as it scrolls into view), `rotatingText` (a comma separated list of words,
-one shown at a time), `typingTerminal` (lines typed in sequence, held, then started again) and
-`codeSample` (a snippet with its language and one click to select the whole of it). `text` takes a
-`motion` of `countUp`, which counts a plain number up to the figure already written in the markup,
-and `flow` takes a `hueRotate` of `subtle` or `wide`, which turns each cell's hue through the
-theme's own colours in a cycle of three.
-
-All of it is CSS. There is no script, so a page with JavaScript off renders the terminal typed out,
-the figure at its number and the first word of the rotation standing, and every animation sits inside
-`prefers-reduced-motion: no-preference`, so a visitor who asked for less motion gets exactly the same
-finished page. "When it comes into view" is `animation-timeline: view()`, and a browser without it
-shows the finished state too. `src/blocks/motion.test.tsx` strips the guards out of every stylesheet
-these emit and fails if anything left animates or hides anything.
-
-Every primitive takes theme tokens and never a colour or a pixel value. Tones are `page`, `surface`,
-`accent`, `inverse` and `gradient` (the inverse band with the theme's three dark roles spread across
-it); spacing is `none` to `xxl` from `theme.space`; type is a role from
-`theme.text`; corners are `none`, `control`, `panel` or `pill`. A tenant that changes the scale
-changes every page built from primitives, and nobody can put one client's blue into a block.
-
-A tone belongs to the band and everything in it: a `section` or a `panel` publishes its ink, its
-accent and its hairline, and the blocks inside read those rather than the page's. That is what makes
-an inverse band readable, and it is why a block dropped anywhere still looks like it belongs.
-
-**Presets** are named arrangements of primitives, stored as data: the shipped library below, plus
-whatever a tenant saves of its own.
-
-**Data blocks** load and choose rather than draw: `source`, `repeat`, `showIf`, `pager` and `slot`.
-See bindings below.
-
-Also built in, from before the layers: `columns` (up to four lists of blocks), `callToAction` and
-`collection` (the newest posts, or authors or categories when the site has those routes). Pages
-already hold these and they render unchanged.
-
-A site adds its own blocks, or replaces a built-in, by registering a definition. The fields are the
-only description of the props: the renderer reads props through them, and `app/api/blocks` publishes
-them for an editor, so the two cannot drift.
-
-```tsx
-import { createBlockRegistry, defineBlock } from "barakopress";
-
-const pricing = defineBlock<{ plan: string; price?: number }>({
-  type: "pricing",
-  label: "Pricing",
-  fields: [
-    { name: "plan", kind: "text", required: true },
-    { name: "price", kind: "number", min: 0 },
-  ],
-  component: ({ props, theme }) => <p style={{ color: theme.colors.ink }}>{props.plan}: {props.price}</p>,
-});
-
-export const blocks = createBlockRegistry(config, [pricing]);
-```
-
-**Reading the schema from barakoBrew.** The console usually runs on another origin than the site, so
-a browser only lets its block editor read `app/api/blocks` when the site names that origin. Set
-`PRESS_CONSOLE_ORIGINS` to a comma separated list, for example
-`PRESS_CONSOLE_ORIGINS=https://brew.example.com`. It is read per request. Unset, no origin is
-allowed. A listed origin gets `Access-Control-Allow-Origin` echoed back on `GET` and on the `OPTIONS`
-preflight, never `*` and never credentials, and every answer carries `Vary: Origin`. Pass
-`{ consoleOrigins: [...] }` to both factories to set the list in code instead.
-
-Field kinds are `text`, `markdown`, `url`, `number`, `boolean`, `select` (with `options`) and `slots`
-(lists of nested blocks, handed to the component already rendered). The list is editor input, so a
-block renders only when its type is registered and every prop passes its field. A present but wrong
-value fails the whole block, a `url` must pass the same check markdown links do, and a component
-never receives a prop its fields did not declare. A page reads at most 400 blocks in total, nested
-ones included, and ten levels deep. The count is spent on every block the binder walks through as
-well as every one that comes out, so a band from the library costs eight or ten of it, and a page
-that goes over loses its tail with nothing said.
-
-`defineBlock<Props, SlotNames>` checks the fields against the props at compile time: every field
-names a prop, its kind suits the prop's type, and a prop that is not optional must be `required`.
-
-A component gets `props`, `slots` and `theme`, not the config, because a client component's props
-are serialised into the page and the config holds the CMS address. A server block that needs the
-config closes over it.
-
-A block that shows something depending on who is looking sets `perViewer: true`. `createPage` leaves
-such blocks out, because its output is cached and shared. `createViewerPage` renders them and calls
-`connection()` first, so that route is always dynamic. Signing a viewer in, and gating a block by
-role, is issue #7.
-
-### Bindings
-
-Any string prop can hold a placeholder, which is barakoCMS's workflow template syntax with an
-optional format and fallback:
-
-```json
-{ "type": "text", "props": { "value": "Welcome to {{site.Name}}", "variant": "display" } }
-{ "type": "text", "props": { "value": "{{item.Fee | money ?? Free}}" } }
-{ "type": "text", "props": { "value": "{{page.PublishedAt | date}}" } }
-```
-
-Scopes are `site` (the tenant's settings and resolved identity), `page` (the entry the page
-renders), `item` (the row inside a `source` or a `repeat`) and `query` (URL parameters). `viewer`
-arrives with #7. Formats are `text`, `date`, `datetime`, `time`, `money`, `number`, `upper` and
-`lower`; `money` uses the tenant's `Currency` setting, or a plain amount when it has none.
-
-Paths, formats and fallbacks only. There are no expressions and no JavaScript. Everything resolves
-on the server as the request's tenant, before a component is called, so a binding never makes the
-browser call the API. A placeholder that finds no value renders its fallback and is reported in the
-server log, never a crash. What a binding resolves to is checked against the field again, so a link
-whose stored field holds `javascript:` drops the block; and a resolved value is never rescanned, so
-one field cannot reach another through its own contents.
-
-`source` loads one entry or a page of them and puts it in scope. `repeat` renders its content once
-per row. `pager` draws prev and next links for the `source` it sits in, paged by the API. `showIf`
-keeps its content only when a bound value has something, or equals what it names.
-
-```json
-{ "type": "source", "props": {
-    "collection": "enrolments", "mode": "list", "pageSize": 20, "pageParam": "p",
-    "filterField": "Class", "filterValue": "{{query.class}}",
-    "content": [[
-      { "type": "repeat", "props": { "empty": "No one yet.", "content": [[
-        { "type": "text", "props": { "value": "{{item.Title}}" } }
-      ]] } },
-      { "type": "pager", "props": {} }
-    ]]
-} }
-```
-
-A filter narrows what the API already lets the reader see. It is never access control: who may read
-which rows is decided in barakoCMS. A page reads at most eight sources, and a `source` at most fifty
-rows a page.
-
-### Presets
-
-A preset is a named block saved as data, not code: a few props and an arrangement of primitives that
-reads them through the `props` scope. A designer saves one in barakoBrew and every site on the
-published image can use it, with no barakoPress release.
-
-```json
-{
-  "type": "band",
-  "label": "Band",
-  "fields": [
-    { "name": "heading", "kind": "text", "required": true },
-    { "name": "tone", "kind": "select", "options": ["page", "accent"] },
-    { "name": "content", "kind": "slots" }
-  ],
-  "blocks": [
-    { "type": "section", "props": { "tone": "{{props.tone}}", "content": [[
-      { "type": "text", "props": { "value": "{{props.heading}}", "variant": "title" } },
-      { "type": "slot", "props": { "name": "content" } }
-    ]] } }
-  ]
-}
-```
-
-A request-time site reads its tenant's presets from the `Presets` site setting. A build-time site
-passes them as `presets` in the config. A preset never replaces a block that is code. It does
-replace a preset, which is how a tenant adjusts one of the shipped blocks below without waiting for
-a release. A preset body may not use another preset saved in the same pass, so a cycle cannot form;
-it may use one compiled earlier, which is how a tenant's own block builds on a shipped one. `slot` marks where the content an editor dropped into the preset
-goes, and that content binds in the page's scope rather than the preset's.
-
-A preset that is not used says why, once, in the server log, with one line per reason rather than one
-catchall: an entry that is not a preset, a type that is not a name, a type an earlier preset already
-uses, a field list that is not a list, fields inside it that are not fields, a name a registered
-block already has, and the presets past the point where a tenant's bodies hold more than 400 blocks
-between them. A setting that quietly does nothing reads as done, which is worse than one that is
-missing. A bad paste is spelled out five times and then counted.
-
-### The block library
-
-Every site gets these, compiled in from the primitives. None of them is code, so a site that wants
-one to look different saves its own under the same name and that one wins.
-
-| Block | What it is | Props |
-| --- | --- | --- |
-| `hero` | The band at the head of a page | heading, body, image, imageAlt, primaryLabel, primaryHref, secondaryLabel, secondaryHref, tone, columns, align, padding |
-| `band` | Copy with one call to action | tone, heading, body, label, href, align, padding, width |
-| `statBand` | A row of figures | heading, tone, columns, padding, items |
-| `cardGrid` | Cards from a collection | heading, collection, filterField, filterValue, empty, tone, columns, padding, hueRotate, option |
-| `peopleGrid` | People from a collection, typed in place, or both | heading, collection, filterField, filterValue, role, tone, columns, padding, items |
-| `timeline` | Dated entries | heading, tone, padding, width, items |
-| `steps` | Numbered entries | heading, tone, padding, width, items |
-| `tiers` | Giving or pricing tiers | heading, tone, columns, padding, items |
-| `keyValueTable` | A panel of facts | heading, tone, padding, radius, rows |
-| `tabs` | Sections that open | heading, tone, padding, width, items |
-| `announcement` | The one line above everything, and it stays there | message, label, href, tone, edge, align |
-| `codeTabs` | A snippet to run, with the other ways behind it | heading, body, code, language, selectLabel, tone, padding, width, items |
-| `progressList` | How far along each entry of a collection is | heading, collection, filterField, filterValue, empty, tone, padding, width |
-| `changelogList` | Release entries, with the word for the kind of release | heading, collection, filterField, filterValue, empty, tone, padding, width |
-| `faq` | Questions, all openable at once | heading, body, tone, padding, width, items |
-| `map` | An embedded map, held to `embedHosts` | src, title, heading, aspect, tone, padding |
-| `stat` | One figure and its label | value, label, align, motion |
-| `timelineEntry` | One dated entry | date, title, body |
-| `step` | One numbered step | number, title, body |
-| `tier` | One tier | name, amount, body, label, href, tone |
-| `person` | One person | name, role, photo, href, linkLabel, align |
-| `keyValueRow` | One fact | label, value |
-| `codeTab` | One more way to run it | label, code, language, selectLabel, group |
-| `faqItem` | One question and its answer | question, answer, tone |
-
-The blocks in the second half go in the first half's slots: stats in a `statBand`, entries in a
-`timeline`, `disclosure` blocks in `tabs`, `codeTab` blocks in `codeTabs`, `faqItem` blocks in
-`faq`. A card grid reads its entries through `{{item.Title}}`, `{{item.Summary}}`,
-`{{item.Date | date}}` and `{{item.Href}}`, so it works against whatever the tenant calls those
-fields, and it takes the collection as a prop rather than knowing any name.
-
-Set a card grid's `option` to `show` and each card carries the glyph and the word the site declared
-for that entry's option, read through `{{item.Icon}}` and `{{item.Word}}`. With `filterField` and
-`filterValue` picking the category, that is a module grid: one band per category, each card marked
-with its own. It is off by default, so a grid that did not ask for it draws what it always drew.
-
-`progressList` reads its figure through `{{item.Progress}}`, which is the collection's `progress`
-field role: the tenant says which of its own fields holds a number from 0 to 100. `changelogList`
-does not group by itself, because grouping means knowing which field holds the kind and that is the
-tenant's field name. One band per kind with `filterField` and `filterValue` is the grouping, and the
-chip on each entry is the option's own word.
+## What it renders
+
+Each of these is its own page in `docs/`, because npm shows only the first 64 KiB of a README.
+
+- [Collections](https://github.com/BaryoDev/barakoPress/blob/master/docs/collections.md): any content type as a list and a detail page, with
+  references, related items, a long-form article layout, and a collection drawn as a docs tree with
+  sections, products, search and an in-page index.
+- [Pages](https://github.com/BaryoDev/barakoPress/blob/master/docs/pages.md): the Pages module's page tree and menus at a mount, reserved slugs,
+  and pages built from blocks: layout and content primitives, lists and groups, the block budget.
+- [Bindings](https://github.com/BaryoDev/barakoPress/blob/master/docs/bindings.md): `{{site.X}}`, `{{page.X}}`, `{{item.X}}` and `{{query.X}}`
+  in a block's props, sources that read a collection, repeats, counts, sums and groups.
+- [Presets, the block library and plugins](https://github.com/BaryoDev/barakoPress/blob/master/docs/blocks.md): named arrangements of primitives,
+  the blocks every site gets, and plugin packages built into a derived image.
+- [Sites and the header](https://github.com/BaryoDev/barakoPress/blob/master/docs/sites.md): one image serving many sites, identity and theme from
+  each tenant's settings, labels, holding mode and share links, and the built-in header.
+- [The look](https://github.com/BaryoDev/barakoPress/blob/master/docs/look.md): the theme, tokens and tones, style recipes, inline marks, and assets
+  used exactly as supplied.
+- [Caching and the webhook](https://github.com/BaryoDev/barakoPress/blob/master/docs/caching.md): what a publish drops, running more than one
+  container, the render cache, the one secret, and a key per tenant.
+- [Deploying](https://github.com/BaryoDev/barakoPress/blob/master/docs/deploying.md): the reference app, its container image, the compose stack and
+  the BaryoVM release manifests.
 
 ## Configuring it
 
@@ -632,7 +194,7 @@ for a post type with no such field.
 
 | Key | Default | Tenant setting | What |
 | --- | --- | --- | --- |
-| `site` | required | `Name`, `Tagline`, `Url` and one per field | Name, tagline and absolute origin. Every absolute link is built from the origin |
+| `site` | required | `Name`, `Tagline`, `Url` and one per field | Name, tagline and absolute origin. Every absolute link is built from the origin. `analyticsScript` and `analyticsWebsiteId` (`AnalyticsScript`, `AnalyticsWebsiteId`) put a Umami script in the head, from an origin in `PRESS_SCRIPT_ORIGINS` |
 | `types` | `post`, `author`, `category` | operator only | The content type names |
 | `fields` | the blueprint's PascalCase names | operator only | Which field holds what |
 | `pageFields` | the blueprint's PascalCase names | operator only | Which field on the page type holds what |
@@ -644,20 +206,20 @@ for a post type with no such field.
 | `locale` | `en-GB` | `Locale` | Passed to `toLocaleDateString` |
 | `currency` | none | `Currency` | The ISO code a `money` binding formats with. Unset, an amount renders as a plain number |
 | `embedHosts` | seven player hosts | `EmbedHosts` | The hosts an `embed` block may frame |
-| `presets` | none | `Presets` | Named blocks saved as arrangements of primitives. See Presets |
+| `presets` | none | `Presets` | Named blocks saved as arrangements of primitives. See [Presets](https://github.com/BaryoDev/barakoPress/blob/master/docs/blocks.md#presets) |
 | `cmsUrl` | `CMS_URL`, or `http://localhost:5005` | operator only | Where the CMS is, from this server. The variable is read when the CMS is called, not when this file runs |
 | `tenant` | `CMS_TENANT` | operator only | Tenant slug, for a multi-tenant deployment. On a request-time site, pins every host to it. The variable is read when the CMS is called, not when this file runs |
-| `sites` | off | operator only | Request-time identity and theme from the tenant's site settings. See below |
+| `sites` | off | operator only | Request-time identity and theme from the tenant's site settings. See [One build, many sites](https://github.com/BaryoDev/barakoPress/blob/master/docs/sites.md#one-build-many-sites) |
 | `pages` | off | operator only | Where the Pages module's pages are mounted. `""` is the site root. It has to match a route file on disk, which is why it is not a tenant's to set |
 | `reservedSlugs` | the routes and the engine's files | `ReservedSlugs`, added to them | First path segments a root-mounted page may not take. Adds to the defaults |
 | `regions` | off | `HeaderPath`, `HeaderTone`, `FooterPath`, `FooterTone` | The header and the footer as block regions |
-| `collections` | the blog's `post`, `author` and `category` | `Collections` | Content types rendered as lists and detail pages. See Collections |
+| `collections` | the blog's `post`, `author` and `category` | `Collections` | Content types rendered as lists and detail pages, with each index's copy, index page and default byline. See [Collections](https://github.com/BaryoDev/barakoPress/blob/master/docs/collections.md) |
 | `optionStyles` | none | `OptionStyles` | Tone, icon and label by `type.field` and option, for `colorBy` |
 | `optionColors` | none | `OptionColors` | The same, when a tone is all an option has. Read as `optionStyles` |
-| `labels` | English | `Labels` | The words the screens print for a visitor. See below |
-| `store` | in process | operator only | Where the state a fleet has to agree on is kept: kept answers, the host map, the replay guard, the generation of each cache tag. Needed only when more than one container serves the site. See below |
-| `home` | the post index | `HomePath`, `HomeCollection` | What `createHome` serves at `/`. See below |
-| `theme` | the barakoCMS palette | `Colors`, `Fonts`, `Radii`, `Layout`, `Space`, `Text` | Colours, faces, radii and column widths. See below |
+| `labels` | English | `Labels` | The words the screens print for a visitor. See [Sites](https://github.com/BaryoDev/barakoPress/blob/master/docs/sites.md) |
+| `store` | in process | operator only | Where the state a fleet has to agree on is kept: kept answers, the host map, the replay guard, the generation of each cache tag. Needed only when more than one container serves the site. See [Running more than one container](https://github.com/BaryoDev/barakoPress/blob/master/docs/caching.md#running-more-than-one-container) |
+| `home` | the post index | `HomePath`, `HomeCollection` | What `createHome` serves at `/`. See [Sites](https://github.com/BaryoDev/barakoPress/blob/master/docs/sites.md) |
+| `theme` | the barakoCMS palette | `Colors`, `Fonts`, `Radii`, `Layout`, `Space`, `Text`, `Tokens`, `Tones`, `StyleRecipes` | Colours, faces, radii, column widths, a site's own named values and tones, and the looks its blocks can name. See [The look](https://github.com/BaryoDev/barakoPress/blob/master/docs/look.md) |
 
 The third column is the whole of the split. A key marked operator only is one the image decides for
 every tenant it serves, and each is that for a reason you can name: `types`, `fields`, `pageFields`
@@ -680,445 +242,28 @@ per request, so when a value was read depended on which value it was.
 | `CMS_URL` | Where the delivery API is. `cmsUrl` in the config wins |
 | `CMS_TENANT` | Pins the process to one tenant. `tenant` in the config wins |
 | `CMS_DEFAULT_TENANT` | The tenant for a host the CMS does not know. `sites.defaultTenant` wins |
-| `CMS_RENDERER_KEY` | Sent to the CMS when a share link is redeemed. See [Share links](#one-build-many-sites) |
+| `CMS_RENDERER_KEY` | Sent to the CMS as `X-Barako-Renderer-Key` on every delivery read when the CMS URL is https or loopback, and when a share link is redeemed, so the CMS rate limits by renderer. See [Share links](https://github.com/BaryoDev/barakoPress/blob/master/docs/sites.md#one-build-many-sites) |
 | `PRESS_CONSOLE_ORIGINS` | Browser origins allowed to read the block schema, comma separated |
-| `PRESS_SECRET` | The HMAC key for everything this renderer signs. See [One secret](#one-secret) |
+| `PRESS_SECRET` | The HMAC key for everything this renderer signs. See [One secret](https://github.com/BaryoDev/barakoPress/blob/master/docs/caching.md#one-secret) |
 | `REVALIDATE_SECRET` | The webhook key before `PRESS_SECRET`, read only while that is unset |
 | `PRESS_PREVIEW_SECRET` | The share key before `PRESS_SECRET`, read only while that is unset |
+| `PRESS_FONT_ORIGINS` | The origins a font stylesheet may be linked from. Unset, Google Fonts only. See [One build, many sites](https://github.com/BaryoDev/barakoPress/blob/master/docs/sites.md#one-build-many-sites) |
+| `PRESS_SCRIPT_ORIGINS` | The origins a site's Umami script (`AnalyticsScript`) may be loaded from. Unset, none, so no script is rendered. Read when a page renders, so a cached page keeps its tag until it renders again. See [One build, many sites](https://github.com/BaryoDev/barakoPress/blob/master/docs/sites.md#one-build-many-sites) |
 
 Values are used exactly as the environment has them, untrimmed. A secret with a trailing space is a
 different HMAC key, so trimming one here would stop a webhook that verifies today.
 
+The reference app's `Dockerfile` also takes two build arguments, read when the image is built and
+not by the package: `PRESS_DEPLOY` names a directory under `deploy/` to lay over the reference app,
+and `PRESS_TRAILING_SLASH=true` sets Next's `trailingSlash` in `next.config.ts`. See
+[The reference deployment](https://github.com/BaryoDev/barakoPress/blob/master/docs/deploying.md#the-reference-deployment-in-this-repository).
+
 **A site is build time or request time.** Without `sites`, identity is build time: the index, the
 feed, the sitemap and robots are prerendered, so anything *your own* `press.config.ts` reads from the
 environment is baked when you build, not when the server starts. Write per-site values as literals in
 that file. Getting this wrong is how a client site ships with the vendor's name in its masthead. With
-`sites`, identity is data in the CMS and read per request, which is the next section.
-
-### One build, many sites
-
-barakoCMS D22 reverses "identity is build time" for the shared renderer: every site runs the same
-image, and what makes a site that site is its tenant's `site` settings entry, edited in barakoBrew.
-
-```ts
-export const config = defineConfig({ sites: {} });
-```
-
-A request-time site puts its page routes under one tenant segment and adds a `proxy.ts` beside
-`app/`:
-
-```
-proxy.ts                              export default createPressProxy(config)
-app/
-  %5Fpress/[site]/                    the tenant segment. %5F is `_`, which Next reads as a
-    layout.tsx                        private folder when it is written plainly
-    page.tsx
-    [...path]/page.tsx
-    blog/[slug]/page.tsx
-  feed.xml/route.ts                   these resolve their own tenant and stay where they are
-  robots.ts
-  sitemap.ts
-  api/...
-  %5Fshare/route.ts
-```
-
-```ts
-// proxy.ts
-import { createPressProxy } from "barakopress";
-import { config } from "@/press.config";
-
-export default createPressProxy(config);
-```
-
-The proxy resolves the tenant and the share session once and rewrites to
-`/_press/<tenant>~<gate>~<host>/<path>`. The pages read all three out of that segment, so nothing in
-a page reads a header or a cookie, and Next can keep the render. Why the tenant has to be in the
-path, and what is cached and what is not, is [The render cache](#the-render-cache) below. A build-time
-site needs none of this and keeps its routes where they are.
-
-On each request the engine resolves the tenant, reads that tenant's settings, and renders with them:
-
-1. `CMS_TENANT` (or `tenant`) set: every host is that tenant, with no lookup.
-2. `sites.tenantHeader` set and the request carries a valid handle in it: that tenant. Off by default.
-3. The host, from `sites.hostHeader` (default `host`), looked up with `GET /api/tenants/by-host/{host}`.
-4. `sites.defaultTenant`, or `CMS_DEFAULT_TENANT`, read at request time.
-5. None of those: a 404. Never another tenant's site.
-
-A handle is only ever read from the request through a header the operator named. `X-Tenant` and
-`X-Forwarded-Host` sent by a caller are ignored unless you configure them, and you should configure
-them only behind a proxy that sets the header and strips a caller's value.
-
-The settings are the singleton `site` type from barakoCMS `docs/site-settings.md`
-(`POST /api/content-types/blueprints/site`, then publish its one entry). The engine reads `Name`,
-`Tagline`, `Url`, `Locale`, `Logo`, `LogoAlt`, `FooterLogo`, `Favicon`, `ShareImage`, `Copyright`,
-`Colors` (the theme slots), `Fonts` (a family name per role, and the stylesheet that loads it),
-`Radii`, `Layout`, `TopBar`, `HeaderLinks`, `FooterColumns`, `SocialLinks`, `HeaderPath`,
-`HeaderTone`, `FooterPath`, `FooterTone`, `AssetsAsSupplied`, `LogoAsSupplied`, `LogoClearSpace`,
-`PageSizes`, `ReservedSlugs`, `Labels`, `HomePath` and `HomeCollection`. `Collections`, `OptionStyles` and `OptionColors` are read as the collections section
-describes. `Variants` are not rendered yet. Every value is checked for shape; one that fails, and any the
-entry leaves out, keeps the configured value, so a half-filled theme renders. A link is a path on the
-site or an absolute http or https URL. Set `Url`: without it the feed and sitemap fall back to the
-host the tenant was found by.
-
-`createSiteLayout` and `createSiteMetadata` render the root layout from all of this: `lang`, the
-faces, the palette, the top bar, header links, footer columns, social links and the copyright line.
-
-**What the site serves at `/`.** Every site used to be a blog at the root, because the root route
-mounted the post index and nothing else could be named:
-
-| Field | Type | What |
-| --- | --- | --- |
-| `HomePath` | string | A site path such as `/home`. The page the Pages module serves there is the home page. Nothing served there falls back to the index, so naming a page before writing it is safe |
-| `HomeCollection` | string | The key of a collection. Its index is the home page. `HomePath` wins when both are set |
-
-Neither set, `/` is the post index, which is what it was. The blog's own `post`, `author` and
-`category` are ordinary `Collections` entries now, so a school whose news lives in `article` with a
-`Headline` replaces `post` in its settings and gets both its list and its item pages from that entry.
-The RSS link in the built-in header, and the feed alternate in the page metadata, appear only when
-some collection has `feed` on, so a clinic with no posts stops advertising an empty feed.
-
-**The words a visitor reads.** `Labels` is the visitor-facing copy, key by key. A school setting
-`Locale` to `fil-PH` used to get Filipino dates beside English "min read" and "Related":
-
-```json
-{ "Labels": { "minRead": "minutong pagbasa", "by": "ni", "related": "Kaugnay" } }
-```
-
-| Key | English |
-| --- | --- |
-| `minRead` | `min read` |
-| `by` | `by` |
-| `related` | `Related` |
-| `relatedNote` | `cosine similarity, computed on load, not curated` |
-| `featured` | `Featured` |
-| `back` | `Back` |
-| `home` | `Home` |
-| `preview` | The banner over a draft being previewed |
-| `untitled` | `Untitled` |
-| `feed` | `RSS` |
-| `empty`, `emptyNote` | The notice on an index with nothing published |
-| `failed`, `failedNote` | The notice on an index whose read failed |
-| `shareInvalid` | `This link is not valid or has expired.` |
-
-A key left out, or saved as anything but a word, keeps the English, so a half-filled map reads. A
-build-time site passes `labels` to `defineConfig`. Nothing about a site's own content is here: a
-collection's heading is its `label` and how its count reads is its `noun`.
-
-**The colour slots, by role.** `Colors` sets any slot of the palette, one at a time. The slots are
-`pageBg`, `surface`, `ink`, `proseInk`, `secondaryInk`, `muted`, `hairline`, `accent`, `accentHover`,
-`accentInk`, `accentTint`, `accentTintBorder`, `accentBorderStrong`, `inverse`, `inverseChrome`,
-`inverseInk`, `inverseAccent`, `code` and `success`. A role says where a colour goes rather than what
-it looks like: `inverse` is the band that reverses the page, the footer and a code panel and an
-inverse block, so a bakery with a cream footer sets `inverse` to cream and reads right doing it.
-
-```json
-{ "Colors": { "accent": "#17458F", "inverse": "#F4E3C1", "inverseInk": "#3B2A17" } }
-```
-
-Six slots shipped in 0.3.0 under barakocms.com's own names, and those still work: `darkPanel`,
-`darkPanelChrome`, `darkPanelInk`, `darkPanelAccent`, `codeGreen` and `accentTintBorderStrong` are
-read into `inverse`, `inverseChrome`, `inverseInk`, `inverseAccent`, `code` and `accentBorderStrong`.
-Setting either name sets both, so a tenant saved before the rename keeps its site and a consumer's
-own component reading `theme.colors.darkPanel` keeps compiling. The old names are deprecated and go
-in 2.0.0. An `OptionStyles` or `OptionColors` entry naming an old slot resolves too.
-
-Sizes work the same way. `Text` is the type scale by role, `meta`, `small`, `body`, `lead`,
-`subheading`, `heading`, `title`, `display` and `pageTitle`, and `Space` is the spacing scale. The
-blocks and the screens read those names, so a tenant that wants bigger headings sets `title` once
-instead of asking for a release.
-
-**How many items, per tenant.** `PageSizes` sets the four counts for this site, each on its own:
-
-```json
-{ "PageSizes": { "index": 50 } }
-```
-
-A bakery listing 50 products and an agency listing 9 case studies run the same image. A key the
-entry leaves out keeps the configured count, and a collection's own `pageSize` still wins over the
-site's. barakoCMS clamps a public list at 100 whatever is asked for, so a larger number is not an
-error and does not buy more rows.
-
-**Paths this site does not serve.** `ReservedSlugs` adds to the configured reserved list:
-
-```json
-{ "ReservedSlugs": ["shop", "status"] }
-```
-
-A first segment on it is left out of the menu and the sitemap, and a page there is never asked for.
-It is what a proxy in front of this domain answers instead of the renderer, which is a fact about
-one tenant rather than about the image. It only ever adds: a tenant cannot free a segment the app's
-own routes already hold, because a page there would sit behind a route file and render nowhere. A
-tenant's collection routes need no entry, since those are read off its settings already.
-
-**Fonts, from an allow list.** A family name on its own is loaded from Google Fonts, which is what it
-has always meant:
-
-```json
-{ "Fonts": { "heading": "Zilla Slab" } }
-```
-
-A site that cannot use Google Fonts, a school with a licensed face on its own host or a tenant that
-must not send visitor addresses to a third party, names the stylesheet instead:
-
-```json
-{ "Fonts": { "heading": { "family": "Zilla Slab", "url": "https://type.school.example/zilla.css" } } }
-```
-
-That URL is a tenant's setting on its way into a `<link>` in every visitor's page, so which origins a
-page may reach is the deployment's decision and not the tenant's. `PRESS_FONT_ORIGINS` is the list:
-origins separated by commas or spaces, each `https://host`, a bare host read as https.
-
-| `PRESS_FONT_ORIGINS` | What a page may link |
-| --- | --- |
-| unset or blank | Google Fonts, and nothing else. This is what every site rendered before the list existed |
-| `https://type.school.example` | That origin only. Nothing goes to Google Fonts, the built-in link and its preconnects included |
-| `fonts.googleapis.com, type.school.example` | Both |
-
-A URL on any other origin is refused: no link to it is rendered, the role falls back to its family
-name, and the server log says so once rather than once a page view. The list replaces the default
-rather than adding to it, which is what gives a tenant that must not reach Google Fonts a deployment
-where nothing can. `createSiteLayout(config, { loadFonts: false })` still turns off every font link
-for the whole image.
-
-Only an absolute https URL is kept, for the whole chain: http is blocked as mixed content on every
-site this serves, so allowing it would mean rendering a link that never loads. A role the tenant names
-is the tenant's, family and stylesheet together, so a family set with no url clears a configured
-stylesheet rather than leaving the page loading a face it no longer uses. A build-time site sets the
-same thing in `theme.fontSources`, and it is held to the same list.
-
-**Header and footer as block regions.** The built-in header and footer take links and text and
-nothing else, so a clinic that wants a light footer with opening hours and a map cannot have one, and
-a school that wants an enrolment banner with a button cannot either. Point a region at a page and its
-blocks are drawn there instead, resolved and bound exactly as the page route resolves and binds them.
-
-| Field | Type | What |
-| --- | --- | --- |
-| `HeaderPath` | string | A site path such as `/site/header`. The page served there is drawn in place of the top bar and the header band |
-| `HeaderTone` | string | `page`, `surface`, `accent` or `inverse`: the tone behind the header region. `page` when unset or not one of the four |
-| `FooterPath` | string | A site path such as `/site/footer`. The page served there is drawn in place of the footer |
-| `FooterTone` | string | The same four names, behind the footer region |
-
-Set neither and nothing changes: `TopBar`, `HeaderLinks`, `FooterColumns`, `SocialLinks` and
-`Copyright` draw the built-in chrome with the markup they always had, which is what keeps a site
-whose own CSS keys off that markup rendering. A path with nothing served at it does the same, so
-naming a page before writing it is safe, and so is a typo.
-
-A region page is chrome rather than somewhere to go, so it is left out of the menu and the sitemap.
-It still answers on its own route, which is how an editor opens it to work on it.
-
-A header region replaces the whole band, the site name, the menu and the RSS link along with the top
-bar. There is no navigation or logo block yet, so a header region lists its own links until the block
-library has one.
-
-A build-time site sets the same thing in its config, and a tenant's settings win over it:
-
-```ts
-export const config = defineConfig({
-    site: { name: "Mabini Clinic", url: "https://clinic.example" },
-    pages: "",
-    regions: { footer: { path: "/site/footer", tone: "surface" } },
-});
-```
-
-The registry the regions render with is the one passed to `createSiteLayout(config, { blocks })`, and
-the built-in blocks when none was passed.
-
-**Caching per tenant.** Every read carries the tenant in `X-Tenant` and in its cache tag,
-`<cacheTag>:<tenant>`, and a narrower tag beside it: `<tenant tag>:entry:<type>:<slug>` on a read of
-one entry, `<tenant tag>:type:<type>` on a list, a search, the settings and the page tree. The webhook
-purges the tags of the tenant its host resolves to, so point each tenant's webhook at
-`https://<that tenant's domain>/api/revalidate`, signed with that tenant's own key (see
-[One key per tenant](#one-key-per-tenant)). A publish on one tenant leaves every other tenant's cached
-reads in place.
-
-**When the CMS is down.** Each successful read is also kept in the store, keyed by CMS, tenant and path.
-A read that fails with a network error, a 5xx, or no answer within `cmsTimeoutMs` answers from the
-last good copy and logs a warning; the next successful read replaces it. For ten seconds after such a
-failure that read answers from the copy without asking the CMS, so an outage costs one request per
-read every ten seconds rather than one per visitor. The same holds after a purge: a publish that lands
-within those ten seconds shows once the ten seconds are up. Known hosts keep resolving the same way. A page that was cached
-for a tenant keeps answering 200 with that tenant's identity and theme. A tenant never gets another
-tenant's kept answer.
-
-**Holding mode.** A tenant can show a holding page on every route in place of its site, for a launch,
-maintenance or a seasonal break, and share the real site with a few people through site share links.
-Three fields on the `site` entry control it:
-
-| Field | Type | What |
-| --- | --- | --- |
-| `Mode` | string | `Live` or `Holding`. Unset, or anything else, is `Live` |
-| `HoldingPath` | string | A site path such as `/coming-soon`. The page the Pages module serves there is the holding page. Empty, or nothing served there, renders the default holding page: the name, the tagline and `HoldingMessage`, in the theme |
-| `HoldingMessage` | string | The line the default holding page shows under the name and tagline, as text, for example `Closed until 6 January.` Unset or blank shows no line. Read only while holding. For more than a sentence, use `HoldingPath` |
-
-Holding is presentation, not access control: the API still delivers every published entry. Content
-that must stay hidden before launch stays unpublished with a scheduled publish.
-
-While a tenant is holding, for that tenant only:
-
-- every page answers the holding page with `noindex` and `Cache-Control: private, no-store`. A page
-  stops in `siteConfig` with a not-found before it reads anything, so its content and its title never
-  reach the response. Next has already sent the status by then, so it is 200, the same for a path
-  that exists and one that does not;
-- the holding page is read with `GET /api/public/pages/resolve?path=<HoldingPath>` and rendered with
-  the page renderer and the registry passed to `createSiteLayout(config, { blocks })`;
-- a link to `HoldingPath` is left out of the header, top bar and footer. `feed.xml` and `sitemap.xml`
-  are 404 for everyone, session or not, and `robots.txt` answers `Disallow: /` with no sitemap line;
-- route handlers (revalidate, blocks, `/_share`, `/api/share/redeem`) and `/_next/static` are served
-  as usual.
-
-Switching `Mode` is a publish: the webhook drops the tag the settings read carries and the next
-request reads the new settings. No deploy.
-
-**Site share links.** barakoCMS creates, lists and revokes them; anyone who may update the `site` type
-can. A client is given `{site Url}/_share#{key}`. The key is in the fragment, so no server log, proxy
-or referrer sees it:
-
-1. `/_share` is a tiny page. Its script reads the fragment, removes it from the address and history,
-   and posts the key in a form to `/api/share/redeem`. Without JavaScript it says the link needs
-   JavaScript. No key is ever accepted in a query string.
-2. `/api/share/redeem` asks barakoCMS once, `POST /api/public/site/share-links/redeem` with the key in
-   the body and the tenant header. On 200 it sets `__Host-press-share` (HttpOnly, Secure,
-   SameSite=Lax, Path=/, no Domain, so only that host gets it) and answers a `no-store` 303 to `/`.
-   On 404, 429 or any failure it sets nothing and sends the visitor to `/#share-invalid`, the holding
-   page with "This link is not valid or has expired." A post whose `Origin` or `Sec-Fetch-Site` names
-   another site is refused the same way. The key is never logged.
-3. With a valid cookie that visitor sees the real site for that tenant. A forged, expired or
-   other-tenant cookie is ignored.
-
-The cookie holds no key. It is an expiry and an HMAC-SHA256 over the tenant and that expiry, so each
-later request is checked in process without asking the CMS, and a cookie made for one tenant opens no
-other. It needs one setting:
-
-| Variable | What |
-| --- | --- |
-| `PRESS_SECRET` | The HMAC key, at least 32 characters, for example `openssl rand -base64 48`. Read per request. Unset or shorter, no session is issued or accepted and everyone gets the holding page. Every instance behind one domain needs the same value. `PRESS_PREVIEW_SECRET` is read in its place when `PRESS_SECRET` is unset. See [One secret](#one-secret) |
-| `CMS_RENDERER_KEY` | Optional. Sent to barakoCMS as `X-Barako-Renderer-Key` when a link is redeemed, and must match the renderer key barakoCMS is configured with. Read per request and never logged. Unset, no key header is sent |
-
-**Redemption is rate limited per tenant and visitor.** Every redemption leaves this container from the
-same address, so barakoCMS needs the visitor's address to tell visitors apart. Name the header a
-proxy in front sets it in, `sites: { visitorIpHeader: "x-real-ip" }`, and it is sent on as
-`X-Barako-Visitor-IP`. Name it only behind a proxy that sets that header and strips a caller's value,
-the same rule as `hostHeader` and `tenantHeader`. A value that is not exactly one IPv4 or IPv6
-address, a comma separated list included, is not sent. barakoCMS trusts the address only when
-`CMS_RENDERER_KEY` matches, so both are needed for a per visitor limit. With no header named nothing
-is sent: a Next route handler never sees the socket's address, and the `X-Forwarded-For` Next adds
-keeps whatever a caller put there.
-
-**A session lasts until the link expires or for 24 hours, whichever is sooner.** Opening the link
-again starts a new one while the link is valid. **A revoked link can keep working for up to 24
-hours** for someone who already opened it, because the session is checked here, not in barakoCMS. To
-end every session now, change `PRESS_SECRET`, which does it for every tenant on that
-deployment, and changes every tenant's webhook key with it.
-
-Whether a request gets the holding page is decided by the proxy, from the cookie, once per request,
-and the answer is a segment of the path the render is kept under. A render made for a visitor with a
-session is never served to one without, or the reverse, because the two are different paths. A page
-you write by hand must call `siteConfig(config, params)` before it reads or renders anything, which
-is what keeps it behind the holding page and what gives it its tenant. A build-time site has no
-settings entry and no holding mode.
-
-`generateStaticParams` factories return nothing on a request-time site, since there is no tenant at
-build. `scripts/two-hosts.sh` runs the built reference app against a stand-in CMS with two tenants
-and checks all of the above; CI runs it on every push.
-
-### The look is configuration too
-
-The post screen styles itself from `config.theme`, inline, so it renders correctly whether or not you
-import `barakopress/styles.css`. That import is optional and a screen that needs it renders unstyled
-for anyone who skips it, which is exactly what happened: barakocms.com never imported it, got an
-article at x=0 on a blank page, and stopped using the screen at all.
-
-```ts
-export const config = defineConfig({
-  site:  { name: "Client Three", url: "https://clientthree.example" },
-  theme: { colors: { accent: "#008060" }, layout: { prose: "68ch" } },
-});
-```
-
-Each group merges over the defaults on its own, so setting one colour keeps the other seventeen. The
-groups are `colors` (18 values), `fonts` (`heading`, `body`, `mono`), `radii` (`panel`, `control`,
-`pill`) and `layout` (`prose`, `wide`, `gutter`). `DEFAULT_THEME` is exported if you want to read the
-values or build a palette from them.
-
-Loading the faces is the site's job, not the engine's. The default theme names Sora, Manrope and
-JetBrains Mono with real fallback stacks, and a `<link>` in your root layout is what makes them
-arrive. `createSiteLayout` writes that link for you: a family name from Google Fonts, or the
-stylesheet named in `theme.fontSources` when the face is not loaded from there, held to
-`PRESS_FONT_ORIGINS` either way.
-
-**Three slots**, for what belongs to the site rather than the engine:
-
-```tsx
-<PostView
-  config={config}
-  post={post}
-  headerBackdrop={<Bean />}      {/* decoration behind the header band */}
-  beforeBody={<RoleStrip />}     {/* a wide band under the header */}
-  afterBody={<Newsletter />}     {/* the foot of the reading column */}
-/>
-```
-
-They are not a way to compose a post out of arbitrary sections. Anything that has to sit between two
-paragraphs belongs to the block model, which is issue #6, because only the body knows where it goes.
-
-Read time is derived from the body at 200 words a minute, with fenced code blocks excluded, so there
-is no field to fill in and nothing to keep in sync.
-
-### Assets used exactly as supplied
-
-Some marks come with an identity manual: never recoloured, never outlined, never put in a box, never
-crowded. A renderer that rounds a corner or drops a logo into a tinted panel breaks that rule, and on
-screen it looks like a nice touch. Mark the asset and it is drawn from the file, with a minimum clear
-space held around it, everywhere the engine draws an image.
-
-```ts
-export const config = defineConfig({
-  site:  { name: "The club", url: "https://club.example", logo: "/mark.svg" },
-  theme: { asSupplied: [{ url: "/mark.svg", clearSpace: "lg" }] },
-});
-```
-
-A tenant says the same thing in its site settings:
-
-| Field | Type | What |
-| --- | --- | --- |
-| `AssetsAsSupplied` | list | URLs, or `{ "url": "...", "clearSpace": "lg" }` for one that needs more room. A list saved empty clears the configured one |
-| `LogoAsSupplied` | boolean | Marks `Logo` and `FooterLogo`, so replacing the logo file does not mean editing a second setting that names the old one |
-| `LogoClearSpace` | string | The clear space around those two |
-
-The clear space is a name from the theme's spacing scale (`none`, `xs`, `sm`, `md`, `lg`, `xl`,
-`xxl`), `md` when unset, and it is a minimum: a block asking for more gets more, a block asking for
-less gets the site's. A URL is matched without its query, so a mark the CMS resized with `?w=480` is
-still that mark.
-
-What a marked asset gets is the file: no tint, no border, no corner, no shadow, no filter, no crop,
-and the clear space around it at every width. A block that asked for a frame draws the mark alone
-instead, which is what the `image` block's own `asSupplied` and `clearSpace` props are for when the
-site has not listed the file. It holds in the header, the footer, the holding page, a header or
-footer region, a page block, a preset, a post's cover image, a collection item's image and an image
-inside markdown, and `src/assets.test.tsx` walks all of those and fails if a new way to draw an image
-skips the rule.
-
-One thing it cannot do: it does not know what is behind the mark. A tenant that puts a marked asset
-on an `inverse` band gets the supplied file on that band, drawn plainly. Choosing the band is the
-tenant's, and a white box behind the mark would itself be the boxing the rule forbids.
-
-### Related posts, if the CMS has the AI module
-
-`listRelated` asks `BarakoCMS.AI` for the posts closest to this one and hands them to `PostView`,
-which renders a band of cards with the similarity score on each. `createBlogPost` already does the
-call, so a site using the factory gets it for nothing.
-
-Nothing about it is required. A CMS without the module answers 404, a type that is not publicly
-deliverable answers 404, a module installed but not enabled answers an empty list, and an
-unreachable CMS throws. All four end the same way: an empty array, no band, no heading, no empty
-state. The reader of a site without the module never learns the feature exists.
-
-The post being read is its own closest match, so the fetch asks for more than it renders and drops
-itself. A hit with no slug is dropped too, because there is nothing to link it to.
-
-Turning it on is the CMS's job, not this package's: `dotnet add package BarakoCMS.AI`, point
-`Ai:EmbeddingBaseUrl` at an Ollama instance, set `Ai:Enabled`, and index the type.
+`sites`, identity is data in the CMS and read per request: see
+[One build, many sites](https://github.com/BaryoDev/barakoPress/blob/master/docs/sites.md#one-build-many-sites).
 
 ## The caching design, which is the whole point
 
@@ -1132,195 +277,23 @@ publish  ->  signed webhook  ->  revalidate  ->  next render reads once
 
 Every read in `src/delivery.ts` is tagged with your `cacheTag`. `POST /api/revalidate` drops that tag
 the moment barakoCMS says something changed, so a publish is live in one request and the steady state
-is no database reads.
-
-### What a publish drops
-
-A read carries a second, narrower tag beside the site's own: the entry's when it read one entry, the
-type's when it read a list, a search, the site settings or the page tree. barakoCMS names the content
-type and sends the entry's public data with every delivery, so a publish drops that type's tag and
-that entry's tag, and leaves every other entry of the type cached. Correcting one typo on a school
-with a thousand news posts re-renders that post and the lists it appears in, not the other 999.
-
-A delivery that names no content type, or one this site renders nothing of, drops the site's own tag,
-which is every read it has cached. That is what every delivery did before this, so a workflow posting
-a body of its own keeps working.
-
-A response barakoCMS marks `Cache-Control: no-store` is not cached: the class is remembered against
-that path and every later read of it asks the CMS uncached, carrying no tag. That is how a type that
-has to be fresh to the minute lives beside pages cached for hours.
-
-### Running more than one container
+is no database reads. [Caching and the webhook](https://github.com/BaryoDev/barakoPress/blob/master/docs/caching.md) has the rest: what a publish
+drops, the render cache, running more than one container, and wiring the webhook.
 
-The kept answers, the host to tenant map, the webhook replay guard and the generation of each cache
-tag are in process by default, which is right for one container and wrong for two: a purge reaches
-one of them through the load balancer, and the others keep serving their own copies until the
-backstop runs out.
+## Deploying
 
-Pass a `store` on the config and they share it. It is three methods over anything the deployment
-already runs:
-
-```ts
-import type { PressStore } from "barakopress";
-
-const store: PressStore = {
-    async get(key) { return (await redis.get(key)) ?? null; },
-    async set(key, value, ttlSeconds) { await (ttlSeconds ? redis.set(key, value, { EX: ttlSeconds }) : redis.set(key, value)); },
-    async delete(key) { await redis.del(key); },
-    // Only when the key is absent, atomically. This is what honours a replayed delivery once.
-    async add(key, value, ttlSeconds) { return (await redis.set(key, value, { NX: true, ...(ttlSeconds ? { EX: ttlSeconds } : {}) })) !== null; },
-};
-```
-
-A purge one container receives then reaches the rest: the honoured delivery writes a generation
-against each tag it dropped, and a read carries the newest generation of its own tags in the URL it
-asks the CMS for, so a container that was never told is asking for something it has never cached.
-Next's own data cache stays per container; what crosses is the knowledge that it is out of date.
-
-Each read also carries a backstop, 300 seconds by default. That is not for correctness, it is for the
-deployment where nobody ever created the webhook: without it their blog would be empty forever and
-nothing would say why. With it, a missing webhook degrades publishing from instant to a few minutes.
-
-**The cache invalidation is configuration, not code.** In barakoBrew: a workflow on your post content
-type, trigger `Published`, one Webhook action with the URL and a shared secret. Nothing is deployed
-to change it.
-
-### The render cache
-
-Reads being cached is half of it. The other half is not rendering the page again, and for a
-request-time site that used to be impossible: resolving the tenant meant reading the request host,
-reading a header makes a route dynamic, and Next never keeps a dynamic route. One container serving
-forty domains re-rendered every page for every visitor, with every read under it already cached.
-
-Next keys what it keeps by the path and by nothing else. There is no `Vary` and no second key to
-add. So whatever a render depends on has to be in the path, and three things are:
-
-| In the segment | Why |
-| --- | --- |
-| the tenant | two tenants must never share an entry. This is the whole reason the segment exists |
-| the gate | `public`, or `shared` for a request carrying a valid share session. A holding tenant answers differently for each, so each gets its own entry |
-| the host | the site's origin when the tenant's settings leave `Url` empty. Two hosts on one tenant are two renders, not one |
-
-The proxy writes them, as `/_press/<tenant>~<gate>~<host>/<path>`, and it is the only thing that
-does: a path that arrives under `/_press` from outside is a 404, because otherwise
-`https://one.example/_press/other~public~other.example/` would render another tenant's site on this
-tenant's domain. A host the CMS does not know is a 404 before anything renders, so an invented host
-never makes an entry: only a host a tenant owns can put one there.
-
-**What is cached.** The index, the pages tree, the collection indexes and the archives, per tenant
-and per path. `revalidateTag` drops a tenant's renders along with its reads, so the webhook that was
-already purging one purges both, and a publish on one tenant leaves every other tenant's renders in
-place. The first few views of a path answer `STALE` rather than `HIT` while the reads under them are
-still filling Next's data cache; after that it is `HIT` with no render and no read.
-
-**What is not cached, deliberately.**
-
-| Not cached | Why |
-| --- | --- |
-| a route that reads `?preview=` | a draft must never be in a shared cache, and reading the query is what keeps the route out of it. `createBlogPostPreview` is such a route; `createBlogPost` is not |
-| a page binding `{{query.X}}` | same reason. On a kept route the query is not handed to the blocks at all, so the binding is reported as an unbound scope and renders as nothing. A site that wants it writes `createPage(config, blocks, { query: true })` and leaves `generateStaticParams` out of that file |
-| `createViewerPage` | per viewer by definition. It calls `connection()`, and a route that does cannot be kept |
-| the feed, the sitemap and robots | `sitemap.ts` and `robots.ts` have to sit at the root of the app tree, so neither can carry a tenant segment. They resolve their own tenant and stay dynamic |
-| `/_share` and the redeem route | per visitor |
-
-**Which routes are kept is the consumer's call, in the consumer's file**, the same as `revalidate`.
-A page route that exports `createSiteStaticParams()` is kept; one that does not is rendered per
-request. That is also the switch for the two rows above: a route that reads the query leaves it out.
-
-**Nothing downstream may keep a copy.** Every rewritten answer carries `Cache-Control: private,
-no-store`, which is what a request-time site has always sent. Next's cache is the server's own and is
-not that header, so the render is still kept here. What stays true is that a browser or a proxy
-holding `/` is never holding one visitor's gate for the next visitor.
-
-### One secret
-
-`PRESS_SECRET` keys everything this renderer signs: each tenant's webhook key and each share session
-cookie. Every signature puts its purpose first in what it signs (`revalidate.` or `press-share.`), so
-one made for one purpose never verifies as another. It is read per request and has one rule for every
-purpose: at least 32 characters, for example `openssl rand -base64 48`.
-
-| When `PRESS_SECRET` is | Webhooks | Share sessions |
-| --- | --- | --- |
-| 32 characters or more | verified with it | signed with it |
-| set but shorter | refused with 503 | none issued or accepted |
-| unset | `REVALIDATE_SECRET`, as in 0.3.0 | `PRESS_PREVIEW_SECRET` |
-
-The older names are read only when `PRESS_SECRET` is unset, so a site that set them keeps working, and
-the keys derive byte for byte as before, so a key already pasted into a tenant's workflow keeps
-verifying. A `REVALIDATE_SECRET` shorter than 32 characters still verifies and logs a warning once,
-until 1.0.0. A `PRESS_PREVIEW_SECRET` shorter than 32 characters opens no session, as before.
-
-Moving to the new name is copying the value: `PRESS_SECRET` set to what `REVALIDATE_SECRET` held
-derives the same tenant keys, provided it is 32 characters or more. A shorter one has to be replaced,
-and each tenant given its new key.
-
-### Wiring the webhook
-
-1. Put a random value of at least 32 characters in `PRESS_SECRET` where your app runs.
-2. In barakoBrew, create a workflow on your post content type, event `Published`.
-3. Add a Webhook action with `Url` set to `https://your-site/api/revalidate` and `Secret` set to the
-   same value. On a site with `sites` configured, the `Secret` is the tenant's key instead, below.
-
-### One key per tenant
-
-With `sites` configured, one app serves many tenants, and each tenant's admin can read and edit its
-own workflows. So no tenant is given `PRESS_SECRET`. Each delivery is verified with a key derived
-for the tenant its host resolves to:
-
-```
-key = lowercase hex HMAC-SHA256(PRESS_SECRET, "revalidate." + tenant handle)
-```
-
-A delivery signed with one tenant's key gets a 401 on every other tenant's host, and so does one
-signed with `PRESS_SECRET` itself. Print a tenant's key where `PRESS_SECRET` (or `REVALIDATE_SECRET`) is set:
-
-```bash
-npx barakopress revalidate-key baryo
-# or, with no Node:
-printf 'revalidate.%s' baryo | openssl dgst -sha256 -hmac "${PRESS_SECRET:-$REVALIDATE_SECRET}" | sed 's/^.* //'
-```
-
-Both read the secret from the environment and print only the key. Paste it into the `Secret` of that
-tenant's Webhook action, with `Url` on that tenant's domain. A new tenant needs nothing on the
-renderer. Changing `PRESS_SECRET` changes every tenant's key, so each workflow needs its new one.
-
-A site without `sites` (one build, one site) verifies with `PRESS_SECRET` itself, as it did with
-`REVALIDATE_SECRET`. Its workflow holds that value, so give it a value no other deployment uses.
-
-**Upgrading a multi-tenant site to 0.4.0 is a breaking change.** Every tenant's workflow holds
-`REVALIDATE_SECRET` today, and after the upgrade that value verifies for no tenant: deliveries get a
-401 and purges stop, with the backstop the only refresh. Before or right after deploying, print each
-tenant's key and put it in that tenant's Webhook `Secret`. Then set a new `PRESS_SECRET` and print
-the keys again, because every tenant admin has seen the old value and could derive any tenant's key
-from it.
-
-The barakoCMS webhook body does not name its tenant yet, so the host is what picks the key. Once the
-body carries the tenant (barakoCMS #868), a delivery whose body names a different tenant than its host
-resolves to is to be refused.
-
-**If your site sets `trailingSlash: true`, the webhook URL needs the slash.** Next redirects
-`/api/revalidate` to `/api/revalidate/` with a 308, and barakoCMS does not follow redirects on a
-webhook, deliberately: following one was an SSRF hole, because the guard checked only the first hop.
-So a URL without the slash gets a 308, the delivery is recorded as failed, it retries five times and
-gives up, and the cache is never purged. The site keeps working because of the backstop, so the only
-symptom is that publishing feels slow.
-
-barakoCMS refuses to sign a delivery to an `http://` URL unless `Webhooks:AllowInsecureSignedUrls` is
-on, which is for a loopback receiver in a lab. In production the URL is https, so this is not in your
-way.
-
-Verification follows the recipe in the API's `docs/webhooks.md`: HMAC-SHA256 over
-`"<timestamp>.<raw body>"`, compared in constant time, with a 300 second tolerance so a captured
-delivery cannot be replayed later, and each signature honoured once per tenant. An unsigned, missigned or stale
-delivery gets a 401. If neither `PRESS_SECRET` nor `REVALIDATE_SECRET` is set, or `PRESS_SECRET` is
-shorter than 32 characters, the endpoint answers 503 and purges nothing,
-because an open cache-purge endpoint is a free denial of service.
+The reference app in `app/` is a site that consumes this package by its name, the way yours does. It
+is published as `ghcr.io/baryodev/barako-press` for linux/amd64 and linux/arm64, tagged with each
+release's version and `latest`, and `dev` from master. The compose stack, the site-only compose file,
+the BaryoVM release manifests and building a site's own image with an overlay are in
+[Deploying](https://github.com/BaryoDev/barakoPress/blob/master/docs/deploying.md).
 
 ## What it reads
 
 The `blog` blueprint barakoCMS ships: `post`, `category`, `author`, `page`. Apply it with
 `POST /api/content-types/blueprints/blog`. Field names are PascalCase because that is what the
-blueprint creates, and `src/cms.ts` is the only file in the package that knows any field name.
+blueprint creates. The default names live in `src/config.ts`, the blueprint's field map and
+`REFERENCE_FIELDS`, and a site's config replaces any of them.
 
 Only published entries of a type opted into public delivery appear. Ordering is asked of the API
 rather than applied to the page that came back, because sorting one page of results gives you the
@@ -1359,34 +332,6 @@ should absorb it rather than a reader. Measured against a CMS that logged every
 caused zero reads: `{ expire: 0 }` already makes the next request a blocking miss. It cost three
 requests per delivery and tripled what an attacker got from one captured signature, for nothing.
 
-## The reference deployment in this repository
-
-`app/` is not the product. It is a site that consumes this package by its name, exactly as yours
-does, so the package cannot quietly depend on something only its own repository has. It comes with a
-container, a compose stack with Caddy terminating TLS, and a BaryoVM release manifest.
-
-```bash
-cp .env.example .env      # point CMS_URL at your instance, set PRESS_SECRET
-npm install
-npm run build && npm start
-```
-
-Deploying that stack to a VM:
-
-```bash
-baryovm vm provision blog1                     # or bring your own VM
-baryovm vm bootstrap blog1                     # installs Docker, and only Docker
-baryovm vm harden blog1                        # sshd policy and fail2ban
-baryovm stack add blog --vm blog1 --sudo --release-file ./baryovm.release.json
-baryovm stack release blog
-```
-
-Before the first release, three DNS names have to point at the machine (`SITE_DOMAIN`, `API_DOMAIN`,
-`CONSOLE_DOMAIN`) and a `.env` has to exist on it at `/opt/barakopress/.env`. The release refuses to
-start without that file, and refuses again if `PRESS_SECRET` and `REVALIDATE_SECRET` are both empty, because a stack that
-comes up with no secret can never be told that content changed. Only ports 80 and 443 are published:
-the API, the console and the site are reachable only through Caddy on the compose network.
-
 ## The look check
 
 Before a site's domain moves to this stack, the look check proves the rebuilt pages look like the
@@ -1408,7 +353,7 @@ jobs:
 ```
 
 The pair list format, the per page threshold and the list of things that would otherwise make a run
-flake are in [docs/look-check.md](docs/look-check.md). `npm run look:selftest` runs the check twice
+flake are in [docs/look-check.md](https://github.com/BaryoDev/barakoPress/blob/master/docs/look-check.md). `npm run look:selftest` runs the check twice
 over fixture pages, once green and once against a deliberate colour change, which is how anyone can
 see for themselves that it fails when it should.
 
@@ -1428,11 +373,14 @@ run the package build first. While changing `src/`, leave `npm run watch` going
 `next dev` in another.
 
 Why there is a build step at all, when every consumer is a Next app that could compile TypeScript
-itself: the decision and what it costs are recorded in [CLAUDE.md](CLAUDE.md).
+itself: the decision and what it costs are recorded in [CLAUDE.md](https://github.com/BaryoDev/barakoPress/blob/master/CLAUDE.md).
 
-Releasing is in [RELEASING.md](RELEASING.md). No npm token is stored anywhere.
+Releasing is in [RELEASING.md](https://github.com/BaryoDev/barakoPress/blob/master/RELEASING.md). No npm token is stored anywhere.
 
 ## Status
 
-Early. The blog works end to end against a real instance. Known gaps, all tracked upstream: no media
-picker, no rich editor, and no visitor theme variants.
+0.8.0, on npm as `barakopress` and on ghcr as `ghcr.io/baryodev/barako-press`. It renders
+barakocms.com and press.baryo.dev against real barakoCMS instances. barakocms.com still runs a
+derived image of the engine, with a plugin and a small overlay; #166 to #170 track what it takes to
+run it on the published image as configuration. Other open gaps are in the issues, among them
+visitor-switchable theme variants (#80) and a generated Open Graph image (#81).