← Docs hub

UI reference

Every screen on the compiled site (llmwiki build → site/), what it shows, and how to reach it. The site is plain files — open site/index.html in a browser, or publish site/ to any static host.


Top navigation

Every page in the site carries the same header nav. Keyboard: ⌘K opens the command palette from any page.

# Label URL Surfaces
1 Home /index.html alerts + Metrics + pipeline table + ops timestamps + recent raw docs + collapsible Automation/backlog/commands
2 Raw /raw.html Documents sidebar (logical docs + quick filter) + unified reader for raw/docs/
— Candidates /candidates.html what is pending under wiki/candidates/, a per-row Decision control, and an Apply that assembles the candidates apply command + JSON batch for the rows you decided
3 Graph /graph.html interactive force-directed knowledge graph (vis-network)
— Topics /topics/index.html every topic grouped into curated entities, curated concepts and derived topics, counted per section and ordered by reach within each
4 Projects /projects/index.html filterable card grid of every project + freshness badge
5 Sessions /sessions/index.html sortable table of every session, agent badge, project, model, tool-call count
6 Analytics /analytics.html activity heatmaps, wiki usage, recent activity, project grid
7 Models /models/index.html structured model-profile cards (provider, pricing, benchmarks)
8 Docs /docs/index.html editorial docs hub — tutorials, references, deployment guides
9 Prototypes /prototypes/index.html review-ready UI states (page-shell, article-anatomy, …) for UX iteration
— Search ⌘K command palette — wiki-page matches and site pages, in two groups
— Theme toggle button on the right light / dark (persists via localStorage.theme)

Mobile: the six middle links collapse into a bottom-nav below 768 px; Search + Theme stay in the top bar.


Home

URL: /index.html

