{#- The rietx brand: furo's own `sidebar/brand.html`, with the link pointed at the landing page (WP-1411). Forked rather than configured because furo's brand link is written `href="{{ pathto(master_doc) }}"` in the shipped template, and `theme.conf` offers no option that reaches it — `light_logo`, `dark_logo`, `sidebar_hide_name`, `announcement`, `footer_icons` and the `source_*` keys are the whole list. Overriding the template through `templates_path` is what furo documents for this (https://pradyunsg.me/furo/customisation/sidebar/), and the shipped file points at that page itself. Since WP-1331 the manual is `/manual.html` and the landing page is `/`, so furo's default sends "home" to the page the reader is already in. Nothing in `docs/manual/` linked to the site root before this. Three things here are not furo's: * `rietx_home` is `rietx._about.DOCS_URL`, handed over in `conf.py`'s `html_context`. The URL is never spelled in this tree outside `_about` (root CLAUDE.md § Conventions). * The mark is inline SVG taking its `fill` from a CSS variable, not an ``. An ``-embedded SVG is its own document and cannot see `body[data-theme]`, so `_static/favicon.svg` — which carries its own `prefers-color-scheme` block — would answer the *system* theme and ignore the toggle. That is the failure the committed figure pairs exist to avoid, one element down. Wearing that same file as a CSS `mask-image` fixes the colour and was tried first, since `custom.css` already draws the agent admonition's icon that way. It was measured to fail on a **local** build: chromium treats a `file://` mask source as cross-origin and drops it silently, so the mark vanished for anyone opening `_build/html/` directly while rendering correctly over http. Inline is the cost of not having that trap. So these three paths are a copy of the favicon's, and `tests/test_manual.py` pins them equal — the geometry has one authority, and it is the file. * The wordmark is text, because a webfont loaded by the page does not reach inside an ``-embedded SVG. The landing page's `.brand` is built the same way, an inline mark beside the word. The word itself is `rietx_name`, `_about.DIST_NAME` handed over the same way `rietx_home` is: a hardcoded spelling of the brand here would be invisible to every test in the suite (`_about.py`'s docstring), so the rule is all that catches it. The release line is a second, sibling anchor, and it is the way back to the manual's own front page. The two lines then name their own destinations: the wordmark is the project, ` · manual` is `manual.html`. Before this the brand was one link to the landing page and a reader inside a chapter had no way back to the manual's front page at all, since `root_doc` is in no toctree and furo's sidebar therefore never lists it. Sibling rather than nested because HTML has no nested ``, and the outer href is what `tests/test_manual.py` pins on every page. `release` is Sphinx's own context variable, so the version line quotes the live version rather than a typed one. `docstitle` is deliberately not rendered: it reads "rietx 1.4.0 — manual" and would repeat the wordmark. `tests/test_manual.py` asserts the href on every built page, because a furo upgrade that reshapes this template would drop the link with a green build. -#}