@geekity/cms 0.30.0 → 0.32.0

package/themes/default/README.md

@@ -1,2341 +1,38 @@
 # Default theme
 
-Templates ship here, inside the published package, so every site gets them
-without copying anything.
-
-```
-themes/default/
-  theme.json     the manifest: name, kind and description
-  layouts/
-    base.njk     the page every other layout extends
-    home.njk     the post archive, paginated
-    front-page.njk  the page the Reading setting serves at /
-    post.njk     one post
-    page.njk     one page
-    tag.njk      a tag archive, paginated
-    category.njk a category archive, paginated
-    author.njk   one person's archive, paginated
-    search.njk   the search form and what it found, paginated
-    404.njk      nothing at this URL
-    410.njk      what was at this URL was deleted
-    500.njk      the request failed on the server
-    503.njk      the site is in maintenance mode
-    comment.njk  a native comment on a page of its own
-  partials/
-    post-list.njk     the h-feed a listing is made of
-    pagination.njk    previous/next pager
-    tags.njk          macros for tag and category links
-    kicker.njk        the line above an entry naming its kind and date
-    reply-context.njk the citation of what a reply answers
-    event.njk         when and where an event is
-    citations.njk     the citation of what a like, repost or bookmark cites
-    cited-page.njk    the name and author both citations print
-    read.njk          what a read post read, and how far
-    bio.njk           who an entry is by, as an h-card
-    menu.njk          one named menu, as a nav of links
-    feeds.njk         macros for the feed links in <head>
-    conversation.njk  the replies, likes and boosts under a post or an open page
-    comment.njk       one reply and its answers, as the thread and a comment page print it
-    comment-form.njk  the form under a post or page that is taking comments
-    contact-form.njk  the form on a page whose front matter says contact: true
-    archive.njk       every post by month, on a page that says archive: true
-    backlinks.njk     the site's own posts and pages that link to this one
-    search-form.njk   the search box, on the search page
-    head-end.njk      empty: what a site adds to the end of every <head>
-    body-end.njk      empty: what a site adds to the end of every <body>
-  mail/
-    test.*.njk              the Send test email message
-    password-reset.*.njk    the forgot-password link
-    password-changed.*.njk  the notice sent once a password has been set
-    comment-pending.*.njk   the moderation notice
-    comment-digest.*.njk    the hourly or daily digest of what is waiting
-    comment-reply.*.njk     the notice a commenter gets about a reply
-    contact-message.*.njk   a message from a page's contact form
-  src/
-    style.css    the stylesheet's source, compiled with Tailwind
-  static/
-    style.css    the compiled stylesheet, served at /theme/style.css
-    highlight.js the code highlighter
-```
-
-Plain Nunjucks templates and one stylesheet. The stylesheet is written in
-Tailwind v4 (`src/style.css`) and compiled when the package is built, so
-`static/style.css` is a build product: gitignored in this repository, written
-by `pnpm build` (which the root `prepare` runs after an install and before a
-publish), and shipped in the package like every other file here. The compile
-happens once, on the machine that builds the package. A reader gets one plain
-CSS file and no script, web font or CDN request because of it.
-
-The design is Paper (doc-9, decision-22): one warm column, serif throughout,
-sans for small labels, and a kicker above every entry naming its kind.
-
-**Rebuilding the stylesheet.** After editing `src/style.css`:
-
-```
-pnpm --filter @geekity/cms build:theme
-```
-
-Tailwind scans only this theme's `layouts/` and `partials/`, so a utility class
-written in a template here is compiled in and nothing outside the theme is
-read. The templates themselves use the semantic class names below and the look
-lives in `src/style.css`, through `@apply`.
-
-**A site theme owes Tailwind nothing.** Its own `static/style.css` replaces this
-one wholesale, and any CSS that knows the class names in this README will do.
-The demo theme's is plain CSS. A site that only wants different colours
-overrides the `--color-*` custom properties instead; see [Colours](#colours).
-
-## The manifest
-
-`theme.json` is what makes a directory a theme:
-
-```json
-{
-  "name": "Default",
-  "kind": "site",
-  "description": "One line about the theme.",
-  "colorScheme": "light dark",
-  "themeColor": { "light": "#faf7f2", "dark": "#171412" }
-}
-```
-
-`name` is what a person sees, `kind` is `site` — the only kind there is, and
-the field exists so another can be added later without the format changing —
-and `description` is optional. The directory name is the theme's id. A
-directory without a readable manifest, or one naming a kind this CMS does not
-have, is not a theme.
-
-`colorScheme` and `themeColor` are the colours the head declares before the
-stylesheet loads (see [The head](#the-head)). `colorScheme` is one of `normal`,
-`light`, `dark`, `light dark`, `dark light` or `only light`, preferred scheme
-first. `themeColor` is the colour of the browser around the page, one per
-scheme, as a three- or six-digit hex colour with no alpha. Make it the page's
-own background. A value outside those is ignored, and so is one a theme leaves
-out: each falls back to this theme's, just as a template does.
-
-## Overriding a template
-
-A site keeps its themes under one directory, `themes/` by default and
-`themesDir` in the config, with one folder per theme and a `theme.json` in
-each. Which one it wears is one setting, `theme` in `content/_data/site.json`,
-holding the folder's name:
-
-```
-themes/
-  midnight/
-    theme.json
-    layouts/post.njk
-    static/style.css
-```
-
-```json
-{ "theme": "midnight" }
-```
-
-The setting is what **Appearance > Themes** in the admin writes: the screen
-lists this theme and every folder under `themes/`, marks the one in use, and
-Activate on another writes its name — or, on the packaged theme, takes the key
-out again. A change takes effect on the next request, with no restart, and a
-folder whose manifest will not read is listed under "Not themes" with the
-reason rather than quietly left out.
-
-Resolution order for any template is then that theme first, this directory
-second, one file at a time. The theme above replaces the post layout and keeps
-receiving updates to every other template, and `static/style.css` replaces the
-stylesheet the same way — assets under `/theme/` resolve in the same order.
-Link a theme file with the `asset` filter rather than a literal `/theme/`
-path: `{{ "style.css" | asset }}` puts a hash of the file in the URL, so a
-reader's browser keeps it for a year and still fetches the new one the moment
-it changes. The plain `/theme/style.css` keeps working, cached for an hour. A
-site that has chosen no theme reads this one and nothing else, and a theme
-sitting in `themes/` that the setting does not name is never on the path at
-all. A `theme` naming a folder that is not there, or is not a theme, falls back
-to this one with a warning in the log rather than a broken site.
-
-The admin is not a theme and has no setting. Its templates live in their own
-tree with a loader of their own, off this search path entirely, so no theme can
-shadow the login form or the CSRF field inside it.
-
-An override is a normal Nunjucks template, so it can extend or include the
-packaged ones by name:
-
-```njk
-{% extends "layouts/base.njk" %}
-
-{% block content %}
-<article>
-  <h1>{{ title }}</h1>
-  {{ content | safe }}
-</article>
-{% endblock %}
-```
-
-`layouts/base.njk` defines the blocks `title`, `speculationRules`,
-`viewTransitions`, `head`, `alternates`, `header`, `breadcrumbs`, `content`,
-`footer` and `scripts`, so most sites never have to copy it.
-
-Two layouts are named for the pages the Reading settings pick:
-
-| Template                 | Rendered for                  | Shipped here | Falls back to      |
-| ------------------------ | ----------------------------- | ------------ | ------------------ |
-| `layouts/front-page.njk` | the page served at `/`        | yes          | `layouts/page.njk` |
-| `layouts/posts-page.njk` | the listing on the posts page | no           | `layouts/home.njk` |
-
-`layouts/front-page.njk` is a layout here rather than only an override point:
-see [The front page](#the-front-page) for what it draws. Overriding it is how a
-front page is laid out differently from every other page without overriding the
-layout they all use, and the fallback above is reached only by a theme that
-replaced it with nothing.
-
-There is no posts page layout: a site that sets one gets the listing layout
-until it writes one. On the posts page the page's own front matter and rendered
-body are on the context beside the listing, so `{{ content | safe }}` prints its
-words above the posts; `layouts/home.njk` already does.
-
-## Adding to every page
-
-Analytics, a site verification tag or a chat widget goes on every page, and
-none of them needs a layout copied. `layouts/base.njk` includes two partials
-that this theme ships empty:
-
-| Partial                 | Printed                                            |
-| ----------------------- | -------------------------------------------------- |
-| `partials/head-end.njk` | last in `<head>`, after the cards and the JSON-LD  |
-| `partials/body-end.njk` | last in `<body>`, after the footer and the scripts |
-
-A site theme that holds one of them, and nothing else but its `theme.json`,
-adds that markup to every public HTML page: posts, pages, listings, search, the
-front page, and the 404, 410, 500 and 503 pages. Every other template still
-comes from this directory, so the site keeps receiving updates to them, and
-the two partial names stay as they are. The includes sit outside every block,
-so a layout that overrides `head` or `scripts` without `super()` keeps them.
-
-They are part of the HTML page and nothing else. The Markdown, plain text and
-JSON representations of a page, the feeds, `llms.txt`, mail and the admin do
-not print them. The editor's preview renders the post or page layout in the
-admin, so the context there carries `editorPreview: true` and `layouts/base.njk`
-leaves both partials out. A theme that replaces `layouts/base.njk` and includes
-them itself should test the same key.
-
-Umami and Google Analytics 4, in `themes/analytics/`:
-
-```
-themes/analytics/
-  theme.json
-  partials/head-end.njk
-```
-
-```json
-{ "name": "Analytics", "kind": "site" }
-```
-
-```njk
-<script defer src="https://cloud.umami.is/script.js" data-website-id="your-website-id"></script>
-<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
-<script>
-  window.dataLayer = window.dataLayer || [];
-  function gtag(){dataLayer.push(arguments);}
-  gtag('js', new Date());
-  gtag('config', 'G-XXXXXXXXXX');
-</script>
-```
-
-Then wear the theme, either with Activate on **Appearance > Themes** or with
-`"theme": "analytics"` in `content/_data/site.json`. A site that already wears
-a theme of its own puts the partial in that theme instead.
-
-The partial is a template, rendered with the page's context, so it can read a
-value out of `site.json`, as in `data-website-id="{{ site.umamiId }}"`.
-
-**In Docker.** The image reads themes from `/site/themes`. Mount the site's
-`themes/` directory there, read-only, which is the commented line in
-`deploy/compose.yaml`:
-
-```yaml
-volumes:
-  - ./themes:/site/themes:ro
-```
-
-No custom image is needed. A change to the partial shows on the next request.
-
-**Under a Content-Security-Policy.** The default headers set only
-`frame-ancestors`, so they restrict nothing a page loads, and the inline gtag
-configuration runs as it is. A site that sets a policy of its own with
-`securityHeaders` must allow what the snippets load and where they send data:
-
-| Directive     | Umami                      | Google Analytics 4                                                                             |
-| ------------- | -------------------------- | ---------------------------------------------------------------------------------------------- |
-| `script-src`  | `https://cloud.umami.is`   | `https://*.googletagmanager.com`, and the inline configuration (see below)                     |
-| `connect-src` | `https://gateway.umami.is` | `https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com` |
-| `img-src`     | none                       | `https://*.google-analytics.com https://*.googletagmanager.com`                                |
-
-The inline `<script>` that configures gtag needs one of these:
-
-- Move it to a file in the theme, `themes/analytics/static/gtag.js`, and load
-  it with `<script src="{{ "gtag.js" | asset }}"></script>`. It is then served
-  from the site, and `script-src 'self'` covers it.
-- Allow its hash, `'sha256-…'`, in `script-src`. The hash covers every byte
-  between the tags, so it changes when the measurement ID or the whitespace
-  changes.
-- Allow `'unsafe-inline'` in `script-src`. This also allows any injected
-  inline script, so prefer one of the other two.
-
-## The page shell
-
-`layouts/base.njk` is the page shell: the skip link, one `.global-wrapper` at the
-42rem measure, `.global-header`, `<main id="main">` and the footer, in that
-order. The shape is the andrewshell.org design's (decision-16) and the look is
-Paper's (doc-9).
-
-**One home for each kind of link.** The header carries the site menu, on every
-page. [The bio](#the-bio) carries the person whose page or post it is. The
-footer carries the site's own links. The search box is on the search page and
-nowhere else.
-
-**The header has one rule, and the menu under it.** On the front page it is the
-site title as `h1.main-heading`, linked home, with `site.tagline` in a
-`p.site-tagline` under it; on every other page it is `a.header-link-home`, the site
-title small and linked home, and no tagline. The wrapper carries
-`data-is-root-path="true"` at `/` and nothing anywhere else, which is how the
-stylesheet tells the two apart. `menus.primary` is printed inside the
-`.global-header` on both: at the root it is a line of its own under the
-tagline, and everywhere else the stylesheet lays the header out as one line so
-it sits beside the link home. See [Navigation](#navigation).
-
-**The footer** prints the copyright with the current year and the site
-author's display name, `soloAuthor.name`, or the site title on a site with
-several authors,
-then the page's license, when it has one, as `<a rel="license">` with its name,
-then `Published with Geekity`, and then `menus.footer` — the `footer` area this
-theme declares, and the whole of what the footer links. A site that wants its
-feed there types an `RSS | /feed/` line into it, the way the starter site does.
-Nothing in the footer is read off an account: it used to hold one `rel="me"`
-link per entry of `siteAuthor.links`, which was one nominated user's profile
-presented as the site's. An empty or missing footer menu prints no list at all,
-and the copyright line stands on its own. The year is
-`{{ "now" | date("year") }}` — `now` is the one word the `date` filter reads
-rather than parses — so it is the year at the moment the page is rendered, in
-the site's own timezone. The license is `license`: a post's own from its
-`license` front matter, else the site's from Settings > General, and nothing
-on a site with none.
-
-**The breadcrumb** opens `<main>` on a page with a place in the site's
-hierarchy (TASK-150): a post filed under a category, and a category, tag or
-author archive. It is `nav.breadcrumbs` labelled `Breadcrumb`, holding an `ol`
-whose items run Home, then the post's first category and the post, or the
-archive's term or person, then `Page N` past page one. Every crumb but the last
-is a link; the last is the page itself, a `span` with `aria-current="page"`.
-The trail is `breadcrumbs`, a list of `{ name, url }` that `layouts/base.njk`
-sets before anything is printed, and the JSON-LD prints the same list, so the
-two cannot disagree. Every other page has an empty trail and prints nothing. A
-site that wants no visible breadcrumb empties the `breadcrumbs` block, and the
-`BreadcrumbList` stays in the graph.
-
-Webrings, badges and anything else that is markup rather than a link are
-deliberately not in the package. They go in a site theme's `footer`
-block:
-
-```njk
-{% extends "layouts/base.njk" %}
-
-{% block footer %}
-{{ super() }}
-<p class="webring">
-  <a href="https://example.ring/previous">&larr;</a>
-  An <a href="https://example.ring">example webring</a>
-  <a href="https://example.ring/next">&rarr;</a>
-</p>
-{% endblock %}
-```
-
-### The admin bar
-
-When somebody signed in to the admin reads the site, the CMS puts the admin bar
-across the top of every HTML page: the site title linking to the dashboard,
-**+ New**, **Edit Post** or **Edit Page** on a post or a page, and the account
-menu. A theme draws none of it and needs no template for it. The CMS inserts a
-`<geekity-admin-bar>` element straight after the page's `<body>` tag, and an
-anonymous reader's page is unchanged, byte for byte.
-
-The bar keeps its markup and its stylesheet in a shadow root, so a theme's CSS
-cannot restyle it and its CSS cannot restyle the theme. The element carries an
-inline style that resets it and fixes it to the top of the window, full width,
-above the page. Padding or margins on `<body>`, and rules such as `body > *` or
-a grid on `<body>`, do not move or resize it. It stays in place while the page
-scrolls.
-
-The bar takes no room by itself, so the CMS makes room for it from outside. On
-a page that carries the bar:
-
-- `<html>` has the class `geekity-admin-bar`.
-- A stylesheet in `<head>` declares `--geekity-admin-bar-height` on `:root`
-  and sets `margin-top: var(--geekity-admin-bar-height) !important` on
-  `<html>`, which pushes the whole page down below the bar. The height is
-  40px, or 80px on a screen 600px wide or less, where the bar can wrap onto a
-  second line. A script in the bar then measures it and sets the real height
-  on `<html>`, so the push matches the bar at any width, and is 0 when a theme
-  hides the bar.
-- The same stylesheet sets `scroll-padding-top` on `<html>` to the bar's
-  height, so a link to an anchor on the page, such as a skip link or a
-  footnote, scrolls its target to below the bar. It is declared with no
-  specificity, so a theme that sets its own `scroll-padding-top` keeps it.
-
-A theme with a sticky or fixed header of its own offsets it by the bar's
-height. The fallback of `0` applies on every page the bar is not on:
-
-```css
-.site-header {
-  position: sticky;
-  top: var(--geekity-admin-bar-height, 0);
-}
-```
-
-A theme that sets its own `scroll-padding-top` adds the bar to it the same
-way, for example `calc(var(--geekity-admin-bar-height, 0px) + 4rem)`. Use the
-`geekity-admin-bar` class for any other change, for example
-`.geekity-admin-bar .site-header { ... }`.
-
-A theme that must not show the bar can hide it:
-
-```css
-geekity-admin-bar {
-  display: none !important;
-}
-```
-
-The `!important` is needed because it has to beat the element's inline style.
-With script on, the bar then measures 0 and the page moves back up. For a
-reader without script, the theme also removes the margin:
-
-```css
-html.geekity-admin-bar {
-  margin-top: 0 !important;
-}
-```
-
-### An entry
-
-`layouts/post.njk` and `layouts/page.njk` draw the same thing, the entry, and it
-is a microformats2 `h-entry`. An article, and a page:
-
-```html
-<article class="blog-post h-entry">
-  <header class="post-header">
-    <p class="kicker">
-      <span class="kicker-kind">Article</span>
-      <span class="kicker-dot" aria-hidden="true">·</span>
-      <a href="/category/notes/" class="p-category" rel="category">notes</a>
-    </p>
-    <h1 class="p-name">Hello</h1>
-    <p class="post-deck p-summary">The description the author wrote.</p>
-  </header>
-  <section class="e-content">
-    <p>The rendered body.</p>
-    <p class="entry-meta">
-      <a class="u-syndication small" href="https://news.indieweb.org/en"
-        >IndieNews</a
-      >
-      <a href="/2026/09/hello/" class="u-url"
-        ><time class="small dt-published" datetime="2026-09-02T09:00:00.000Z"
-          >Published 2 September 2026</time
-        ></a
-      >
-      <span aria-hidden="true">·</span>
-      <time class="small dt-updated" datetime="2026-09-05T09:00:00.000Z"
-        >Updated 5 September 2026</time
-      >
-      <span aria-hidden="true">·</span>
-      <span class="small"
-        >Also on
-        <a class="u-syndication" href="https://news.indieweb.org/en/…"
-          >news.indieweb.org</a
-        ></span
-      >
-    </p>
-  </section>
-  <p class="post-categories">…tags…</p>
-  <hr />
-  <footer>…the bio…</footer>
-</article>
-<nav class="blog-post-nav" aria-label="Neighbouring posts">…</nav>
-```
-
-**The kicker names the kind.** `p.kicker`, from `partials/kicker.njk`, opens
-every entry: the kind word in `span.kicker-kind` (Article, Note or Reply for a
-post, from its `postType`; Page for a page), then the categories it is filed
-under as `p-category` links. It is the only place the kind is said, small and
-once, and an article is additionally the only kind with a visible headline.
-The deck is the front matter's `description` as a `p.post-deck.p-summary`,
-printed only when the author wrote one.
-
-**The Published line is inside the `e-content`**, which is the one thing about
-this shape worth knowing. It is what the source theme does: the date and the
-permalink are part of the words, so a reader, or a fediverse peer reading the
-`e-content`, takes them with the post. The permalink wraps the `dt-published`
-time as a `u-url`, and a `dt-updated` follows it after a middle dot only when
-the update happened on a different day in the site's own timezone; a typo fixed
-an hour later is not news. The line opens with a `u-syndication` link to each
-syndication target the post selects (`syndicateTo`, TASK-155), which is what
-IndieNews and Bridgy Publish look for on the page, and ends with the post's
-copies elsewhere (`syndication`) after **Also on**. A page never prints either,
-and its line is a `p.page-meta` rather than a `p.entry-meta`.
-
-**A post first published elsewhere says so.** A post whose front matter names
-its original with `canonical_href`, an absolute http or https URL such as a
-Substack essay's, has it on the context as `original` (TASK-293). The line
-then reads **Originally published at** and links the original as a second
-`u-url` of the h-entry, after the permalink's. The link says the publication's
-name when the front matter gives one in `canonical_name`, such as `Smarter
-Engineers` for a guest post on someone else's Substack (TASK-316), and the
-original's host otherwise. It is no
-`u-syndication`, because the original is not a copy of this post, and
-original-post-discovery reads a copy's off-site `u-url` as its original. The
-same URL is the page's `rel="canonical"` and its `og:url`, so search engines
-credit the original. A value that is not an absolute http or https URL is
-ignored, and `geekity sync` names the file. So is a `canonical_name` with no
-valid `canonical_href` beside it.
-
-**Every post's page has one `h1`.** A post with a name of its own is headed by
-it, as above. So is a post with a title and no words, such as a titled like,
-repost or bookmark (TASK-256): its header comes first and its citation after
-it. A title that only repeats a post's opening words is no name. A note, or a
-reply without a title, opens on its words instead,
-set larger, so it has no `header`; in its place is an `h1` a screen reader and
-a crawler navigate by and a sighted reader never sees, saying what the post is,
-who wrote it and when, and then the kicker:
-
-```html
-<h1 class="screen-reader-text">Note by Ada Lovelace, 11 September 2026</h1>
-<p class="kicker"><span class="kicker-kind">Note</span></p>
-```
-
-It says `Reply`, `Like`, `Repost` or `Bookmark` for those and leaves out the name or the date the post does
-not have. It is not a `p-name`: a parser that found one would take the post
-for an article. The headings under it step down one level at a time: the
-conversation and the comment form are `h2`, and a refused form's error summary
-is an `h3` inside the form's section.
-
-**A reply cites what it answers** with `partials/reply-context.njk`, a
-`div.reply-context.cite.u-in-reply-to.h-cite`: a rule on the start side, a
-`p.cite-line` saying "In reply to" and the target's name, author and date as
-far as they are known, and its excerpt as a `blockquote.cite-quote.p-content`.
-Where it goes depends on whether the post shows a title. An untitled reply
-opens on it, under the kicker and before its words. A titled reply prints its
-`header.post-header` first and the citation after it, before the `e-content`,
-so the page opens on its title rather than on a link. A listing follows the
-same rule: an untitled entry cites under its kicker, a titled one after its
-title and summary. The same partial cites a reply in a feed. The layouts own
-the placement; the partial owns only what the citation says, and it stays
-inside the `h-entry` wherever it is printed.
-
-**A reply to a silo copy cites the original** (TASK-197). When the post a
-reply answers is a copy of a post on another site, and that post lists the
-copy as its `u-syndication`, `replyContext.original` is the original's URL and
-the rest of `replyContext` describes the original. The `h-cite` links the
-original, and a `p.cite-copy` after it says "Also in reply to its copy on" the
-silo's host, linking the copy as a `u-in-reply-to` of its own, so a parser
-reads both as what the post answers.
-
-**An RSVP says whether its author is going** (TASK-198). An RSVP is a reply
-to an event whose `rsvp` is `yes`, `no`, `maybe` or `interested`.
-`partials/rsvp.njk` opens its `e-content` with a `p.rsvp-line` holding a
-`data.p-rsvp` whose value is the answer and whose text is Going, Not going,
-Maybe or Interested; it prints `rsvp.line`, the HTML the feeds also carry. Its
-reply context says "RSVP to" rather than "In reply to", and when the event's
-page is an `h-event`, or describes a schema.org `Event` in JSON-LD, its start
-follows the event's name as a `time.dt-start` and its place as a
-`span.p-location`, inside the `h-cite`. A start the event page wrote with no
-zone is that wall clock where the event is, so it is printed in UTC
-(`replyContext.startZone`) rather than moved into the site's zone. Its kicker
-and its hidden `h1` say RSVP. An RSVP to a silo copy of an event cites the
-original as a reply does.
-
-**An event is an h-event** (TASK-200, decision-32). A post whose front matter
-has a readable `start` is an event: its title is the event's name, its body
-the description, and `end` and `location` are optional. `layouts/post.njk`
-types its article `h-event` rather than `h-entry`, its kicker and hidden `h1`
-say Event, and `partials/event.njk` follows the title with a
-`dl.event-details`. The When row is a `time.dt-start` and, with an end, a
-`time.dt-end`, each written with the `date` filter's `datetime` format in the
-site's zone, with the instant as its `datetime`. The Where row is a
-`span.p-location` holding the place's words, or "Online at" an
-`a.p-location` that links the address to join an online event. The JSON-LD
-describes the post as a schema.org `Event` instead of a `BlogPosting`. That
-`Event` is a `Place` or a `VirtualLocation`, carries an attendance mode and an
-`EventScheduled` status, and names the author's Person as its `organizer`.
-The answers it is given are grouped in `conversation.rsvps`; see [The
-conversation](#the-conversation).
-
-**A like, a repost or a bookmark cites what it cites** (TASK-169) with
-`partials/citations.njk`, beside the reply context and drawn the same way: one
-`div.reply-context.cite.h-cite` per entry of `citations`, classed
-`u-repost-of`, `u-like-of` or `u-bookmark-of`, whose `p.cite-line` says
-Reposted, Liked or Bookmarked and links the target as its `u-url`. The link
-says the target's name, as the reply context does, with its author after it as
-a `p-author h-card`, when the target was read when the post was saved
-(TASK-244): its `h-entry` name, its oEmbed title, or its `og:title` or
-`<title>`. A YouTube, TikTok, Reddit or Giphy target is named by that
-provider's known oEmbed endpoint, asked before its page, which is read only
-when the endpoint names nothing (TASK-251, TASK-253). Any other target's oEmbed
-title comes from the endpoint its page links. A title that is only a site suffix such as "- YouTube" is
-no title. A comment on this site (`replyContext.comment`, TASK-326) says "a
-comment". With only an author it says "a post", and with neither "a page on"
-the target's host, never the bare URL, which can run to hundreds of
-characters: "Bookmarked a page on example.com" (TASK-255). Its kicker
-and its hidden `h1` say Repost, Like or Bookmark. It is placed as the reply
-context is: at the top of an untitled post, after the header of a titled one.
-A listing cites each entry's from the same partial, by the same rule.
-
-**Both citations name the cited page** through `partials/cited-page.njk`, so
-they print its name and author by one rule. A name that already ends in " by "
-and the author's name, in any case, does not print the author again
-(TASK-247): SoundCloud titles a track "Flickermood by Forss" and names Forss
-as its author. The title link stops before " by ", and the words after it
-become the `p-author h-card`, so the line reads "Liked Flickermood by Forss"
-and a parser still reads the whole title as the `p-name`. A name that mentions
-its author anywhere else, such as "Rick Astley - Never Gonna Give You Up" by
-Rick Astley, keeps the author after it. A page that names no author but names
-its site, its `og:site_name`, is followed by a middle dot and the site as a
-plain `span.cite-site`, never an `h-card`, because a site is not an author: a
-bookmark of a Scripting News post reads "Bookmarked RSS tip #2 · Scripting
-News". A like's, a repost's or a bookmark's citation never prints the page's
-description, which on many sites describes the site rather than the post.
-
-**A citation shows who wrote the cited page** (TASK-199) as fully as the page
-said. The author's photo, an `img.u-photo.cite-avatar` with empty alt text
-since their name is beside it, comes before the name inside the `h-card`; a
-fediverse author's handle follows the name as a `span.p-nickname.cite-handle`
-reading `@user@host`. The photo is the `u-photo` of the `h-entry` author's
-`h-card` (or of the page's `h-card` for the same person), the avatar of the
-account an ActivityPub object is attributed to, or the author image in the
-page's JSON-LD, copied into the site's uploads as a picture is, and left out
-when the post has removed its preview. A Mastodon status is read from the
-ActivityPub object its page links, so its author's display name, handle,
-avatar, words, first image and date come from the status itself rather than
-from the page's `og:title`. A page with no `h-entry` and no object is read
-from its JSON-LD (`headline`, `author`, `datePublished`, `image`) and then its
-Open Graph, Twitter and `article:` tags.
-
-**A citation shows the cited page's picture** (TASK-252) when the page named
-one and the post has not removed its preview. The picture is the page's
-oEmbed photo, else its oEmbed thumbnail, else its `og:image`, else its
-`twitter:image`, copied into the site's uploads when the post was saved, so
-a reader's browser never asks the cited site or its CDN for anything. It is
-`context.picture`: `{ src, width, height, kind, video, shownInFull, imgHtml }`, where
-`imgHtml` is an `img.u-photo` inside the `h-cite`, responsive when the copy has
-variants. A repost of a photo (`shownInFull`, such as a Giphy GIF) prints it in full
-under the line, as `a.cite-photo` linking to the target, with the target's
-name as its alt text. Every other citation with a picture (a like, a bookmark,
-a reply, a repost of a video or a page) is classed `cite-with-thumb` and
-prints it as `a.cite-thumb` beside the line: a 6rem thumbnail linking to the
-target, out of the tab order and hidden from assistive technology because the
-title beside it is the same link, with an empty alt text. A video's thumbnail
-is also classed `cite-video`, which the stylesheet draws a play mark on. A
-picture that could not be copied, was bigger than the site's upload limit or
-was never named leaves the citation as it was, with no picture. A post whose
-front matter says `preview: false`, which the editor's remove control writes,
-prints the plain citation, and so do its listing entry and its feed items.
-There is never an iframe or a script from the cited page.
-
-**A cited URL that is itself an image** (TASK-255), one that answers with an
-`image/*` type rather than a page, is copied as its own picture of kind
-`photo` and has no name, so `context.image` is true and the line says "an
-image from" its host as the link: "Reposted an image from edu.casio.com". A
-repost shows it in full like a reposted GIF, a like or a bookmark as a
-thumbnail beside "Liked an image from edu.casio.com", and a post that hid its
-preview still says it reposted an image. Its alt text is the post's
-`cited-alt`, which the editor's card writes, else the post's title, else
-empty. An image that could not be copied, or was bigger than the site's
-upload limit, keeps no context, so its citation says "a page on" its host.
-
-The feeds open each
-citing post's HTML with the same citation as a `p.cite-line`, the picture
-after it with an absolute `src`.
-
-**A read says what was read** (TASK-229) with `partials/read.njk`, a
-`p.read-line` at the top of the `e-content` that reads like indiebookclub's
-own: a `data.p-read-status` whose value is `to-read`, `reading` or `finished`
-and whose text is Want to read, Currently reading or Finished reading, then a
-`span.p-read-of.h-cite` with the title as a `cite.p-name` (linked as its
-`u-url` when the post gives one), the author as a `p-author`, and the
-identifier as a `data.p-uid` whose value is the `isbn:` or `doi:` uid. Its
-kicker and its hidden `h1` say Read. A listing prints each entry's from the
-same partial. The partial prints `read.line`, the same HTML the feeds and the
-federated Note open with (TASK-233); `read.status`, `read.statusLabel` and
-`read.of` are there for a theme that marks it up differently.
-
-The tags are printed under the words and inside the article, so that each link
-is a `p-category` of this entry, as one `p.post-categories` from
-`partials/tags.njk`. The stylesheet draws the `#` in front of each, so the
-category a parser reads is the tag and not the hash.
-
-**A post with a recording plays it** (TASK-213), from
-`partials/recording.njk`, between the header and the `e-content`. The main file
-is the browser's own player, `<audio controls>` or `<video controls>` as
-`enclosure.player` says, with `preload="metadata"` so a reader who never presses
-play downloads nothing, and a download link inside it for a browser that plays
-neither. The `<source>` carries `u-audio` or `u-video`, so a microformats parser
-finds the file on the entry. A video whose transcript is WebVTT also gets it as
-a `<track kind="captions">`. Under the player a `figcaption` links the
-transcript, as Captions for VTT or SRT and Transcript otherwise, and lists the
-other versions by their title, else their media type. A post without a
-recording, or whose front matter is missing what a player needs, prints none of
-it.
-
-**A post with photos shows them** (TASK-166), from `partials/photos.njk`, after
-the recording and before the `e-content`, each in a `figure.post-photo`. Each is
-the context's `photo.html`: an `<img class="u-photo">` with its alt text, so a
-microformats parser finds every photo on the entry, and a `<picture>` with the
-upload's resizes when it has them. The alt text is the post's own, else the
-media library's. A listing prints them the same way above each entry, and the
-JSON-LD `BlogPosting` lists each as an `ImageObject` with its absolute `url`
-and its alt text as `caption`. The first photo is the post's share image when
-its front matter names no `image`.
-
-```html
-<figure class="post-recording">
-  <audio controls preload="metadata" aria-label="Recording of Episode twelve">
-    <source
-      class="u-audio"
-      src="/uploads/2026/10/episode-12.mp3"
-      type="audio/mpeg"
-    />
-    <a href="/uploads/2026/10/episode-12.mp3">Download the recording</a>
-  </audio>
-  <figcaption class="post-recording-links">
-    <p><a href="/uploads/2026/10/episode-12.vtt">Captions</a></p>
-    <p id="post-recording-versions">Other versions</p>
-    <ul aria-labelledby="post-recording-versions">
-      <li>
-        <a href="/uploads/2026/10/episode-12.mp4" type="video/mp4">Video</a>
-      </li>
-    </ul>
-  </figcaption>
-</figure>
-```
-
-After the entry a post prints its backlinks, then `nav.blog-post-nav`: the
-`previous` and `next` posts as two cards, `rel="prev"` and `rel="next"`, each
-opening on a `span.blog-post-nav-label`, and nothing at all at the ends of the
-archive; then the conversation and the comment form. A page prints its
-backlinks too, then the conversation and the comment form when it takes
-comments, and the contact form when its front matter asked for one. A page has
-no neighbours, no tags and no syndication links, because none of those are
-things a page has.
-
-### Backlinks
-
-A link from one of the site's posts or pages to another sends no webmention.
-The CMS records it instead, and the linked document's context carries
-`backlinks`: the listed posts and pages whose body links to it, newest first,
-each as `{ title, url, date }`. `title` is the linking document's title, or a
-note's first words. `date` is absent for a page that has none. A link counts
-whether it is absolute or relative, with or without its trailing slash, a query
-or a fragment, and through a `redirect_from` of the target. A link to `/`
-counts for the page the Reading setting makes the homepage. A link to a URL the
-site answers with a redirect counts for the document the redirect leads to,
-whether the redirect is a `redirect_from` or an entry in `_data/redirects.json`
-or `_data/redirects/*.json`, `/?p=123` included. A link with a query names the
-query's redirect only when the query matches the redirect's source exactly, as
-a request does, so `/?p=123&ref=feed` is a link to `/`. A document that links
-to itself is not its own backlink. Drafts, future-dated, unlisted,
-private and trashed documents never appear. `backlinks` is always a list, and
-it is empty when nothing links to the document.
-
-`partials/backlinks.njk` prints a `section.backlinks` under the entry, apart
-from the conversation: an `h2` that says "Linked from", then an `ol` of links,
-each with its date in a `<time>`. It prints nothing for an empty list, so
-`layouts/post.njk` and `layouts/page.njk` include it with no condition. The
-front page has `backlinks` on its context too, but `layouts/front-page.njk`
-does not print them, because most of a site links home. A site theme that wants
-them there adds the same include to its own `layouts/front-page.njk`:
-
-```njk
-{% include "partials/backlinks.njk" %}
-```
-
-A site theme moves the list by including the partial somewhere else in its own
-layout, and leaves it out by overriding a layout without the include. To change
-the markup, add a `partials/backlinks.njk` to the site theme. That file replaces
-this one, as any other template is replaced.
-
-### The bio
-
-`partials/bio.njk` is who the page is by: the `p-author h-card` the rule and
-the footer at the end of an entry hold, and the heading of an author archive.
-It replaces `partials/byline.njk`, which is gone — a byline was a name in a
-meta line, and this is the whole credit.
-
-```njk
-{% set bioAuthor = author or siteAuthor %}
-{% include "partials/bio.njk" %}
-```
-
-`bioAuthor` is the one thing to set, and nothing renders when it is absent.
-It is one of the profile objects the context already carries: `author` on a
-post, falling back to `siteAuthor`; `siteAuthor` on a page; the archive's
-person on an author archive.
-
-What the bio prints: a round `u-photo` at 50px when they have an avatar,
-"Written by" and their name as a `p-name u-url` linked `rel="author me"` to
-their archive, then `p-job-title` and `p-locality` when the profile says, then
-their `p-note` and their `rel="me"` links as a `ul.hlist.bio-links` — each
-link's `rel` is on it ready to print, `me` first and then whatever else the
-Links box typed. Set `bioRelMe` to `false` to keep the card and drop its
-claims: the name is linked `rel="author"` alone and `me` comes off every
-link.
-
-**The homepage** speaks for the site's author only on a site whose Site author
-setting names a user, which `soloAuthor` on the context says. Then
-`layouts/base.njk` puts that person's `rel="me"` claims in the head of `/` as
-`<link rel="me">` elements, one for their author archive and one for each
-profile link, whichever layout draws the page (decision-45). Their author
-archive's link home carries `rel="me"` back, so the homepage and the archive
-name each other. `layouts/home.njk` at `/` also ends with that person's card,
-with the same claims, and sets `bioHome` to the homepage's absolute URL, which
-puts a `data.u-url.u-uid` holding it first in the card, so a parser running the
-[representative h-card algorithm](https://microformats.org/wiki/representative-h-card-parsing)
-on the homepage finds this card as the site's (TASK-193). The archive stays a
-second `u-url`. No other page sets `bioHome`. A static front page prints no
-card: see [The front page](#the-front-page) for how a site puts one back. On a
-site with several authors neither homepage prints a card or makes a claim. Each of
-those is printed only when the profile says it, so a profile holding a name
-alone prints a name alone. A name this site has no account for is printed
-unlinked, because the file still said somebody wrote this.
-
-**The person and only the person.** The site menu used to be printed here as
-well, because the design had no header navigation; it is in the header on
-every page now — see [Navigation](#navigation) — so the bio says nothing about
-the site. The note and the links used to be behind a `bioProfile` switch that
-an author archive set and an entry did not, on the grounds that the page
-footer already carried the site's identity links. It carries nobody's, so the
-switch is gone and the card is the same wherever it appears: at the top of
-somebody's archive, and under each of their posts.
-
-`bioLead` is what the line opens with, `Written by` unless a layout sets
-another; `layouts/author.njk` sets `Posts by`, because the card there heads
-somebody's writing rather than crediting one piece of it.
-
-**A site that used `partials/byline.njk`** — `{{ byline.line(author) }}` from
-an overridden layout — either includes this partial instead or writes the line
-itself. It was four lines of markup, and the object behind it has not changed:
-
-```njk
-{% set writer = author or { name: site.title } %}
-<span class="p-author h-card">
-  {%- if writer.url %}<a class="u-url" href="{{ writer.url | url }}">{{ writer.name }}</a>
-  {%- else %}{{ writer.name }}{% endif %}
-</span>
-```
-
-`apps/demo/themes/demo/layouts/post.njk` is that, worked: the demo wants a
-byline under the title rather than a bio in the footer, so it writes one.
-
-### A listing
-
-`partials/post-list.njk` is the feed every listing is made of (the home page,
-the posts page, a tag, category or author archive, and a front page that
-lists `newestPosts`) and it is a microformats2 `h-feed` of `h-entry` items, each opening on
-its kicker:
-
-```html
-<div class="feed h-feed">
-  <article class="feed-item h-entry">
-    <p class="kicker">
-      <span class="kicker-kind">Article</span>
-      <span class="kicker-dot" aria-hidden="true">·</span>
-      <time class="feed-date dt-published" datetime="…">2 September 2026</time>
-      <span class="kicker-dot" aria-hidden="true">·</span>
-      <a href="/category/notes/" class="p-category" rel="category">notes</a>
-    </p>
-    <h2 class="feed-title p-name">
-      <a href="/2026/09/hello/" class="u-url">Hello</a>
-    </h2>
-    <div class="feed-excerpt p-summary">
-      <p>What the post is about, in about 280 characters...</p>
-    </div>
-    <p class="feed-more">
-      <a href="/2026/09/hello/" aria-label="Continue reading: Hello">
-        Continue reading<span aria-hidden="true"> &rarr;</span>
-      </a>
-    </p>
-  </article>
-  <hr class="feed-separator" />
-  <article class="feed-item h-entry">
-    <p class="kicker">
-      <span class="kicker-kind">Note</span>
-      <span class="kicker-dot" aria-hidden="true">·</span>
-      <a href="/2026/09/coffee/" class="u-url"
-        ><time class="feed-date dt-published" datetime="…"
-          >3 September 2026</time
-        ></a
-      >
-    </p>
-    <div class="feed-excerpt e-content"><p>The whole note.</p></div>
-  </article>
-</div>
-```
-
-**Only an article has a headline.** A note, which has no title, is printed
-whole as its `e-content`, and the date in its kicker is its `u-url`. A reply is
-a note that first cites what it answers with `partials/reply-context.njk`, and
-a reply with a title is an article that cites it after its title and summary.
-A like, a repost and a bookmark place `partials/citations.njk` the same way,
-and one with a title and no words is listed by its title too. An article's categories are in
-its kicker; a note's are on its own page.
-
-The excerpt is the entry's `summary`, the very line the feeds publish, so a
-reader and a feed cannot be told two different things, through Nunjucks'
-`truncate(280)`, which cuts at the last space before 280 characters and adds an
-ellipsis. A `description` shorter than that is printed whole. It is plain text
-rather than markup, deliberately: an excerpt with half a code block in it is
-not an excerpt.
-
-Each entry of a listing carries `replyContext` beside `inReplyTo` when it is a
-reply whose target has been fetched, the same object a reply's own page gets,
-so the feed can cite it in full.
-
-An entry's tags are not in a feed item. They belong under the entry, where
-there is one post's worth of them rather than twenty.
-
-**The heading level belongs to the layout**, not to the list. `feedHeading` is
-the level `post-list.njk` prints its titles at and defaults to 2, which is what
-a listing wants; a page whose feed sits under a heading of its own sets 3
-before including it, so the outline never skips a level:
-
-```njk
-{% set feedHeading = 3 %}
-{% include "partials/post-list.njk" %}
-```
-
-A listing with nothing on it says `No posts found.` in `p.empty`.
-
-`partials/pagination.njk` prints two links in `nav.pagination`, `← Previous`
-to the page before this one and `Next →` to the page after it, with `rel="prev"`
-and `rel="next"`, and nothing at all on a listing of one page. The arrows
-themselves are `aria-hidden`, because a screen reader that announced them would
-read the decoration and then the word.
-
-Each listing layout heads its own page: `layouts/home.njk` with the listing's
-title, and the three archives with a `header.archive-header` whose kicker says
-what kind of archive it is (Tag, Category, Author) over an `h1.page-title`
-naming whose: the term, or the person, followed by their `h-card`. The
-category archive's header is also a `header.category-header` and prints a
-`div.category-description` under the name when the context carries a
-`categoryDescription`; the CMS has no store of term descriptions, so nothing
-writes one today and the header is the heading alone.
-
-`layouts/404.njk` says `Content not found.` under a `Not found` kicker and
-links home and to the search. The 500 and 503 pages below open on a kicker the
-same way.
-
-`layouts/410.njk` is the page at the URL of a post or page that was moved to
-the trash (TASK-195). It says `This content has been deleted.` under a
-`Deleted` kicker and links home and to the search. The context is the 404's:
-`title`, `url` and `page.url`, and nothing of the deleted document. Its `.md`
-and `.json` representations answer 410 too. A trashed draft was never public,
-so its URL is a 404 instead.
-
-`layouts/500.njk` is the page a request gets when the server fails while
-answering it (TASK-129). It says `Something went wrong.` in an
-`article.server-error` and links home. The context is the 404's: `title`,
-`url` and `page.url`. The response is a 500 with `Cache-Control: no-store`, and
-the error itself goes to the server's log, never into the page. If this template
-fails too, the CMS answers with a plain HTML page of its own instead, so a theme
-cannot turn one failure into a crash. A request for the `.md` or `.json`
-representation gets a 500 in that format and never reaches this template.
-
-`layouts/503.njk` is the page a request gets while the site is in maintenance
-mode (TASK-130). It says `Down for maintenance.` in an `article.maintenance`.
-The context is the 404's, plus `until` (an ISO 8601 time) and `untilText` (the
-same time as an HTTP date) when the operator named when the site should be
-back. The response is a 503 with `Retry-After` and `Cache-Control: no-store`.
-The theme's files under `/theme/` are still served, so the page can use the
-stylesheet. If this template fails, the CMS answers with a plain HTML page of
-its own.
-
-### Search
-
-`layouts/search.njk` is the page at `/search/` (TASK-22). It prints
-`partials/search-form.njk`, and once there is a `query` a `p.search-summary`
-saying how many documents matched, a `div.search-results` of
-`article.search-result` entries, and the ordinary pager. It asks not to be
-indexed with `<meta name="robots" content="noindex">` in its `head` block.
-
-The context is a listing's with two differences. `query` is the words searched
-for, trimmed, and an empty string on the page before a search. Each entry in
-`posts` carries a `snippet`: a few words of
-HTML around the match, escaped, with every matched word in `<mark>`. Print it
-with `safe`. The results are best match first rather than newest first, and
-only what the public site would serve is ever among them.
-
-`partials/search-form.njk` is a `GET` form to `/search/` with the words in `q`,
-so it needs no JavaScript and a search is a URL. This layout is the only thing
-that includes it: the box used to be in the footer of every page as well, and
-search is a menu item now — a `Search | /search/` line like any other. The
-search page takes the path `/search/` ahead of any document permalinked there.
-
-### The front page
-
-`layouts/front-page.njk` is what a site gets at `/` once the Reading settings
-name a homepage (`homepage` in `content/_data/site.json`). It is that page read
-somewhere else: the same document, the same context, with `page.url` saying `/`
-rather than the permalink that redirects there.
-
-It draws the page's own title and words, and nothing else (decision-44):
-
-1. `h2.section-title`, the page's title. It is an `h2` because
-   `layouts/base.njk` heads the root path with the site title as the `h1`.
-2. `div.page-body.e-content`, the rendered body. There is no Published line,
-   because a front page is read as the site rather than as a page somebody
-   wrote on a Tuesday.
-3. The contact form, when the page's front matter says `contact: true`.
-
-It lists no posts, prints no line of links and prints no bio. A site that wants
-any of them on its front page overrides `layouts/front-page.njk` in its own
-theme. Two context keys are the front page's alone, for that override:
-
-- `newestPosts(count)` is a function. It returns the newest `count` published
-  posts as entries, in the same shape a listing's `posts` are, so
-  `partials/post-list.njk` prints them. Drafts, future-dated, unlisted and
-  trashed posts are left out. The theme chooses the count. The query runs only
-  when a template calls it, so a front page that lists nothing costs nothing.
-  A count that is not a whole number of at least 1 is an error.
-- `postsPage` is `{ title, url }` for the page carrying the listing, and is
-  **absent** when the site names none, because a link to a listing that has no
-  URL is a link to nothing.
-
-`newestPosts` replaces `recentPosts`, which held this month's posts when there
-were at least five and the five newest otherwise. An override that read
-`recentPosts` calls `newestPosts(5)` instead. This override draws the page's
-words, the five newest posts, a line of links and the site author's card as
-the site's representative h-card:
-
-```njk
-{% extends "layouts/base.njk" %}
-
-{% block content %}
-<div class="page-body e-content">
-  {{ content | safe }}
-</div>
-
-<h2 class="section-title">Recent Posts</h2>
-{% set posts = newestPosts(5) %}
-{% set feedHeading = 3 %}
-{% include "partials/post-list.njk" %}
-
-<p class="front-links">
-  {% if postsPage %}
-  <a href="{{ postsPage.url | url }}">{{ postsPage.title }}<span aria-hidden="true"> &rarr;</span></a>
-  {% endif %}
-  <a href="{{ "/search/" | url }}">Search<span aria-hidden="true"> &rarr;</span></a>
-</p>
-
-{% if soloAuthor %}
-{% set bioAuthor = soloAuthor %}
-{% set bioHome = "/" | absoluteUrl %}
-<hr>
-<footer>
-  {% include "partials/bio.njk" %}
-</footer>
-{% endif %}
-{% endblock %}
-```
-
-The stylesheet still styles `h2.section-title` and `p.front-links`, so an
-override can use both. Whatever the override prints, the solo author's
-`rel="me"` claims stay in the head of `/` (decision-45).
-
-### An archive page
-
-A page whose front matter says `archive: true` prints every post the site has
-published under its own words, newest month first:
-
-```html
-<section class="archive">
-  <h2>September 2026</h2>
-  <ol class="list-none">
-    <li>
-      <a href="/2026/09/hello/"><span>Hello</span></a>
-    </li>
-  </ol>
-  <h2>August 2026</h2>
-  …
-</section>
-```
-
-`partials/archive.njk` draws it and `layouts/page.njk` includes it. It is the
-whole archive on one page and nothing paginates it: an archive page is a way of
-finding one piece of writing rather than a listing to read through, which is
-also why there are no excerpts on it. Drafts and posts whose date has not
-arrived are absent, as they are everywhere else.
-
-`archiveMonths` is what it loops over, and it is on the context **only** for a
-page whose front matter says `archive: true`, so a layout asks:
-
-```njk
-{% if archiveMonths %}
-{% include "partials/archive.njk" %}
-{% endif %}
-```
-
-Each entry of it is `{ month, posts }`: `month` is the heading, `September
-2026`, and `posts` is `{ title, url, date }` for each post of it, newest first.
-Which month a post belongs to is the CMS's answer rather than the template's,
-because a date in a file is a UTC instant and the site's `timezone` is the lens
-it is read through — so the grouping and the date printed under an entry are
-one decision rather than two.
-
-The key is honoured wherever it is written, exactly as `contact: true` is: a
-theme that wants the list on some other kind of page adds the same three lines
-to that layout.
-
-### The head
-
-Beside the title, the canonical link and the feeds, every page carries a
-description, Open Graph and Twitter card tags, the site's icons and one
-JSON-LD graph. All of it is in the `head` block, so an override that only means
-to add a tag calls `{{ super() }}` first.
-
-**The description** is the page's own `description` from the front matter, else
-the entry's `summary` — the line the feeds publish — else `site.tagline`. It is
-printed once, as `<meta name="description">`, and the Open Graph and Twitter
-descriptions say the same thing.
-
-**The colours** come from the theme's `theme.json` (see
-[The manifest](#the-manifest)), on the context as `theme`.
-`<meta name="color-scheme">` comes before the stylesheet, so a reader in dark
-mode gets a dark canvas rather than a white flash while the stylesheet loads.
-`<meta name="theme-color">` is printed twice, once with
-`media="(prefers-color-scheme: light)"` and once for dark.
-
-**The card.** `og:title` is the page's title, or the site's on the front page;
-`og:site_name` is always the site's. `og:type` is `article` on a rendered post
-or page and `website` everywhere else, a listing carrying a page's front matter
-included. `og:url` is the canonical URL: the page's own, or the `original` a
-post first published elsewhere names. An article also carries
-`article:published_time`, `article:modified_time` (the `updated` date, else the
-publish date), `article:author` (the author's profile URL here, else their
-name) and one `article:tag` per tag.
-
-**The picture** is the first of these that the page has, on the context as
-`shareImage`:
-
-1. The `image` in the entry's front matter.
-2. `site.avatar`, which only a hand edit of `site.json` sets.
-3. The profile photo of the person the page is by: the writer of a post or page
-   that names an author, the user of an author archive, and the site's author
-   on a solo-author site's homepage and other pages about nobody in particular.
-4. The site icon, from `icon` in `site.json`.
-
-A page with none of these prints no `og:image` and no `twitter:image` rather
-than an empty one. The picture always carries `og:image:alt` and
-`twitter:image:alt`. The alt text is what the media library says about the
-upload, else words for what it shows. For the entry's own picture, its
-`imageAlt` front matter comes first, and the entry's title last. For the
-avatar, the last resort is the site's author; for a photo, that person's
-display name; for the icon, the site's title. `og:image:width` and
-`og:image:height` are printed when the image's variants have been derived,
-because the size is read from their sidecar rather than from the file.
-`twitter:card` is `summary_large_image` for a picture at least 1200 pixels wide
-and wider than it is tall. Everything else, a square photo included, is
-`summary`, the small picture beside the words.
-
-**The icons** come from the site's `icon` setting in `site.json`, else
-`site.avatar`, through the derived images (decision-10). `icon` exists for a
-site whose avatar is a face and whose mark is a logo. The head links `icon` at
-32 and 16 pixels and `apple-touch-icon` at 180, each a square PNG cropped from
-the middle of the picture and encoded the first time a browser asks for it. An
-SVG icon is linked first as itself, with `type="image/svg+xml"` and no
-`sizes`, and the PNGs are rasterised from it. They are on the context as
-`icons`, a list of `{ rel, sizes, type, href }`, which is empty, and the links
-are not printed at all, when the site has neither setting, when it names a
-file no icon can be made of, or when image optimization is off.
-
-**The favicon and the manifest** are routes, not templates. `/favicon.ico`
-holds 16, 32 and 48 pixel frames drawn from the same picture, because browsers
-and crawlers ask the root for it whatever the head links; it answers 404 on a
-site with no icon. `/manifest.webmanifest` gives the site's title as `name` and
-`short_name`, `start_url` `/`, `display` `minimal-ui`, the theme's light
-`themeColor` as `theme_color` and `background_color`, and icons at 192 and 512
-pixels plus a maskable 512 whose picture sits inside the middle 80%, padded
-with its own dominant colour. The head links it on every page.
-
-**The search description** is a route too. `/opensearch.xml` is an OpenSearch
-1.1 description that names the site by its title (cut to the 16 characters
-`ShortName` allows), describes it by its tagline, else its title, shows
-`/favicon.ico` as its `Image` when the site has an icon, and searches
-`/search/?q={searchTerms}`. Every URL in it is absolute and carries the base
-path. The head links it on every page with `<link rel="search"
-type="application/opensearchdescription+xml">`, outside the `head` block, so a
-browser offers the site as a search engine. A theme that replaces `base.njk`
-copies that line to keep the offer.
-
-**The embed card** is a route too. `/_geekity/oembed?url=…` is an oEmbed
-provider: for the URL of a published post or page it answers a `rich` embed
-with the title, the author and their archive, the site as provider, a
-thumbnail when the post's own `image` has a recorded size, and an `html`
-card that is a blockquote of escaped text and links with no script, followed
-by a hidden, sandboxed `<iframe>` of `/_geekity/embed?url=…`. That route is
-the same card as a page of its own, and it is the one response another site may
-frame. WordPress keeps a card from a provider it does not know only when the
-card has an iframe, and it shows the frame once the page inside reports its
-height. A consumer that strips iframes still has the blockquote. `maxwidth`
-and `maxheight` are honoured, `format=xml` gives the same fields as XML, and
-any other URL is a 404. The head of each post and page links it with
-`<link rel="alternate" type="application/json+oembed">` and its `text/xml+oembed`
-twin, outside the `head` block. A theme that replaces `base.njk` copies those
-lines to keep the card.
-
-**The structured data** is `partials/jsonld.njk`, one `<script
-type="application/ld+json">` holding one `@graph` per page, and it is the only
-structured data the theme emits — there is no Microdata anywhere, by
-decision-16, because the visible markup already carries microformats2 for the
-IndieWeb. The graph holds:
-
-- `WebSite`, always, with the site's title, tagline and URL, and a
-  `potentialAction` that is a `SearchAction` on
-  `/search/?q={search_term_string}`. On a site whose author is a user, its
-  `publisher` and `about` both point at that user's Person, on every page. On
-  a site with several authors its `publisher` is the Organization below and it
-  has no `about`. With a site license, `license` is its URL.
-- `Organization`, on a site with several authors only: the site itself, named
-  for its title, at `{baseUrl}/#organization`. It publishes the `WebSite` and
-  every entry.
-- `Person`, from `siteAuthor`: their name, archive URL, avatar, bio, job title
-  and location, and a `sameAs` of their profile links and their actor id, which
-  is what asserts that the schema.org Person and the fediverse actor are one
-  identity. Identity comes from a user profile, so a site — or a byline —
-  naming nobody with an account here prints no Person, and the `author`
-  reference goes with it. A site with several authors prints no Person on a
-  page about nobody in particular.
-- `ProfilePage` on an author archive, whose `mainEntity` is that Person.
-- `BlogPosting` on a post and `Article` on a page, with the headline, URL,
-  `mainEntityOfPage`, `datePublished`, `dateModified`, description, image,
-  `author`, and the site's `publisher`: the site author's Person, or the
-  Organization. A post with no title is headed by the words its `<title>`
-  names it by, its `label`, cut on a word boundary to at most 110 characters.
-  A post with no words either is labelled by what it is (TASK-261): "Liked",
-  "Reposted", "Bookmarked" or "Reply to" and the cited page's stored title,
-  else the host its citation line names ("Liked a page on www.youtube.com"), and
-  for a photo post its first photo's alt text, cut to ten words like a note's
-  (TASK-264), or "Photo" when that photo has none. The kicker still says Photo
-  and no heading is printed. "Untitled" is the last fallback.
-  Its `image` is the picture the Open Graph tags print, so the two always
-  agree (see [The head](#the-head)). Its `license` is the page's license URL,
-  the front matter's over the site's, and absent with none.
-- `BreadcrumbList` wherever the page prints a breadcrumb (see
-  [The page shell](#the-page-shell)): one `ListItem` per crumb with its
-  `position`, `name` and absolute URL as `item`.
-
-A site that wants a different graph — more types, an `Organization` publisher,
-nothing at all — writes its own `partials/jsonld.njk` and that file replaces
-this one, like any other partial.
-
-### Prefetching and page transitions
-
-Two tags near the top of `<head>` make moving between pages feel faster. Both
-are progressive enhancement: a browser that does not support one ignores it.
-
-**Speculation rules.** The `speculationRules` block prints one `<script
-type="speculationrules">` that asks the browser to prefetch a page the reader
-is about to open. It covers links to this site's own pages, at `moderate`
-eagerness, which in Chrome is a hover of about 200 milliseconds or the start of
-a tap. It never prefetches:
-
-- `/admin` and anything under `/admin/`, which includes `/admin/logout`.
-- Any path with `logout` in it.
-- A feed: `/feed/`, `/feed/atom/`, `/feed/json/`, and any other path that has
-  a `/feed/` segment, such as a tag's feed or a post's comments feed.
-- A file under `/uploads/`.
-- A URL with a query, such as `/search/?q=words`.
-
-Every pattern is written through the `url` filter, so a site served from a
-subdirectory prefetches only its own pages.
-
-**No rules reach a signed-in reader.** The CMS removes every `<script
-type="speculationrules">` from a page it draws for somebody signed in, the same
-page that carries [the admin bar](#the-admin-bar). That page is drawn for one
-person and never stored, so a prefetch of it is wasted work. A site theme that
-writes its own rules does not have to check who is reading.
-
-**View transitions.** The `viewTransitions` block prints a `<style>` that opts
-into cross-document view transitions. The browser cross-fades from one page of
-the site to the next, with no JavaScript. The rule is inside `@media
-(prefers-reduced-motion: no-preference)`, so a reader who asks for reduced
-motion gets no transition:
-
-```css
-@media (prefers-reduced-motion: no-preference) {
-  @view-transition {
-    navigation: auto;
-  }
-}
-```
-
-A site theme that wants a different animation adds `::view-transition-*` rules
-to its own stylesheet.
-
-**Turning either off.** Override its block with nothing in it:
-
-```njk
-{% extends "layouts/base.njk" %}
-
-{% block speculationRules %}{% endblock %}
-{% block viewTransitions %}{% endblock %}
-```
-
-### Colours
-
-Every colour is a custom property on `:root`, and these tokens are the
-override contract: a site that only wants different colours redefines them in
-its own stylesheet rather than replacing this one. Tailwind's own palette is
-cleared in `src/style.css`, and its utilities (`text-ink`, `bg-paper`,
-`border-edge` and the rest) are mapped onto these properties with
-`@theme inline`, so redefining a token recolours every rule that uses it.
-
-A second scheme under `@media (prefers-color-scheme: dark)` redefines the same
-tokens on dark paper, and `color-scheme: light dark` lets a browser paint its
-own form controls and scrollbars to match. There is no toggle: the reader's
-system setting is the setting.
-
-Both schemes meet the Colour contrast rule of the
-[specification.website checklist](https://specification.website/checklist.md):
-every run of text, the small kickers, dates and meta lines included, at 7:1
-(WCAG 1.4.6, AAA) on whatever it sits on, and every border a reader relies on
-(a field, a card, a code block, the focus outline, the citation and blockquote
-rules) at 3:1 (1.4.11). Nothing a reader needs is drawn at reduced opacity.
-That is a test rather than a claim: `src/web/theme-colors.test.ts` reads the
-tokens out of the compiled stylesheet and computes the ratio of every pair the
-design puts on screen, so a colour changed in `src/style.css` that breaks one
-fails the build.
-
-| Token                     | Utility    | What it colours                                                        |
-| ------------------------- | ---------- | ---------------------------------------------------------------------- |
-| `--color-body`            | `paper`    | The paper, and the words on a submit button.                           |
-| `--color-text`            | `ink`      | Body text and headlines.                                               |
-| `--color-muted`           | `muted`    | Kickers, dates, meta lines, decks, quotes, the bio note, the footer.   |
-| `--color-primary`         | `accent`   | Links, a kicker's kind word, the citation rule, the submit button.     |
-| `--color-secondary`       | `accent-2` | Tag links and the focus outline.                                       |
-| `--color-rule`            | `rule`     | Decorative hairlines only: between entries, above the footer.          |
-| `--color-edge`            | `edge`     | Borders a reader relies on: fields, the previous and next cards, code. |
-| `--color-base`            | `surface`  | A sunk surface: fields, notices, a face with no avatar.                |
-| `--color-base-2`          | —          | A cooler sunk surface.                                                 |
-| `--color-base-3`          | —          | The raised surface: the focused skip link.                             |
-| `--color-code-background` | `code`     | Behind `code` and a fenced block.                                      |
-| `--color-code-text`       | —          | Code with no highlighting on it.                                       |
-| `--color-error`           | `error`    | A field that will not do, and what the form says about it.             |
-
-`--color-rule` is the one token in no contrast pair, because it is decoration:
-a site that recolours it may make it as faint as it likes. Anything drawn with
-`--color-edge` has to stay at 3:1 against the paper and the surface.
-
-### Code highlighting
-
-The CMS renders a fenced block as `<pre tabindex="0"><code
-class="language-x">` and highlights nothing: highlighting is a theme's, and it
-happens on the client (decision-16). The `tabindex` is the core's doing and is
-there on every `<pre>`, because a block wider than the measure scrolls sideways
-and a scroll container nothing can focus cannot be read from a keyboard.
-
-This theme highlights with **[highlight.js](https://highlightjs.org/)**,
-self-hosted at `static/highlight.js` and pinned — nothing is fetched from a
-CDN. The `scripts` block of `layouts/base.njk` loads it, deferred, **only on a
-page whose rendered body holds a `language-` class**, so a page with no code on
-it ships no JavaScript at all. Auto-detection is off: a block with no language,
-or one naming a language the bundle does not carry, is left exactly as the
-renderer wrote it — its class, its plain text, no highlighting.
-
-The bundle carries the core and eighteen grammars — `bash`, `css`, `diff`,
-`dockerfile`, `go`, `ini`, `javascript`, `json`, `markdown`, `nginx`, `php`,
-`python`, `rust`, `shell`, `sql`, `typescript`, `xml` and `yaml`, with their
-aliases, so `js`, `ts`, `html`, `yml` and `sh` all work. It is a build product
-that is nevertheless committed, so a site gets a working highlighter out of the
-package with no build step. Rebuilding it is one command:
-
-```
-pnpm --filter @geekity/cms build:highlight
-```
-
-Run that after bumping the `highlight.js` devDependency or editing the language
-list in `scripts/build-highlight.js`, and commit what it writes.
-`src/web/highlight-bundle.test.ts` fails when the committed file was built from
-a different version of highlight.js than the one installed.
-
-**The palette is Tomorrow**, the one both of the sites this design comes from
-used: Chris Kempson's Tomorrow on light paper and Tomorrow Night on dark, from
-highlight.js's own base16 themes, which is also what decides which `hljs-`
-scope takes which slot. None of the light colours is the stock one: a syntax
-theme is drawn for an editor, where a faint comment is a feature, and here code
-is text like any other and meets 7:1 on its block, the bar every run of text
-on the page meets. Each light colour was darkened along its own hue until it
-did and no further, and four of the dark ones (the comment grey, the red, the
-blue and the `base0F` brown) were lightened toward white the same way. Every one
-of them is in the contrast test beside the rest of the palette.
-
-| Token                             | base16   | What it colours                            |
-| --------------------------------- | -------- | ------------------------------------------ |
-| `--color-code-comment`            | `base03` | Comments.                                  |
-| `--color-code-tag`                | `base04` | Markup tags.                               |
-| `--color-code-name`               | `base08` | Variables, names, selectors, list bullets. |
-| `--color-code-literal`            | `base09` | Numbers, constants, attributes, links.     |
-| `--color-code-class`              | `base0A` | Class names, bold.                         |
-| `--color-code-string`             | `base0B` | Strings and inline code.                   |
-| `--color-code-support`            | `base0C` | Built-ins, regexps, quotes.                |
-| `--color-code-function`           | `base0D` | Function names, headings, attributes.      |
-| `--color-code-keyword`            | `base0E` | Keywords, types, italic.                   |
-| `--color-code-meta`               | `base0F` | Preprocessor and embedded-language lines.  |
-| `--color-code-added-background`   | —        | An added line in a diff.                   |
-| `--color-code-removed-background` | —        | A removed line in a diff.                  |
-
-Delimiters, operators and substitutions are deliberately `--color-code-text`,
-the block's own ink: they are most of the characters on screen and a colour
-there is noise. A `diff` block reads by the line rather than by the token, the
-way the source site's `prism-diff.css` did: `.hljs-addition` and
-`.hljs-deletion` take a tint out to the edges of the block and keep the ink, so
-the `+` and the `-` in the text carry the meaning as well as the colour does.
-
-**Swapping it.** Four sizes of change, smallest first:
-
-- _Another palette, same highlighter._ Redefine the dozen `--color-code-*`
-  tokens. Note that `static/style.css` is an all-or-nothing override: a theme
-  that ships its own stylesheet owns these rules too, and a fenced block on it
-  is unhighlighted until it writes them.
-- _Other languages._ Edit `LANGUAGES` in `scripts/build-highlight.js`, rebuild,
-  and commit — or put your own `static/highlight.js` in your theme, which the
-  `/theme/` route resolves before the packaged one.
-- _Another highlighter._ Override the `scripts` block with your own tag. The
-  markup is `pre > code.language-x`, which is what every highlighter reads.
-- _None._ Override the `scripts` block with nothing in it.
-
-```njk
-{% extends "layouts/base.njk" %}
-
-{% block scripts %}{% endblock %}
-```
-
-### Videos
-
-A YouTube or Vimeo URL on a line of its own in a post plays as the video
-(decision-34; doc-2 lists the addresses it knows). The core renders it into the
-body, so it reaches a theme inside `content` as:
-
-```html
-<figure class="video-embed video-embed-youtube">
-  <iframe
-    src="https://www.youtube-nocookie.com/embed/dQw4w9WgXcQ"
-    width="560"
-    height="315"
-    title="YouTube video"
-    loading="lazy"
-    allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
-    referrerpolicy="strict-origin-when-cross-origin"
-    allowfullscreen
-  ></iframe>
-  <figcaption>
-    <a href="https://www.youtube.com/watch?v=dQw4w9WgXcQ"
-      >https://www.youtube.com/watch?v=dQw4w9WgXcQ</a
-    >
-  </figcaption>
-</figure>
-```
-
-It is one line in the real output. A Vimeo video is the same with
-`video-embed-vimeo`, a `https://player.vimeo.com/video/ID?dnt=1` player and the
-title `Vimeo video`. The core sets no style on it: with nothing from the theme
-the player is the providers' standard 560 by 315.
-
-**Paper** makes it responsive. `.video-embed iframe` takes the full width of
-the text column at 16:9, with the rounded corners an image has, and the
-figcaption takes the muted caption style every figure in a post has. A theme
-that ships its own `static/style.css` writes that rule itself:
-
-```css
-.video-embed iframe {
-  width: 100%;
-  height: auto;
-  aspect-ratio: 16 / 9;
-}
-```
-
-The figcaption is the link a feed reader, a fediverse server or the embed view
-keeps when it drops the iframe. A theme that would rather not show it on the
-page can hide `.video-embed figcaption`; the feeds carry it either way.
-
-## Mail templates
-
-The messages the CMS sends live under `mail/` and resolve the same way, so a
-`mail/test.txt.njk` in the theme the site wears replaces the text of the test
-message and leaves its subject and HTML twin coming from the package. Each message is up to three
-files:
-
-| File                      | What it is                                                     |
-| ------------------------- | -------------------------------------------------------------- |
-| `mail/<name>.subject.njk` | The subject. Rendered to a single line. Optional.              |
-| `mail/<name>.txt.njk`     | The plain text body. **Required.**                             |
-| `mail/<name>.html.njk`    | The HTML twin. Optional; without it the message is plain text. |
-
-A message that has no `.txt.njk` anywhere on the search path is an error rather
-than an empty email, so a typo in a template name is reported instead of sent.
-
-The package ships seven messages:
-
-| Name               | When it goes                                     | What `data` carries                                                                                                                        |
-| ------------------ | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------ |
-| `test`             | Send test email, on Settings.                    | Nothing.                                                                                                                                   |
-| `password-reset`   | Somebody asked to reset a password.              | `username`, `resetUrl`, `expiresAt`, `expiresInHours`.                                                                                     |
-| `password-changed` | A reset link was used.                           | `username`, `signedOut` (how many sessions ended).                                                                                         |
-| `comment-pending`  | A comment or webmention is waiting for approval. | `comment`, `post` (`title`, `url`), `actions` (one `{ action, label, url }` each for approve, spam and delete), `queueUrl`.                |
-| `comment-digest`   | An hourly or daily digest of what is waiting.    | `items` (one `{ comment, post, actions }` each), `total` waiting, `more` beyond the ones listed, the `mode` that asked for it, `queueUrl`. |
-| `comment-reply`    | A reply to somebody's comment was approved.      | `reply`, `comment` (the one it answers), `post`, `unsubscribeUrl`.                                                                         |
-| `contact-message`  | Somebody filled in a page's contact form.        | `message` (`id`, `subject`, `text`, `received`), `from` (`name`, `email`), `page` (`slug`, `permalink`, `title`, `url`), `messagesUrl`.    |
-
-The `comment` inside each of a digest's `items` is the same shape as
-`comment-pending`'s, and its `actions` are the same three links, minted per
-recipient because each is spent the first time it is used. A digest is built
-from the queue as it stands when it is sent, so an item moderated in the
-meantime is simply not in it, and no digest is sent to somebody with an empty
-queue.
-
-`comment` and `reply` above are the same shape: `author`, `website`, `source`
-(`comment` or `webmention`), `kind`, `text`, `html`, `submitted`, and `url`.
-The commenter's email address is deliberately **not** among them — the message
-goes to a moderator, but it also goes through a mail provider's servers, and
-nothing on that screen needs it.
-
-The links in `actions` and `unsubscribeUrl` each carry a signed token and work
-without a login. Print them; do not try to build one.
-
-`contact-message` is sent with reply-to set to the sender, so answering it in a
-mail reader answers the person who wrote it. `message.text` is plain text as it
-was typed — print it, do not render it as Markdown or as HTML.
-
-The subject and the plain text body render with autoescaping **off**, because
-neither is HTML: `&` between two query parameters stays an `&`, and an
-apostrophe in somebody's name stays an apostrophe. The HTML twin escapes as
-every other template does.
-
-The context is `site` (that is `content/_data/site.json`), `baseUrl`, and
-whatever the feature that sent it passed as `data`. The `date`, `url` and
-`absoluteUrl` filters are the same ones a page has, so a message can write a
-link with `{{ "/admin/" | absoluteUrl }}`.
-
-Writing `mail/welcome.txt.njk` into the theme is enough to add a message this
-package never shipped; nothing has to be registered.
-
-## Template context
-
-The context mirrors what an Eleventy layout receives, so a layout ported from
-an Eleventy build needs few edits. It is part of the package's semver contract.
-
-Every template gets:
-
-| Key           | What it holds                                                                                                                                                                                           |
-| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `site`        | `content/_data/site.json`, if the site has one, over the defaults `title` and `url`. Any key in the file is readable, so `site.tagline`, `site.author` and anything else a site adds are all available. |
-| `menus`       | Every menu the site stores, by name, marked for this page: `menus.primary`, `menus.footer`, and any other name. See [Navigation](#navigation).                                                          |
-| `siteAuthor`  | Who the page is by, as a profile. **Absent** when nobody matches. See [Bylines and author archives](#bylines-and-author-archives).                                                                      |
-| `soloAuthor`  | The site author's profile, on every page of a site whose Site author setting names a user. **Absent** on a site with several authors. See [The bio](#the-bio).                                          |
-| `icons`       | The site's icons, as `{ rel, sizes, type, href }`. Empty until the site has an icon or an avatar to derive them from. See [The head](#the-head).                                                        |
-| `theme`       | The colours the theme declares, as `{ colorScheme, themeColor: { light, dark } }`, each absent when no theme declares it. See [The manifest](#the-manifest).                                            |
-| `shareImage`  | The picture a shared link shows, as `{ url, alt, size: { width, height }, card }`. `size` is absent when it is not known. **Absent** when there is no picture. See [The head](#the-head).               |
-| `llmsTxt`     | The path of `/llms.txt`, while the site serves it. **Absent** when the site has turned it off. The default theme links it from the front page only.                                                     |
-| `license`     | The page's license as `{ name, url }`: the page's `license` front matter, else the site's. **Undefined** with none. It replaces the raw front matter value on the context.                              |
-| `siteLicense` | The site's own license as `{ name, url }`, whatever the page says. **Undefined** with none.                                                                                                             |
-
-A document — one post, one page, or one entry of a listing — adds:
-
-| Key                                         | What it holds                                                                                                     |
-| ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
-| `title`                                     | Display title.                                                                                                    |
-| `date`                                      | Publish date, a JavaScript `Date` at the UTC instant the file holds. Absent when the document has none.           |
-| `updated`                                   | Last modified date, a `Date`, when the front matter has one.                                                      |
-| `tags`                                      | The document's tags, in file order.                                                                               |
-| `categories`                                | The document's categories, in file order.                                                                         |
-| `content`                                   | The Markdown body rendered to HTML. Print it with `\| safe`.                                                      |
-| `summary`                                   | Its `description` as plain text, else an excerpt of the body, else empty. The line the feeds publish.             |
-| `url`                                       | The document's URL path, the same value as `page.url`.                                                            |
-| `page.url`                                  | The document's URL path. Always ends in `/`.                                                                      |
-| `page.date`                                 | The same `Date` as `date`.                                                                                        |
-| `page.fileSlug`                             | The permalink's last segment.                                                                                     |
-| `page.inputPath`                            | The source file, relative to the content directory.                                                               |
-| `type`                                      | `post` or `page`.                                                                                                 |
-| `permalink`, `slug`, `draft`, `description` | Straight from the front matter.                                                                                   |
-| `lang`                                      | The `lang` front matter as a canonical tag, such as `fr-CA`. Absent when it names none or no tag.                 |
-| `enclosure`                                 | The post's recording, parsed, with `player` (`audio` or `video`) and `transcript.captions`. Absent with none.     |
-| `photos`                                    | The post's photos, each `{ url, alt, html }`; `html` is the `img.u-photo`, responsive. Empty with none.           |
-| `citations`                                 | What it reposts, likes or bookmarks, each `{ property, url, context }`; `context` as `replyContext`, when known.  |
-| `read`                                      | A read post's `{ status, statusLabel, of, line }`; `of` is `{ name, author, uid, uidLabel, url }`.                |
-| `rsvp`                                      | An RSVP's `{ value, label, line }`: `yes`, `no`, `maybe` or `interested`, its words, and its `p-rsvp` line.       |
-| `event`                                     | An event's `{ start, end, location }`: `Date`s, and `{ kind: "place", name }` or `{ kind: "virtual", url }`.      |
-| `syndicateTo`                               | On a post's page, the syndication targets it selects, each `{ id, name, url }`. Empty with none.                  |
-| `syndication`                               | Its copies elsewhere, each `{ url, label }`: front matter `syndication`, and on its page the copies targets made. |
-| `original`                                  | Where it was first published, `{ url, label }`: `canonical_href`, named by `canonical_name` or its host.          |
-| `author`                                    | Who wrote it, as a profile rather than a string. See [Bylines and author archives](#bylines-and-author-archives). |
-| `activityStreams`                           | The post's ActivityPub object id, absolute. Only on a rendered published post.                                    |
-| `previous`                                  | The published post before this one by date, as `{ title, url }`. Absent on the oldest post.                       |
-| `next`                                      | The published post after it. Absent on the newest post, and on a page.                                            |
-| `backlinks`                                 | The site's listed posts and pages that link to it, newest first, each `{ title, url, date }`. Empty with none.    |
-| `newestPosts`                               | A function, front page only: `newestPosts(5)` is the five newest published posts, as entries.                     |
-| `postsPage`                                 | The page carrying the listing, as `{ title, url }`, on the front page only. Absent when the site names none.      |
-| `archiveMonths`                             | Every published post as `{ month, posts }`, newest month first. Only on a page that says `archive: true`.         |
-| `webmention`                                | Where a webmention about this page is sent. Only on a rendered document, and only while the site takes them.      |
-| `noindex`                                   | `true` on an unlisted or unpublished page, which the base layout prints as a robots `noindex` meta. Else absent.  |
-| `conversation`                              | The replies, likes and boosts under the post. Only when there are any. See [The conversation](#the-conversation). |
-| everything else                             | Any front matter key the CMS does not model is on the context under its own name.                                 |
-
-A listing — the home page, a tag archive, a category archive or an author
-archive — adds:
-
-| Key                                        | What it holds                                                                     |
-| ------------------------------------------ | --------------------------------------------------------------------------------- |
-| `title`                                    | The site title on the home page, the term on a taxonomy archive.                  |
-| `posts`                                    | The documents on this page of the listing, newest first, each in the shape above. |
-| `pagination.items`                         | The same array, under the name Eleventy gives it.                                 |
-| `pagination.pageNumber`                    | Zero-based index of this page, as in Eleventy.                                    |
-| `pagination.totalPages`, `.total`, `.size` | How many pages, how many documents, how many per page.                            |
-| `pagination.href.first/last/next/previous` | Pager URLs. `next` and `previous` are `null` at the ends.                         |
-| `pagination.pages`                         | Every page's URL, in order.                                                       |
-| `tag`                                      | The tag, on a tag archive only.                                                   |
-| `category`                                 | The category, on a category archive only.                                         |
-| `author`                                   | The person, on an author archive only. Same shape as a post's `author`.           |
-
-How many posts a listing page holds comes from `postsPerPage` in
-`content/_data/site.json`, and defaults to 10. How many entries a feed holds
-comes from `feedSize` in the same file, and defaults to 20. The `<html lang>`
-comes from `language`, and defaults to `en`. A document whose `lang` names
-another language carries it on its own `<article>`, in an entry, a listing and
-search results alike, through `partials/lang.njk`, and the dates inside that
-article are written in it (see the `date` filter). The rssCloud and WebSub server the
-feeds advertise comes from `notifyServer`, and is empty for none; the theme
-writes nothing for it, because a cloud is advertised in the feed rather than on
-the page.
-
-## Bylines and author archives
-
-`author` on a document is the person the front matter names, resolved against
-the site's users. The fields come from their profile on **Users** in the admin,
-which is the one place identity is written:
-
-| Key               | What it holds                                                                                                  |
-| ----------------- | -------------------------------------------------------------------------------------------------------------- |
-| `author.name`     | What to print: their display name, else their username, else the raw name the file gives.                      |
-| `author.url`      | Their archive, `/author/{username}/`. **Absent** when the name is nobody this site has.                        |
-| `author.username` | Their login. Absent for the same reason `url` is.                                                              |
-| `author.bio`      | What they wrote about themselves, when they wrote any.                                                         |
-| `author.avatar`   | Their picture, as a path or URL. Absent when they have none.                                                   |
-| `author.jobTitle` | What they do, when their profile says.                                                                         |
-| `author.location` | Where they are, as they wrote it.                                                                              |
-| `author.links`    | `{ label, href }` for each link on their profile, in the order they listed them. Absent when they listed none. |
-
-`author` is absent altogether when the document names no author, so anything
-printing it is `{% if author %}`. Guard the link with `{% if author.url %}`: a
-file may name somebody who has no account here — a guest post, or a colleague
-whose account has gone — and that name is still printed, it simply links
-nowhere. [The bio](#the-bio) does both, and is what the theme prints instead of
-the `partials/byline.njk` it used to have.
-
-`layouts/author.njk` is that person's archive, at `/author/{username}/`, with
-their pages at `/author/{username}/page/2/` and their three feeds under
-`/author/{username}/feed/`. It is headed with their name and then the bio —
-the avatar, the note and the `rel="me"` links, the same card that ends each of
-their posts — and lists their published posts newest first. The source design has no author archive, so
-the heading is the CMS's own; the h-card under it is the one partial the theme
-has. A user with no profile still has one; they are called by their username.
-
-`siteAuthor` is the same object on a different question: not who wrote this
-document, but who the page in front of the reader is by. It is what the bio and
-any structured data a theme emits should both read, so that what a reader sees
-and what a machine reads cannot drift apart. The footer does not read it at
-all: the site's links are `menus.footer`, typed rather than borrowed from an
-account. It resolves in this order:
-
-- the document's own `author`, on a post or a page that names one;
-- the person whose archive it is, on an author archive;
-- the site author, `soloAuthor`, everywhere else — the home page, a taxonomy
-  archive, a page that names nobody, the 404.
-
-It is **absent** when none of those name anybody this site has, which on a
-site with several authors is every page about nobody in particular. Write
-`{% if siteAuthor %}` around the bio.
-
-The URL is not only a page. Each user is an ActivityPub actor at that address,
-so it is the page a follower lands on when they click through from the
-fediverse. `author` is therefore a reserved first URL segment, like `tag` and
-`feed`: no document can be permalinked under it and no taxonomy base can take
-it.
-
-## Navigation
-
-A site stores its menus by name in `content/_data/site.json`:
-
-```json
-{
-  "menus": {
-    "primary": [
-      { "label": "Home", "url": "/" },
-      { "label": "About", "url": "/about/" }
-    ],
-    "footer": [
-      { "label": "Colophon", "url": "/colophon/" },
-      { "label": "Mastodon", "url": "https://example.social/@me", "rel": "me" }
-    ]
-  }
-}
-```
-
-Every template gets them as `menus`, keyed by the same names, already in order
-and already knowing which item is the page being looked at:
-
-```njk
-{% for item in menus.footer %}
-<a href="{{ item.url | url }}">{{ item.label }}</a>
-{% endfor %}
-```
-
-That is the whole interface, so a theme renders a menu this one has never heard
-of by looping over the name a site stored it under.
-
-### The areas a theme declares
-
-`theme.json` says where a theme renders a menu, so the Navigation screen can
-offer those places and nowhere else. This theme declares two:
-
-```json
-{
-  "name": "Default",
-  "kind": "site",
-  "areas": [
-    { "name": "primary", "label": "Site menu" },
-    { "name": "footer", "label": "Footer links" }
-  ]
-}
-```
-
-`name` is the key under `menus`, in `site.json` and on the context. `label` is
-what a person choosing an area reads; leave it out and it falls back to the
-name. Declare a third area and a site can fill it in; declare none and the
-theme renders no menu.
-
-The declaration is for the screen, not for the render. Every menu the site
-stores is on the context whether or not a theme declared an area for it — a
-menu nothing loops over is rendered nowhere and kept, which is what lets
-somebody write the menu a theme will use before switching to that theme. An
-`areas` that is missing, or that will not read, leaves the theme with none
-rather than failing to load it.
-
-### One item
-
-Each item is `{ label, url, current }`, plus `rel` on a link that carries `rel`
-values. `url` is a site-root path or an absolute URL for somewhere else, so put
-it through the `url` filter and a site served from a subdirectory still links
-correctly. `current` is true for the item whose path is the one being rendered,
-comparing without the trailing slash; an item pointing off the site is never
-current. `rel` is one string holding every value the line carried, already
-lower case and each said once — print it as the whole attribute,
-`rel="{{ item.rel }}"`, rather than building one of your own. `me` is the value
-most menus have, for the IndieWeb's identity check: Mastodon verifies a link on
-a profile by looking for a `rel="me"` link back, so a footer link to a profile
-marked `me` is what makes the tick appear.
-
-### Where this theme prints them
-
-`partials/menu.njk` holds the markup, as one macro:
-
-```njk
-{% import "partials/menu.njk" as nav %}
-{{ nav.list(menus.footer, "Footer") }}
-```
-
-The second argument is the `aria-label`, which is what tells a reader on a
-screen reader which of a page's menus this one is. Nothing is printed for a
-menu with nothing in it.
-
-`menus.primary` is printed once, in `header.global-header`, on every page
-(TASK-105). At the root, where the header is the site title with the tagline
-under it, the menu is a line of its own under the tagline; everywhere else,
-where the header is the small link home, the stylesheet lays the header out as
-one line and the menu sits beside it. Nothing decides between two places any
-more: a reader looks in the same spot whatever they are reading, and a layout
-that overrides the `content` block cannot lose the navigation by not printing
-a bio.
-
-`menus.footer` is printed in the `footer` block of `layouts/base.njk`, under
-the copyright line, and is the whole of what the footer links — a feed, a
-colophon, a webring, a profile marked `me`. The footer reads nothing off an
-account: it used to print one `rel="me"` link per entry of `siteAuthor.links`,
-which meant one nominated user's links stood for the site and nobody else's
-appeared at all.
-
-Every menu reads the same: a link in one is the colour, the underline and the
-size of a link in the page's prose, in the sans heading font a `nav` is set in
-(TASK-111). A menu is navigation somebody is meant to use rather than a
-footnote, so none of them is set smaller than the words around it, and the same
-goes for the `rel="me"` links `partials/bio.njk` prints under a post. The two
-links that read as plain text instead are the site title and
-`a.header-link-home`, which are the page saying where it is rather than
-somewhere to go, and the stylesheet names those two rather than reaching for
-every link that happens to sit in a `<header>`.
-
-`menus.primary` is the whole of the site menu, in the order the Navigation
-screen names it. Both areas are declared in this theme's `theme.json`, which is
-what puts them on `/admin/navigation` with those labels; a theme that renders a
-third menu declares a third area. A page cannot put itself in a menu; a page
-that should be linked — including the one a site serves as its front page,
-typed `Home | /` — is typed into the box there.
-
-Because the menus live in `site.json`, an Eleventy build of the same content
-renders the same ones; `docs/eleventy.config.example.js` builds them as
-`collections.menus`.
-
-## Feeds
-
-`partials/feeds.njk` holds two macros. `feedLinks(root, title)` writes the three
-`rel="alternate"` links for a listing's RSS, Atom and JSON feeds — RSS first,
-because it is what most subscribers hold:
-
-```njk
-{% import "partials/feeds.njk" as feeds %}
-{{ feeds.feedLinks("/", site.title) }}
-```
-
-`root` is any listing URL ending in `/`; the macro appends `feed/`, `feed/atom/`
-and `feed/json/` and puts each through the `url` filter, so the links carry the
-base path of a site served from a subdirectory. The arguments carry everything
-the macro needs, so it can be imported without `with context`.
-
-`commentsFeedLink(feed, title)` writes the one link a comments feed has. It
-takes the feed's own URL rather than a root, because a comments feed is RSS 2.0
-and nothing else:
-
-```njk
-{{ feeds.commentsFeedLink("/comments/feed/", site.title + " comments") }}
-```
-
-`layouts/tag.njk`, `layouts/category.njk` and `layouts/author.njk` each call
-`feedLinks` over their own root, so an archive advertises its own three feeds
-as well as the site's — on an author archive that root is `author.url`.
-
-`layouts/base.njk` fills the `alternates` block with `feedLinks` over `/` and
-then the site's comments feed, so every page that extends it advertises all
-four. On a published post, and on a page that takes comments, it adds that
-document's own comments feed, from `commentsFeed` on the context. On a
-published post it also adds a link pointing at the post's ActivityPub object:
-
-```html
-<link
-  rel="alternate"
-  type="application/activity+json"
-  href="https://example.com/2026/09/hello/"
-/>
-```
-
-A post's object id is its permalink, so that link usually points at the page it
-is on: it says the URL answers ActivityStreams as well as HTML. A post migrated
-from elsewhere keeps the id its file names, and the link points there instead.
-It comes from `activityStreams`, which is only on the context of a rendered
-published post, as `commentsFeed` is only on a document that has a comments
-feed, so a layout that overrides the block and does not call `super()` has to
-emit both itself. They are on the context rather
-than in `post.njk` so that a site which overrides that layout, as the demo
-does, keeps them.
-
-After the block, and outside it, the base layout writes the webmention
-endpoint:
-
-```html
-<link rel="webmention" href="/_geekity/webmention" />
-```
-
-It comes from `webmention` on the context, which is on a rendered document only
-when the site is taking webmentions, so a theme asks `{% if webmention %}` and a
-site that has turned them off advertises nothing. The CMS also sends the same
-endpoint as a `Link` header on every representation of a document, so a sender
-that does not parse HTML still finds it.
-
-The pingback endpoint follows it, as an absolute URL because the spec asks for
-one:
-
-```html
-<link rel="pingback" href="https://example.com/_geekity/pingback" />
-```
-
-It comes from `pingback` on the context, which is there only when the site
-takes webmentions and the document can be answered: every post, and a page
-only while it takes comments. The same endpoint goes out in an `X-Pingback`
-header under the same rule.
-
-On the front page it also writes the site's index for language models:
-
-```html
-<link rel="describedby" type="text/markdown" href="/llms.txt" />
-```
-
-It comes from `llmsTxt` on the context, which is absent once the site turns the
-file off. The CMS sends the same link as a `Link` header on the front page.
-
-`layouts/tag.njk` and `layouts/category.njk` override that block, call `super()`
-and add the archive's own three feeds:
-
-```njk
-{% import "partials/feeds.njk" as feeds %}
-{% set tagRoot = "/" + (site.tagBase or "tag") + "/" + (tag | lower | urlencode) + "/" %}
-{% block alternates %}
-{{ super() }}
-{{ feeds.feedLinks(tagRoot, site.title + ": " + tag) }}
-{% endblock %}
-```
-
-A layout that does not extend the base one has to emit the links itself. The
-feeds are generated by the CMS, not by a template, so nothing here decides what
-goes in them.
-
-Category archives get their own three the same way.
-
-## The conversation
-
-`conversation` is what has been said about a post: the fediverse replies, likes
-and boosts its inbox was sent, the fediverse posts that quoted it with its
-author's approval, the comments people left on the page itself, and the
-webmentions other pages sent it.
-It is on the context of a rendered post **only when there is something in it**,
-so a post nobody has answered renders no empty section and a layout can simply
-ask:
-
-```njk
-{% if conversation %}
-{% include "partials/conversation.njk" %}
-{% endif %}
-```
-
-That is what `layouts/post.njk` does, and `layouts/page.njk` with it.
-
-A page takes part only while it takes comments: when its front matter says
-`comments: true` and the site has not switched comments off. A page is closed
-by default, as WordPress closes them, and the CMS leaves `conversation` off the
-context of a closed page however much has been approved against it, so a page
-that turns comments off shows nothing. A post is different: it keeps its thread
-after it closes. Webmentions to a page are received and moderated either way,
-exactly as webmentions to a post are, and appear once the page opens.
-
-`partials/conversation.njk` is the whole
-section — a `div.reactions-section` of the likes, the boosts and the mentions
-as facepiles grouped by kind, and then the thread as
-`div#comments.comments-area` — and a site replaces it with a
-`partials/conversation.njk` of its own in the theme it wears, exactly as it
-replaces any other template. It defines two macros, `face(item, icon, href)`
-and `group(items, label, kind, icon, source)`, and a layout that wants to place
-the pieces itself can import them:
-
-```njk
-{% import "partials/conversation.njk" as reactions with context %}
-{{ reactions.group(conversation.likes, "Likes", "p-like", "❤️") }}
-```
-
-One reply and everything under it is `comment(reply, classes)` in
-`partials/comment.njk`, which the thread and a comment's own page both import.
-`classes` is the reply's microformat: `h-entry`, the default, under a post, and
-`p-comment h-cite` on a comment's page, where the comment is the one entry.
-
-A reply post prints its replies inside its own `h-entry`, as `p-comment
-h-cite`s, so the page it answers finds them there when it is sent a salmention
-(TASK-320). `layouts/post.njk` includes `partials/conversation.njk` twice for
-one, setting `conversationPart`: `"replies"` inside the entry for the thread,
-and `"reactions"` below it for the facepiles, whose links are not the entry's.
-Left unset, the partial prints the whole section.
-
-### The shape
-
-The conversation is deliberately **not** spelled in ActivityPub's vocabulary.
-Native comments and webmentions land in the same thread, so every
-entry says where it came from and what it is, and nothing else about it changes
-with the source. A theme that never looks at `source` renders all of them
-correctly; one that does can style them apart. The one thing a theme does have
-to look at is `kind`: a `mention` is in `conversation.mentions` rather than in
-the thread, because it is not an answer.
-
-| Key                                                | What it holds                                                                                                           |
-| -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
-| `replies`                                          | The replies to the post, oldest first, each carrying its own `replies`. See below.                                      |
-| `likes`                                            | The likes, oldest first, in the same shape.                                                                             |
-| `boosts`                                           | The boosts, oldest first, in the same shape. A webmention `repost` is one of them.                                      |
-| `mentions`                                         | The pages and fediverse quotes about this post, oldest first, in the same shape.                                        |
-| `rsvps`                                            | An event's answers, each group `{ value, label, people }`, going, maybe, interested, not going, only with people in it. |
-| `counts.replies`                                   | How many replies, counted through the whole thread rather than the top of it.                                           |
-| `counts.likes`, `counts.boosts`, `counts.mentions` | How many of each.                                                                                                       |
-| `counts.rsvps`                                     | How many people answered an event, in every group.                                                                      |
-| `counts.total`                                     | All of them added up. Zero never reaches a template: there would be no `conversation` at all.                           |
-
-Each entry — a reply, a like or a boost — is:
-
-| Key               | What it holds                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `id`              | What it is called: a fediverse reply's note id, a reaction's activity id, a stored comment's key. It is what an answer to it names.                                                                                                                                                                                                                                                                                                                                                   |
-| `key`             | Its key (decision-51): 16 lowercase hex digits, the comment's id for one stored on the site and the key of its guid for anything else. Its anchor is `#comment-{key}` and its replies feed `/replies/{key}/`.                                                                                                                                                                                                                                                                         |
-| `guid`            | What the comments feeds call it: a native comment's `/comment/{key}/` page, a stored comment's origin (else its `url`), a fediverse note's id, a reply post's object id.                                                                                                                                                                                                                                                                                                              |
-| `migrated`        | `true` for a comment imported from the site this one replaced (decision-51). It shows like any other, but no feed carries it and no count a feed advertises includes it.                                                                                                                                                                                                                                                                                                              |
-| `source`          | `"activitypub"` for a fediverse reply, `"comment"` for one left on the page, `"webmention"` for another page linking here, `"post"` for a reply post a user of the site wrote (its `url` is the post's permalink).                                                                                                                                                                                                                                                                    |
-| `kind`            | `"reply"`, `"like"`, `"boost"`, `"repost"` or `"mention"`. A `repost` comes from a webmention; a `mention` is a webmention or an approved fediverse quote.                                                                                                                                                                                                                                                                                                                            |
-| `author.name`     | The best name available: their display name, else their handle, else their server, else their id. For a webmention, the source's `h-card` name, else its host.                                                                                                                                                                                                                                                                                                                        |
-| `author.handle`   | `@user@host`, or `null`. Taken from the follower or actor profile the site holds, else guessed from the actor URL unless it ends in a number. `null` for a native comment.                                                                                                                                                                                                                                                                                                            |
-| `author.url`      | Their profile page, the website a commenter typed, or a webmention author's `u-url`. May be `null`, so guard the link.                                                                                                                                                                                                                                                                                                                                                                |
-| `author.avatar`   | Their avatar, or `null`. The site knows one for a fediverse actor whose profile it holds or whose imported comment brought their icon, and for a webmention whose `h-card` carried a `u-photo`. Always a same-origin `/_geekity/avatars/…` path, never the remote URL: see [Avatars](#avatars).                                                                                                                                                                                       |
-| `author.actorId`  | Their id, which is what identifies them however they are named. `null` for a native comment, and for an imported one whose actor the export did not name.                                                                                                                                                                                                                                                                                                                             |
-| `author.username` | The site user they are, or `null`: whoever wrote a reply post, or the user a comment imported from the site this one replaced names (a WordPress comment written signed in). Such a comment's `author` is that user's, as a reply post's is: their display name, avatar and author archive.                                                                                                                                                                                           |
-| `url`             | Where it can be read: the remote note's `url` for a fediverse reply or quote, the source page for a webmention, and `/comment/{key}/`, its own page, for a native comment (see [A comment's own page](#a-comments-own-page)).                                                                                                                                                                                                                                                         |
-| `content`         | What it says, **already sanitised**, so print it with `\| safe`. Empty for a like or a boost.                                                                                                                                                                                                                                                                                                                                                                                         |
-| `published`       | A `Date`: when it was published, or when it arrived if it did not say. Use the `date` filter.                                                                                                                                                                                                                                                                                                                                                                                         |
-| `inReplyTo`       | What it answers — the post's ActivityPub id, or another reply's — and `null` for a reaction.                                                                                                                                                                                                                                                                                                                                                                                          |
-| `status`          | `"published"`. On the record for the sources that moderate.                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| `replies`         | The replies to this one, oldest first, nested as deep as the site has seen. One may be a placeholder: see below.                                                                                                                                                                                                                                                                                                                                                                      |
-| `rsvp`            | An RSVP: `{ value, label }`, its `p-rsvp` (`yes`, `no`, `maybe` or `interested`) and the words for it. Absent otherwise. A webmention reply that is an RSVP carries one, and the default theme prints it as a `data.p-rsvp` at the top of the comment's content. On an event, an RSVP is in `rsvps` rather than the thread, and so is a fediverse `Accept` (`yes`), `TentativeAccept` (`maybe`) or `Reject` (`no`) of the event. Each person is there once, with their latest answer. |
-
-Four rules decide what is in the thread, and they are the CMS's rather than a
-theme's: a reply whose author deleted it is gone, and its own answers move up to
-whatever it was answering; a comment a reader may not see (waiting for a
-moderator, spam or deleted) that has a visible reply under it is a placeholder,
-and one with none is not there at all; a like is counted once per actor,
-so an imported like and the same actor's like
-delivered here are one, and it disappears when that actor undoes it; and a note answering something this post
-has nothing to do with is left out.
-
-A fediverse reply or reaction imported from the site this one replaced is
-shown once, however often its server sends it again or the reply backfill
-reads it: the imported comment is the one in the thread, with the moderator's
-decision on it, and the answers to its note thread under it.
-
-A placeholder in `replies` is `{ id, withheld: true, replies }`: the hidden
-comment's id and the replies under it, and nothing that names its author or
-says what it said. Test `reply.withheld` before printing an author. A pending
-or spam comment's placeholder sits where the comment would; a deleted one's
-under the post, since nothing is known of what it answered. `counts.replies`
-and the comments feeds count and carry the visible replies only.
-
-`content` is safe to print whatever produced it, and safe for different reasons.
-A fediverse reply is HTML somebody else's server composed, rebuilt from an
-allowlist — `a`, `p`, `br`, lists, `blockquote`, `pre`, `code` and the inline
-emphasis tags, with every link carrying `rel="nofollow noopener noreferrer"`. A
-webmention's `e-content` goes through the same allowlist. A native comment is
-Markdown the commenter typed, rendered with raw HTML off, no images embedded,
-and every link carrying `rel="nofollow ugc"`. Nothing else survives any of the
-three routes, so a theme may print all of them directly.
-
-The packaged partial draws each entry as the source design does: an
-`li.comment.h-entry` carrying `id="comment-{{ reply.key }}"` and a
-`comment-{{ reply.source }}` class, holding an `article.comment-body` whose
-`footer.comment-meta` is the author as a `.comment-author.vcard.p-author.h-card`
-(their avatar, or the first letter of their name in a `span.comment-avatar-empty`
-when there is none, and their link marked `rel="nofollow ugc"` unless `author.username` says the
-author is a user of the site, as a reply post's author is) and the permalink as a `.comment-metadata` link around a
-`time.dt-published`, with a `span.comment-source` saying "via webmention" or
-"via the fediverse" when it came that way, then the words in
-`div.comment-content.e-content`. Answers nest in an
-`ol.children` inside what they answer. A Reply link in a `div.reply` goes on the
-ones written here — `source == "comment"` — when the post is still open; it
-carries the comment's key to the form as `?reply_to=`, so threading needs no
-JavaScript. A fediverse reply is answered on the server that holds it and a
-webmention on the page that sent it, so neither gets one. A placeholder is an
-`li.comment.comment-placeholder` with the hidden comment's anchor, a
-`p.comment-withheld` printing `withheld()` ("This comment is no longer
-shown."), and its replies in an `ol.children`; it is no microformat of its own.
-
-Above the thread, `group()` draws one `div.reaction-group` per kind that has
-anything — `p-like`, `p-repost` and `p-mention`, the source theme's classes — as
-an `h2.reaction-title` of the label and the count, in a `span.reaction-count`,
-beside a `div.facepile` of
-`a.u-url` faces. A face is a round `u-photo` avatar; a reaction whose author the
-site knows no picture of is the emoji badge of its kind and a `.reaction-name`
-instead. Likes and boosts link to the person, and a mention to the page it came
-from, because the page is the thing worth reading.
-
-There is no key saying a post has stopped taking comments, and none is needed:
-**the absence of `commentForm` is what a closed post looks like**, since the CMS
-puts the form on the context only while the site switch, the closing window and
-the post's own front matter all agree it is open. The packaged partial prints
-`p.no-comments` under a thread when there is no form, which is WordPress's
-"Comments are closed." and the reason a reader cannot find one.
-
-An Eleventy build of the same content gets the same thing from the same files:
-`docs/eleventy.config.example.js` adds a `conversation` filter over
-`federation.inbox`, and puts the post's ActivityPub id on the context as
-`activityStreams` and its slug as `geekitySlug`, so a layout reads
-
-```njk
-{% set conversation = federation.inbox | conversation(activityStreams, geekitySlug) %}
-```
-
-and then loops over exactly the keys above. The slug is what names the post's
-comment file under `content/_data/comments/`; the format is documented in
-backlog doc-6. Two things differ: a native comment's `url` is its
-`#comment-{key}` anchor, because a static build writes no comment pages, and
-the site's own reply posts (`source: "post"`) are not in the thread.
-
-### A comment's own page
-
-A comment left through the form has a page of its own at `/comment/{key}/`,
-which is its `url` everywhere: the thread's permalink, the comments feeds and
-what another site fetches when it replies to the comment. The anchor
-`#comment-{key}` on the post stays, so an old link still scrolls to it. A
-webmention and a fediverse reply have no such page: their `url` is where they
-came from.
-
-`layouts/comment.njk` draws it, with the comment as the page's one `h-entry`.
-It answers only while the post shows its conversation, and is `noindex` and on
-no list: not the sitemap, the post feeds or search. Its context:
-
-| Key         | What it holds                                                                                                                                                                                 |
-| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `comment`   | The comment, an entry of the shape above, its `replies` nested at every depth by the thread's own rules.                                                                                      |
-| `ancestors` | What it answers, from the top-level comment down to its parent. An ancestor a reader may not see (waiting for a moderator, spam, deleted, withdrawn) is `null`, so the chain keeps its place. |
-| `post`      | The post it is on, as a listing entry is: `label`, `url`, `date`, `summary`, `author` and the rest.                                                                                           |
-| `threadUrl` | The comment's anchor on the post, for a link back to the whole conversation.                                                                                                                  |
-
-The packaged layout prints the chain above the comment as nested
-`u-in-reply-to h-cite`s: the comment cites its parent, which cites its own,
-down to the post, which is printed first, so a parser and a reader meet the
-thread in the same order. A `null` ancestor is a cite with no author and no
-words, printing the same `withheld()` the thread's placeholder does. The replies follow inside the
-entry as `comment(reply, "p-comment h-cite")`, with no Reply links, and a
-link to `threadUrl` ends the page.
-
-### Avatars
-
-A reader's browser never fetches a face from the server it lives on. The
-`author.avatar` a theme is handed is a path on this site, under
-`/_geekity/avatars/`, and the CMS fetches the picture, crops it to an
-80-pixel square WebP (twice the 40 pixels this theme shows a commenter at)
-and keeps it under `data/avatars/`. Print it as it is; it needs no filter.
-
-The route serves only the pictures the site shows: a follower who has
-liked, boosted, quoted or answered a post, and the author of an approved
-comment or webmention. Any other URL is a 404, and nothing is fetched for it.
-Pictures are fetched in the background when the site starts and every six
-hours after, refreshed once they are a week old, and forgotten once nothing
-shows them. A picture that cannot be fetched, is over 2 MB, or is not a JPEG,
-PNG, GIF, WebP or AVIF is served as a grey placeholder, and tried again an
-hour later. `data/avatars/` is a cache: delete it and every picture is fetched
-again.
-
-## The comment form
-
-`commentForm` is on the context of a rendered post **only when that post is
-still taking comments**. A site switch, a closing window counted from the
-post's date, and `comments: true` or `comments: false` in the post's own front
-matter all agree before it gets here, so a layout asks:
-
-```njk
-{% if commentForm %}
-{% include "partials/comment-form.njk" %}
-{% endif %}
-```
-
-That is what `layouts/post.njk` does, after the conversation. A closed post
-still shows the thread — including every fediverse reply, which arrives whether
-a post is open or not — and simply has no form, which is what the conversation
-reads to print "Comments are closed." A site replaces
-`partials/comment-form.njk` the way it replaces any other template.
-
-The packaged partial is a `section#respond.comment-respond` with an
-`h2.comment-reply-title`, one paragraph per field and the button in a
-`p.form-submit` — the source design's names, so the stylesheet styles every
-label, field and button of both forms through `.comment-respond` and a site
-that has CSS for the WordPress theme can bring it. The name and email fields sit
-in a `div.field-row`, side by side on a wide screen, in both forms. On a site
-that takes webmentions a `p.comment-help` under the heading says a reader can
-reply from their own site instead.
-
-| Key                        | What it holds                                                                                                                                                                      |
-| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `action`                   | Where the form posts. One fixed path; the post travels as a field.                                                                                                                 |
-| `fields`                   | The name each field is submitted under: `post`, `name`, `email`, `url`, `body`, `inReplyTo`, `trap`, `loaded`, `notify`, `csrf`, `listed`. Use these rather than typing the names. |
-| `post`                     | The post's slug, for the hidden field.                                                                                                                                             |
-| `loaded`                   | When this form was rendered, in epoch milliseconds, for the hidden field. A submission that comes back too fast is refused.                                                        |
-| `values`                   | What is in the fields: empty on a fresh form, what was typed on a refused one.                                                                                                     |
-| `problems`                 | One message per field a person has to put right — `name`, `email`, `url`, `body`.                                                                                                  |
-| `error`                    | A message about the submission as a whole, when there is one.                                                                                                                      |
-| `notifiable`               | Whether to offer `fields.notify`, the "email me when somebody replies" box. False on a site that sends no mail, where the box would promise a message nothing could send.          |
-| `nameLength`, `bodyLength` | The `maxlength` for the two fields that have one.                                                                                                                                  |
-
-`fields.trap` is a honeypot: render it, hide it from sight and from assistive
-technology, and give it `tabindex="-1"` and `autocomplete="off"`. A submission
-that filled it is dropped. **Do not** remove it from a replacement partial —
-it is one of three things standing between the site and a spam queue.
-
-### When a submission is refused
-
-The CMS answers a refused comment with the post again, `problems` and `error`
-filled in. The packaged partial tells assistive technology about it in two
-places, and a replacement partial should do the same:
-
-- **A summary before the form.** One element with `role="alert"`,
-  `tabindex="-1"` and `autofocus`, labelled by a heading that is `error`, or a
-  sentence of your own when there is none, and holding a link to each field in
-  `problems` (`<a href="#comment-name">…</a>`). `autofocus` moves focus to it on
-  load with no script, so it has to be the first `autofocus` on the page.
-- **On each field in `problems`.** `aria-invalid="true"` and
-  `aria-describedby` naming the element that holds its message, so a screen
-  reader reads the message with the field.
-
-The contact form below keeps the same contract.
-
-### When somebody is signed in
-
-Two more keys are on `commentForm` when — and only when — the request carries a
-valid session for this site's admin:
-
-| Key          | What it holds                                                                                                                     |
-| ------------ | --------------------------------------------------------------------------------------------------------------------------------- |
-| `signedInAs` | Who the reply will be posted as: `name`, which is their display name or their username, and `url`, which is their author archive. |
-| `csrfToken`  | The value for a hidden `fields.csrf`, without which the submission is refused.                                                    |
-
-**A replacement partial has to draw both forms**, because the site draws this
-one for its own author and the stranger's one for everybody else:
-
-```njk
-{% if commentForm.signedInAs %}
-<input type="hidden" name="{{ commentForm.fields.csrf }}" value="{{ commentForm.csrfToken }}" />
-<p class="comment-signed-in">
-  Commenting as <a href="{{ commentForm.signedInAs.url }}">{{ commentForm.signedInAs.name }}</a>.
-</p>
-<p class="comment-check">
-  <input id="comment-listed" name="{{ commentForm.fields.listed }}" type="checkbox" value="1"{% if commentForm.values.listed %} checked{% endif %} />
-  <label for="comment-listed">Include in posts and feeds</label>
-</p>
-{% else %}
-{# fields.loaded, fields.trap, and the name, email and website boxes #}
-{% endif %}
-```
-
-The signed-in branch renders **no** name, email or website box, **no**
-`fields.trap` and **no** `fields.loaded`: the site already knows all three
-answers, and a session is better evidence that this is a person than a honeypot
-or a stopwatch. It renders `fields.csrf` instead, because this is the one form
-on the public site that acts on somebody's behalf — without the token, a page
-on another site could make them post under their own name. The comment box, the
-reply-to field and the notify box are the same in both branches.
-
-What the signed-in branch posts is a reply post rather than a comment (CMS
-README, "Replying while signed in"). It adds `fields.listed`, a checkbox
-labelled "Include in posts and feeds" and unchecked by default: unchecked
-publishes the reply post unlisted, checked publishes it public. The stranger's
-branch never draws it, and the CMS ignores it from a stranger.
-
-A Reply link, `?reply_to={key}#respond`, goes on every entry of the thread for
-somebody signed in, and on `source == "comment"` entries only for a stranger.
-`partials/comment.njk` asks `reply.source == "comment" or
-commentForm.signedInAs`.
-
-The account's email address is **never** on the context. The comment is stored
-with it, exactly as a stranger's is, and it is no more printable than theirs.
-
-A page carrying this form is one reader's page rather than the post, so the CMS
-answers it `Cache-Control: private, no-store` and with no ETag. A theme does
-not have to do anything about that, but it is why printing somebody's name into
-a page is safe here.
-
-Two more keys travel beside it, both from the URL rather than from the post:
-
-| Key                                   | What it holds                                                                                                                   |
-| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
-| `commentNotice`                       | The thank-you after a submission, from the `?comment=` the redirect carried.                                                    |
-| `commentReplyTo`, `commentReplyingTo` | The comment a `?reply_to=` link named and the name on it, once the CMS has checked it is an approved comment on this very post. |
-
-## The contact form
-
-`contactForm` is on the context of a rendered document **only when its front
-matter says `contact: true`**, so a layout asks:
-
-```njk
-{% if contactForm %}
-{% include "partials/contact-form.njk" %}
-{% endif %}
-```
-
-That is what `layouts/page.njk` does, after the page's content. The key is
-honoured wherever it is written, so a theme that wants the form under a post as
-well only has to add the same two lines to `layouts/post.njk`; the editor
-offers the checkbox on pages.
-
-`archive: true` is the other front matter key of this kind: it puts every
-published post on the page instead of a form. See
-[An archive page](#an-archive-page).
-
-The packaged partial is a `section#contact.comment-respond.contact-form`: it is
-the same kind of form as the comment one, so it wears the same class and the two
-share one set of rules rather than keeping two that drift.
-
-| Key                                            | What it holds                                                                                                                                    |
-| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `action`                                       | Where the form posts. One fixed path; the page travels as a field.                                                                               |
-| `fields`                                       | The name each field is submitted under: `page`, `name`, `email`, `subject`, `message`, `trap`, `loaded`. Use these rather than typing the names. |
-| `page`                                         | The page's slug, for the hidden field.                                                                                                           |
-| `loaded`                                       | When this form was rendered, in epoch milliseconds, for the hidden field. A submission that comes back too fast is refused.                      |
-| `values`                                       | What is in the fields: empty on a fresh form, what was typed on a refused one.                                                                   |
-| `problems`                                     | One message per field a person has to put right — `name`, `email`, `subject`, `message`.                                                         |
-| `error`                                        | A message about the submission as a whole, when there is one.                                                                                    |
-| `nameLength`, `subjectLength`, `messageLength` | The `maxlength` for the three fields that have one.                                                                                              |
-
-`fields.trap` is the same honeypot the comment form carries, and the same rules
-apply: render it, hide it, and **do not** remove it from a replacement partial.
-
-One more key travels beside it, from the URL rather than from the page:
-
-| Key             | What it holds                                                                                                                            |
-| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
-| `contactNotice` | The thank-you after a message was sent, from the `?contact=` the redirect carried. The shipped partial shows it **instead of** the form. |
-
-**Where the message goes is never on the context.** The contact address is read
-when a submission arrives, so it cannot end up in the HTML however this partial
-is rewritten. Do not try to print it, and do not put a `mailto:` beside the
-form.
-
-## Taxonomy macros
-
-`partials/tags.njk` holds one macro per taxonomy, and each renders nothing at
-all for an empty list. Both are one `p.post-categories` of `p-category` links,
-which is the shape the design prints in a feed item's meta line and under an
-entry — `categories` marks each link `rel="category"` and `list` marks each
-`rel="tag"`, so under an entry the two read as one line of what it is filed
-under, categories first:
-
-```njk
-{% import "partials/tags.njk" as taxonomy with context %}
-{{ taxonomy.categories(categories) }}
-{{ taxonomy.list(tags) }}
-```
-
-`list` links to `/{{ site.tagBase }}/{tag}/`, the tag in lower case, and `categories` to
-`/{{ site.categoryBase }}/{category}/`, which is where the CMS serves each
-archive. Both bases are settings — `tag` and `category` until the settings
-screen says otherwise — and they reach a template through `site`, which is why
-the import above carries `with context`: a macro imported without it cannot see
-`site` and would fall back to the defaults.
-
-## Filters
-
-| Filter                       | What it does                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `date(format, zone, locale)` | Formats a `Date` or a date string. `long` gives `2 September 2026` on an `en` site and `2 septembre 2026` on an `fr` one; `full`, `medium` and `short` are Intl's other date styles, and `readable` (the default) is `long`. `datetime` gives `10 October 2026 at 09:00 GMT-5`, the day and the time with the zone named. `month` gives `September 2026`, `year` gives `2026`, `html` gives `2026-09-02` for a `<time datetime>`, and `iso` gives the full ISO 8601 instant. Every format but `html` and `iso` is written in the site's locale: the `locale` setting, or the `language` when that is empty. Bare `en` writes the day first, as `en-GB` does; `en-US` gives `September 2, 2026`. A date in a file is a UTC instant; every format but `iso` is rendered in the site's `timezone` setting, and `iso` stays the instant. Pass `zone` — an IANA name — to override the setting for one call. Pass `locale` — a BCP 47 tag — to write the words in another language for one call; it comes after `zone`, so pass `none` for the zone to keep the site's: `{{ date \| date("readable", none, lang) }}`. An empty locale, or one that is no tag, writes in the site's. A value that is not a date renders as the empty string. |
-| `plural(forms, locale)`      | Picks the form for a count by its plural category in the site's locale, through `Intl.PluralRules`: `{{ n \| plural({ one: "# reply", other: "# replies" }) }}`. The keys are the CLDR categories (`zero`, `one`, `two`, `few`, `many`, `other`), a category the forms leave out falls back to `other`, and `#` is the count in the locale's digits. Pass `locale` when the strings are in a language of their own: the default theme's words are English, so it passes `"en"`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| `url`                        | Prefixes a root-relative path with the base URL's path, so a site served from a subdirectory links correctly. Eleventy's filter of the same name.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| `absoluteUrl`                | The same path as a fully qualified URL against the site's `baseUrl`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| `asset`                      | The URL of a file in the theme's `static/` directory, with the base path in front and a hash of the file's bytes on the end: `{{ "style.css" \| asset }}` gives `/theme/style.css?v=3f2a9c01b7d4`. The file is found the way `/theme/` finds it, the chosen theme first. A hashed URL is served with `Cache-Control: public, max-age=31536000, immutable`, and editing the file changes the hash on the next render. A file no theme has gets its plain `/theme/` URL.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-
-`date` reads one word rather than parsing it: `{{ "now" | date("year") }}` is
-the year at the moment the page is rendered, in the site's own timezone. It is
-what the footer's copyright line is written with, and it is the one date a page
-has that no file carries.
-
-The default theme passes the document's `lang` as that locale for every date
-inside its `<article>`: the Published and Updated lines, the hidden heading of
-a note, the kicker in a listing or a search result (`kicker.line(…,
-lang=post.lang)`), and the date of the post a reply answers. So a post that
-says `lang: fr` on an `en` site reads `Published 2 septembre 2026`, while the
-navigation, the conversation under it, the archive's month headings and the
-footer stay in the site's locale. A theme that wants the same passes `lang`
-on an entry and `post.lang` in a listing; one that passes nothing writes every
-date in the site's locale, as before.
-
-Nunjucks' own filters — `default`, `join`, `urlencode`, `safe` and the rest —
-are all available. Autoescaping is on, so rendered Markdown is the one thing
-that has to be passed through `safe`.
+The templates and the stylesheet that every Geekity CMS site gets, shipped
+inside `@geekity/cms`. A site theme can replace one template at a time. The
+rest come from this theme.
+
+## Override a template
+
+```sh
+mkdir -p themes/mine/layouts
+echo '{ "name": "Mine", "kind": "site" }' > themes/mine/theme.json
+cp node_modules/@geekity/cms/themes/default/layouts/post.njk themes/mine/layouts/
+```
+
+Edit the copy, then choose **Mine** on **Appearance > Themes** in the admin.
+Every template that your theme does not ship still comes from the default
+theme.
+
+## Documentation
+
+[The default theme](https://github.com/geekitycom/cms/blob/main/docs/theme/README.md)
+lists every file in this folder. Each topic has a page of its own:
+
+- [The manifest](https://github.com/geekitycom/cms/blob/main/docs/theme/manifest.md)
+- [Overriding a template](https://github.com/geekitycom/cms/blob/main/docs/theme/overriding-a-template.md)
+- [Adding to every page](https://github.com/geekitycom/cms/blob/main/docs/theme/adding-to-every-page.md)
+- [The page shell](https://github.com/geekitycom/cms/blob/main/docs/theme/page-shell.md)
+- [Mail templates](https://github.com/geekitycom/cms/blob/main/docs/theme/mail-templates.md)
+- [The Markdown representation](https://github.com/geekitycom/cms/blob/main/docs/theme/markdown.md)
+- [Template context](https://github.com/geekitycom/cms/blob/main/docs/theme/template-context.md)
+- [Bylines and author archives](https://github.com/geekitycom/cms/blob/main/docs/theme/bylines.md)
+- [Navigation](https://github.com/geekitycom/cms/blob/main/docs/theme/navigation.md)
+- [Feeds](https://github.com/geekitycom/cms/blob/main/docs/theme/feeds.md)
+- [The conversation](https://github.com/geekitycom/cms/blob/main/docs/theme/conversation.md)
+- [The comment form](https://github.com/geekitycom/cms/blob/main/docs/theme/comment-form.md)
+- [The contact form](https://github.com/geekitycom/cms/blob/main/docs/theme/contact-form.md)
+- [Taxonomy macros](https://github.com/geekitycom/cms/blob/main/docs/theme/taxonomy-macros.md)
+- [Filters](https://github.com/geekitycom/cms/blob/main/docs/theme/filters.md)