Queue-first landing page. Layout:

  1. Problems banner — one red banner (#llmwiki-problems, role="alert") at the top of Home alerts when anything needs attention (#374): schedule overdue, setup outdated, last sync/synth/build/run failure, and lint errors (same [error] gate as before). Hidden when clean; re-checked every minute while the page is open. Entries use outcomes in llmwiki-state.json (updated on full pipeline runs; browser refresh picks up changes without rebuild).
  2. Metrics — four cards in order: Tokens, Last 7 days avg (s/day, sub-line t/day · t/s), Knowledge (hint includes stale count when > 0), Payoff / page; title links to Analytics.
  3. Pipeline state — Eligible sources table (#llmwiki-state-widget): column widths 23% / 17% / 14% / 17% / 14% / 17%; Queryable / In site with floating i hints; Other row In site = Total HTML minus summed attributed rows; Last sync, Last synth, Last build in the Total footer. Operations list (Oldest pending, Last queue run, Synth estimate updated). Recent raw documents, then collapse sections: Automation (Maintain refreshes the site once after summarization), not-synthesized sessions/docs, Commands, estimate warnings, Linter output (full report from ops.last_lint_report after any lint run).
  4. Recent raw documents — newest raw/docs/ entries with title + inline source meta (compact rows).

Numbers come from llmwiki-state.js (synth.pipeline + synth.pending + synth.estimate + ops.*), refreshed by llmwiki sync / llmwiki synth --estimate / successful synth and build stamps / lint (JSON + site data sidecar only — lint does not rewrite HTML). Every llmwiki build also recounts pending/stale candidates into synth.pipeline.to_review* (cheap disk walk — #84). The Knowledge metrics card shows topic-graph Entities · Concepts · Other (Topics index parity). Pending review count and a short stale note render as the first line under the Pipeline state table (link → Candidates page). Pipeline snapshot still carries trusted_entities / trusted_concepts file counts for operators who need disk totals. llmwiki build still one-shot backfills synth.pipeline rows when the state snapshot predates that key (v1.4→v1.5 upgrade — #70). The session-analytics content (heatmap, stats, project grid) lives on Analytics.


Raw

URL: /raw.html (document pages under /documents/…)

Browsable surface for everything under raw/docs/ (wiki-add / imported documents). The Documents sidebar mounts on Raw, on Home when it shows documents, and on each document page — one shared tree from documents-tree.js, not a per-page rebuild.

Logical documents. Within each folder, files that share a base slug (runbook.md or runbook-01.md … runbook-NN.md) are one document. The sidebar lists each once under a cleaned readable title (no (part i/N…) suffix). Folder nesting stays — project folders from llmwiki add --project and per-document folders alike — but a project folder is only a container: two different base slugs under the same folder stay two entries, not one merged page.

Unified reader. Opening a sidebar or search hit lands on one canonical HTML page that assembles every part in order, with in-page #part-NN section anchors and without repeated part-title / breadcrumb chrome. Single-file docs still render as one complete page. Old bookmarks to a per-part path (…/<slug>-02.html) keep working as stub pages that redirect to the unified URL at the matching section.

Quick filter. The sidebar has a filter input above the tree. Matching is case-insensitive: titles that start with the query appear first, then titles that only contain it; every ancestor folder of a match stays visible so place-in-folder stays clear; non-matching sibling branches hide. Matching substrings in document labels are highlighted; when nothing matches, the empty copy is No documents match. Titles and “one document vs many parts” agree with Ctrl+K’s type:document hits — both surfaces serialize the same build-time logical-document catalog (see reader-api.md).

The site is only static files under site/ — there is no separate hosted reader HTTP API. Opening those files from disk (file://…/site/raw.html) or via any local static file server behaves the same for Documents + Ctrl+K because the tree and search payloads also ship as .js sidecars (documents-tree.js, search-index.js); browsers block fetch() of sibling .json from file://, so the pages load window.llmwikiData[…] from the sidecars instead.


Candidates

URL: /candidates.html

The review gate for pending stubs under wiki/candidates/ (#97). Two tables — Entities (pending) and Concepts (pending) — each with Name (title, slug and age), Description, and Decision.

Name shows the title once, then a muted age line (slug · age only when the slug differs from the title). When the pending name near-matches one or more previously discarded subjects (#146), a muted Prior dismissals: list follows — each item "<DismissedName>" — <reason>. An empty recorded reason shows as (discarded without explanation). Rows llmwiki remove recorded for pages it archived (reason archived by remove: last citing source removed) can surface here too, next to reviewer-written reasons. The list is computed at build time from wiki/archive/candidates/dismissals.json (same near-match rule as candidates list); the browser does not re-match. Merges are not treated as dismissals for this list.

Decision is a per-row select: Promote, Flip and promote, Merge into…, Discard, and — when the row has prior dismissals — Discard with prior reason (reuses the best match’s reason without retyping; still maps to a normal discard in the apply batch). Merge into… and Discard reveal the field that action needs; Discard with prior reason only reveals the optional redirect field. Every row starts at No decision and stays there until you choose — deciding is browser state, so nothing runs and nothing is sent.

Apply sits in a bar above the tables that stays pinned under the site nav while you scroll, so it is in reach from any row. It assembles the rows you decided — and only those — into the command to run and the JSON batch to pipe into it, shown directly below the bar with Copy command and Copy JSON:

llmwiki candidates apply --vault <vault> --actions -

Merge into… reveals a filterable dropdown of every page merge --into resolves for that table — the trusted pages under wiki/<kind>/ first, then the same-table pending stubs. Press the ▾ button or ↓ to browse the whole list without typing, type any part of a name to narrow it (case-insensitive substring), ↑ / ↓ to move, Enter to choose, Esc to close. The list is the closed set of valid targets: text naming no page is marked as you type, and a row holding one is named on the page instead of going into a batch that would fail at the CLI.

Discard reveals a required reason. That reason is stored in wiki/archive/candidates/dismissals.json with the archived stub (new discards do not write a sibling *.reason.txt), so a blank one throws the decision away — a row set to Discard with no reason is held back the same way an unresolved merge target is. Beside it, an optional Redirect links to field names an existing page: filled, the batch row carries redirect and links to the discarded name point at that page; left empty, they become plain text. redirect belongs to a discard, so a batch row carrying it on any other decision is refused before any row runs, and a redirect whose name another live page already answers to fails that row by name instead of quietly recording a second claim on it.

A row left at No decision is absent from the batch and stays pending, so a half-finished review can be applied and resumed. Apply refuses an empty batch; when a decided row is not yet executable it names the row, marks the field and moves focus to it, and emits nothing until you finish it. llmwiki candidates apply rebuilds site/ after a successful batch, so reload the page (or reopen the file) to see the remaining queue. Pass --no-rebuild if you are applying several batches and will llmwiki build once at the end. One-off CLI actions and /wiki-candidates do the same wiki work; only apply rebuilds.

Action Effect
promote Move into trusted wiki/entities/ or wiki/concepts/; status: reviewed
flip-promote Wrong kind → promote into the opposite trusted folder and rewrite type: (do not hand-mv stubs between candidate folders)
discard Archive under wiki/archive/candidates/; links to it become plain text, or point at the Redirect links to page
merge Fold into another page of the same kind, then archive the stub

Projects index

URL: /projects/index.html

Grid view of every project. Each card shows:

Clicking a card navigates to /projects/<slug>.html — the project detail page.

Project detail (/projects/<slug>.html)


Sessions index

URL: /sessions/index.html

Sortable table across every project. Default sort: date desc.

Columns: Session · Agent · Project · Date · Cwd · Model · Msgs · Tools.

Filter bar at top: Project · Agent · Model · date range · slug substring (Clear resets; selections persist in sessionStorage for the tab).

Activity timeline above the filter bar — SVG sparkline of sessions/day across the calendar span. Hover, focus, or click a bar to show that day's date and count in the label (native tooltip too).

Clicking a row navigates to /sessions/<project>/<slug>.html.

Session detail (/sessions/<project>/<slug>.html)


Models

URL: /models/index.html

Structured info cards for each AI model (per llmwiki/schema.py :: ModelProfile):


Graph

URL: /graph.html

Interactive force-directed knowledge graph. Details in reference/reader-api.md under the graph section.

What works:

Node colours. One colour per kind, at equal saturation — a topic no wiki page describes is a normal citizen of the map, not a faded placeholder. The legend renders one swatch per kind actually present in the graph, so a vault with no syntheses advertises no synthesis swatch.

Kind Colour
Sources violet #7c3aed
Entities blue #2563eb
Concepts green #059669
Syntheses amber #d97706
Projects magenta #db2777
Other (no wiki page describes the topic) lime #65a30d

Red is deliberately not a kind colour: the map already spends it on two states — the orphan border and a live search match — and a kind sharing it would read as an error.

Side panel (topic mode, single click) — topic name, Sessions, Connected topics, then the same identity facts the topic page carries: Kind, Active, Reviewed. Kind always renders, reading Unclassified topic when no wiki page describes the node; the two date rows are omitted when the node lacks the field, so a topic with no dates shows the counts and the kind rather than empty rows. Open page → follows, then the top connections and the bridging sessions.

Built-in assets: every graph.html ships with sibling graph-viewer.js and vis-network.min.js (pinned 9.1.9, vendored at build time and included in the installed package). The canvas works from the built static site over HTTP, file://, or fully offline — no unpkg fetch and no manual host step for vis-network. Offline fallback: if either companion script is missing or fails to load, the page shows an inline notice (#offline-notice) via script-tag onerror, a post-load watchdog when graph-viewer.js never runs, and a typeof vis check inside the viewer when the library alone is missing — not a blank canvas.


Topic pages

URLs: /topics/<slug>.html, /topics/index.html

Two things make a topic. A name sessions cited: a [[wikilink]] target found in wiki/sources/*.md, with spelling variants clustered into one canonical name. Or — since #248 — a curated page that describes one: every page under wiki/entities/ and wiki/concepts/ becomes a topic whether or not any session cites it, so promoting a candidate always produces something a reader can open. A topic is therefore not the same thing as a wiki page in either direction: a derived topic renders whether or not any page under wiki/ describes it — an un-promoted candidate, or a name a reviewer declined, keeps its page indefinitely — while every curated entity and concept gets one regardless of reach. Two page sets stay out: wiki/archive/ (cold storage is never published) and _-prefixed folder-context stubs such as wiki/entities/_context.md, which exist only to orient an assistant.

One topic gets no page: the one with nothing to show. A topic is skipped when it has no connected topics and no content of its own — no edge in the co-occurrence graph, and nothing left of its backing page once the title, ## Connections, ## Sessions and ## Sources are removed (a topic no page backs has no content of its own either). The page would carry a name, No connected topics. and an empty evidence list, which helps neither a reader nor an agent. Both halves are required: a reviewed page nobody co-cites still shows what it records, and a page recording nothing still shows the neighbourhood it sits in. The skip is computed once, over the node list the whole build reads, so a skipped topic has no page, no ⌘K entry, no row or count on /topics/index.html, and no node in the graph — and its wiki page stays searchable in the Wiki result group with no link on the row (its corpus url is null), because the assistant still reads it. Reach topics by double-clicking a node in the Graph, from ⌘K (type:topic), from the Topics nav entry, or from the Connected topics list on any other topic or project page.

/topics/index.html lists every topic in three sections, in this order — Entities, Concepts, Other topics — each heading carrying that section's count. Rows keep today's reach ordering (session count, then link count) within each section, and a curated row carries the same kind chip the topic page's identity line shows, so a reviewed page is distinguishable from a name sessions happened to mention. An empty section renders its heading and No topics in this group. rather than disappearing. There are no filter or sort controls.

Three numbers are easy to conflate here. They gate different things, and only the first is configurable per vault:

Constant Value Gates Per-vault?
DEFAULT_MIN_REFS (llmwiki/vault_settings.py) 3 how many pages must cite a name before harvest materialises a candidate stub, and before link_integrity calls an unresolved link a defect yes — via llmwiki.json
min_sessions (llmwiki/topics.py) 2 how many sessions must mention a derived name before it becomes a graph node no
_TOPIC_GRAPH_MIN_NODES (llmwiki/build.py) 5 whether graph.html renders the topic graph at all, or falls back to the page graph no

A curated entity or concept page is exempt from min_sessions: it is seeded as a node with whatever session count it has, including zero (#248). And topic pages no longer follow the third number — build writes topics/<slug>.html whenever the graph carries a curated-backed node, so a vault too small for the topic viewer still gets pages for its entities and concepts while graph.html falls back to the page graph. The ⌘K index carries exactly the topic pages that build wrote — which, since a vault can hold a curated page with neither content nor connections, can be fewer than the vault's curated pages.

Layout

The title, then an identity line of ·-separated parts in this order — each date part dropped entirely when its source is absent, never filled with a placeholder:

Entity chip · Active 2026-01-09 – 2026-07-30 · Reviewed 2026-08-01 · 7 connected topics · 12 sessions · <slug>

The kind chip names the singular kind — Entity, Concept, Project, Synthesis, Source — or Unclassified topic when no wiki page describes it. The chip is never dropped: the absence of a backing page is itself a fact, and a missing chip would leave a reader unable to tell an unclassified topic from a page that failed to render one. Below the identity line:

Where each fact comes from

This is the distinction to keep straight: sessions supply reach and activity, the topic's own wiki page supplies kind, review date and content. Neither substitutes for the other, and neither is invented.

On the page Comes from Present when
Active <first> – <last> the date frontmatter of the sessions that mention the topic — oldest to newest, collapsing to one date when they agree at least one such session carries a date
N sessions + the Sources list (Sessions / Documents) the same set of evidence pages from the graph, partitioned by compiled URL always
N connected topics + the Connected topics list co-occurrence: two topics share an edge when a session mentions both always (the count can be 0)
Kind chip the wiki/ folder holding the page that backs the topic — entities/ → Entity, concepts/ → Concept, and so on. The folder is the only kind signal the schema carries; frontmatter type is not consulted always — Unclassified topic when no page's slug or title matches the topic's canonical spelling or one of its aliases
Reviewed <date> that page's last_updated frontmatter the page records one
Page content that page's body the page has a body left after the omissions below

A topic with no backing page therefore shows no review date and no content, and its chip reads Unclassified topic — and one whose page omits last_updated shows no review date even while sessions supply activity dates.

Page content

The topic page is the only browsable surface for entity and concept pages, so it renders their content above the link lists. What survives is everything after the page's own leading # H1, minus ## Connections, ## Sessions, and ## Sources — the topic page renders Connected topics and a collapsible Sources evidence list (Sessions vs Documents) itself from the graph, so the page's hand-written versions would only duplicate them.

Project topics route to the project page

A topic backed by a page under wiki/projects/ links to /projects/<slug>.html — the full project detail page with its heatmap, session cards and charts — rather than to a thin topic page. The rewrite is applied once at build time and every surface honours it: the map's double-click target, the search index entry, Connected topics lists on topic pages and on project pages, topics/index.html, and [[wikilinks]] cited inside page content.

The match itself identifies which project it is, so an alias spelling routes as correctly as the canonical one. The rewrite is skipped when the build wrote no page for that project: wiki/projects/ is seeded from stubs while site/projects/ comes from session groups, so a project page with no recorded sessions keeps its ordinary topic page rather than being handed a link that 404s.

The type: vocabulary on the backing wiki page, and the origin of every frontmatter field, is Page kinds.


Docs hub

URL: /docs/index.html

The editorial entry point — you're reading a page compiled from the same pipeline. Covered in detail by tutorials/01-installation.md onward. See also style-guide.md.


Prototypes hub

URL: /prototypes/index.html

Review-ready UI states for UX iteration before larger UI changes touch the live templates. Six states:

Slug What's shown
page-shell layout skeleton — nav + footer + breadcrumb, empty content slot
article-anatomy annotated session page with orange callouts on every slot (frontmatter, summary, transcript, connections, related)
drawer-browse faceted project-browse drawer open (by project / lifecycle / cache_tier)
search-results command palette mid-query, 10+ results
empty-search no-match state with escape-hatch links
references-rail article with sticky right-hand ## Connections rail

Every prototype carries a 4 px #7C3AED top stripe and a "Prototype — not a live page" meta block so reviewers never confuse them with real pages.


Recent

URL: /recent.html

Newest raw documents first, one row per logical document — the same base-slug grouping as Raw / search (#305). Chunked docs (<slug>-01.md … <slug>-NN.md in one folder) collapse into a single row with a part count. Each row shows title, date, and origin source, and links to that document’s unified reader page.


Analytics

URL: /analytics.html

Session analytics plus usage-led wiki value (#52). The page opens with a hero line (main sessions · sub-agent runs · projects), then the same four-card primary row as Home (Knowledge hint includes stale candidates), then a second row of token/MCP cards. Below that, sections appear in this order:

  1. Activity — ~18-month GitHub-style heatmaps: Agents Activity (session counts), Wiki MCP calls, and — when telemetry carries signal — Session-page reads and Doc-page reads split from wiki_read_page hits.
  2. Recent activity — last entries from wiki/log.md (including producer breakdown lines such as Processed: 2 Claude · 1 Cursor).
  3. Projects — filterable card grid (session counts, date range, topic chips) linking to per-project detail pages.
  4. LLM-Wiki MCP usage — merged value block and MCP table in one section (MCP telemetry only, not file:// browsing): retrievals · writes · answer rate · payoff-per-page · distinct attributed projects; optional synthesis cost line; sessions vs documents corpus/read mix; top-earning pages; Dead stock as a shared count-badge collapsible listing every unread synthesized source (collapse_section); per-tool calls, items returned, and zero-hit rate. The live surface is six tools (#196); retired names in historical logs are folded into canonical rows at aggregation time — see mcp.md.

There is no daily bar chart — trends are read from the heatmaps. Durable counts and series are described in reference/state-persistence.md.


Command palette (⌘K)

Press ⌘K (or Ctrl+K on Linux/Windows) from any page.


Search index + chunks

Two levels:

Topic entries (type: "topic") point at topics/<slug>.html — or at projects/<slug>.html for a topic that routes to a project page; their body includes session count plus also: … aliases so a query using any non-canonical spelling still hits the right page, and their kind carries the human-readable singular label the palette badge shows (Entity, Concept, Project, … or Unclassified topic). kind is present on topic entries only. The same payloads ship as .js sidecars for file:// (#20).

The wiki corpus is lazy — it is fetched on first ⌘K, never on a page view — and search-index.json points at it through the optional _wiki_corpus manifest key. _wiki_corpus_status records whether the 50 MiB budget was reached and how many over-4-MiB pages were skipped; the palette shows that incompleteness instead of claiming a missing term occurs nowhere. Optional because a site built before #248 carries no such key: the viewer then reports the gap on the page and renders the Wiki group as broken rather than as silently empty, and it does the same when the payload itself fails to load.

The palette lazy-loads chunks as the query narrows. See reference/reader-api.md for the stable shape.


AI-consumable exports

Every session page links to a nested markdown copy for agents:

Site-level exports AI agents should start with:

URL Purpose
/llms.txt short index per llmstxt.org
/llms-full.txt flattened plain-text dump (capped at 5 MB)
/graph.jsonld schema.org JSON-LD entity / concept / source graph
/sitemap.xml standard sitemap with lastmod
/rss.xml RSS 2.0 of newest sessions
/robots.txt AI-friendly robots + link to llms.txt
/ai-readme.md navigation instructions aimed at AI agents
/manifest.json SHA-256 hashes for every file + perf-budget check

Keyboard shortcuts

Press ? on any page to see the shortcuts modal. Current set:

Key Does
⌘K / Ctrl+K open command palette
/ focus search filter (on index pages)
g h go to home
g p go to projects
g s go to sessions
j / k next / previous row (on table views)
? show this shortcut modal
Esc close modal / palette

Theming

Site-wide CSS lives in llmwiki/render/css.py. All tokens inherit from the brand system — see ../maintainers/brand-system.md.

Theme toggle (top-right): light / dark, persists via localStorage.theme. System preference (prefers-color-scheme) is honoured when no override is set.


Accessibility

WCAG 2.1 AA targeted across the whole site. Specifics in ../accessibility.md. Notable:


Keyboard shortcuts

⌘K / Ctrl+KOpen command palette
/Focus search
g hGo to home
g pGo to projects
g sGo to sessions
j / kNext / prev row (tables)
?Show this help
EscClose dialogs

Structured queries

Mix key:value filters with free text in the palette:

type:sessionOnly session pages
project:llm-wikiFilter by project name (substring)
model:claudeFilter by model name (substring)
date:>2026-03-01Sessions after a date
date:<2026-04-01Sessions before a date
tags:rustPages mentioning a tag/topic
sort:dateSort results by date (newest first)

Example: type:session project:llm-wiki date:>2026-04 sort:date