TechArticle

Wiki Configuration

Infobox

headline: Wiki Configuration
description: Reference for wiki.yaml, wiki.yml, and wiki.json (Config).

The CLI loads Config from wiki.yml, wiki.yaml, or wiki.json in the working directory (or from -c path).

The in-memory Config model uses the same nested blocks as the file (wiki, graph, site, link, check, lint, fmt, sparql_service). There is no separate flat runtime shape. Config.load() validates the file, injects config_root (the directory containing the config file), and resolves relative paths under wiki and site. Library and test code can construct configs with Config(wiki={...}, config_root=path) or Config.for_root(path, wiki={...}).

Config files are validated strictly through a Pydantic schema (extra='forbid' on every block). Unknown keys, removed aliases, wrong nested keys under check, lint, or sparql_service, invalid syntax, or a non-mapping top level all fail immediately instead of being ignored.

JSON configs may use graph.context or graph.@context for prefix maps (JSON-LD compatible).

Overview

Terminology

Label	Meaning
Schema optional	Key or block may be omitted; Pydantic applies a default. No yaml key is strictly required for `Config.load()` to succeed.
Init	Written by `wiki init` (`wiki.yml`); omitting an Init key is the same as the schema default.
Recommended	Not enforced by schema, but you typically set it for a real wiki (for example `graph.context.wiki`, `wiki.filename_pattern`, `site.layout`).
Always on	Behavior not gated by yaml severities (route safety, URL collisions, built-in RDF prefixes).

Audit lanes

Three audit lanes map to three commands:

Lane	Command	YAML block	Purpose
Integrity	`wiki check`	`check:`	SHACL, JSON Schema frontmatter, layout file existence
Convention	`wiki lint`	`lint:`	Links, filename pattern severity, headings, link style in prose
Formatting	`wiki fmt`	`fmt:`	Mechanical markdown (mdformat; inline mapping or TOML path)

Rule placement: Mechanical markdown belongs under fmt:. Wiki policy and link conventions belong under lint:. SHACL, JSON Schema, and layout keys belong under check: — never under lint:. See Style Guide for the full matrix.

Putting a regex under check.filename_pattern fails at load with a hint.
check.filename_pattern and check.headings fail at load — use lint.filename_pattern and lint.headings.

Relative --wiki-inputs paths on the CLI resolve against the config file directory (same as paths in yaml), not the shell cwd.

Blocks

Top-level blocks follow a compile pipeline plus audit lanes, not arbitrary grouping. wiki init and docs/wiki.yml use the same order as the packaged scaffold wiki.yml.

Block	Role	Command(s)	Schema	Init scaffold
`wiki:`	Corpus on disk — inputs, assets, filename regex	`check`, `lint`, `build`, `serve`	optional	yes
`graph:`	RDF compile — prefixes, document IRIs, body literals	`check`, `query`, `render`	optional	yes
`site:`	Publish routing — layout path, URL prefix, path style	`build`, `serve`	optional	yes
`link:`	`wiki link` apply format and rename repair map	`wiki link`	optional	yes
`check:`	Integrity severities	`wiki check`	optional	yes
`lint:`	Convention severities	`wiki lint`	optional	yes
`sparql_service:`	Opt-in SPARQL HTTP on `wiki serve`	`wiki serve`	optional	commented example
`fmt:`	Mechanical markdown via mdformat	`wiki fmt`	optional	inline mapping

Order in the file: source and semantics first (wiki, graph), then publish and authoring (site, link), then severity tables (check, lint), optional serve (sparql_service), then fmt last.

Split keys — policy lives in one block, severity or tooling in another:

wiki.filename_pattern — the regex string. lint.filename_pattern — how strictly to flag violations (error, warning, or off).
link.style — what wiki link --apply inserts (standard page links or wikilink). lint.link_style — whether Obsidian [[wikilinks]] in body prose are flagged when link.style is standard.

For why check, lint, fmt, and wiki link are separate commands, see Design philosophies.

Always on

These apply regardless of yaml severities:

Route safety — unsafe URL characters and spaces in routes (wiki check).
Output URL collisions — duplicate built routes (wiki check).
SHACL — when shape documents exist in the corpus (wiki check).
Built-in RDF prefixes — schema, wiki, foaf, rdf, rdfs, xsd, owl, dc, dcterms, sh, wazoo are always merged at runtime; yaml graph.context entries override or add.

Wiki (`wiki:`)

wiki:  # optional block
  inputs: [wiki]                    # default [wiki]; init writes
  assets: [assets]                  # default [assets] if assets/ exists, else []; init writes
  exclude: []                         # default []; init omits
  filename_pattern: "[A-Za-z0-9_()-]+\\.md"  # no default; recommended; init writes

Key	Required	Default	Init	Audited by
`inputs`	optional	`[wiki]`	writes	indexing (`build`, `check`, `lint`, `fmt`)
`assets`	optional	`[assets]` when `assets/` exists, else `[]`	writes	`wiki build` (static copy)
`exclude`	optional	`[]`	omits	indexing (skipped paths)
`filename_pattern`	optional (recommended)	unset — no regex check until set	writes	`wiki lint` (`lint.filename_pattern`)

Page URLs come from paths under wiki.inputs: wiki/Alice.md → /wiki/Alice/ with default site.base_url and site.url_style: dir. index.md in a folder owns that folder’s route (for example wiki/index.md → /wiki/).

See Filename conventions for regex patterns.

Graph (`graph:`)

RDF and document URI settings for graph build, wiki query, microdata, and SHACL.

graph:  # optional block
  # base_iri: unset → graph.context.wiki → https://wiki.example.org/
  content_predicate: schema:articleBody   # unset by default; init writes when flagged
  include_file_extension: false           # default false; init omits (commented)
  implicit_types: []                      # default []; init omits (commented)
  implicit_types_policy: fallback         # default fallback; init omits (commented)
  context:                                # merges with built-in prefixes; init writes
    schema: https://schema.org/
    wiki: https://example.org/wiki/       # recommended
    wazoo: https://schema.wazoo.dev/
    foaf: http://xmlns.com/foaf/0.1/
    dc: http://purl.org/dc/elements/1.1/
    dcterms: http://purl.org/dc/terms/
    sh: http://www.w3.org/ns/shacl#
    xsd: http://www.w3.org/2001/XMLSchema#

Key	Required	Default	Init	Audited by
`base_iri`	optional	unset → `graph.context.wiki` → `https://wiki.example.org/`	commented example	document IRIs, `wiki query`
`context` / `@context`	optional (recommended: `wiki`)	built-in prefixes only when unset	writes extended map	CURIE expansion, SHACL, microdata
`content_predicate`	optional	unset — no body literals in graph	writes when `--graph-content-predicate`	SPARQL full-text
`include_file_extension`	optional	`false`	omits (commented)	document URI generation
`implicit_types`	optional	`[]`	omits (commented)	default `rdf:type` on untyped pages
`implicit_types_policy`	optional	`fallback`	omits (commented)	`fallback` or `append` (SHACL shapes skip append)

When implicit_types_policy is append, frontmatter types are unioned with implicit_types (deduped by resolved URI).

Site (`site:`)

Default page layout and routing for wiki build / wiki serve. Branding and chrome → Page layout.

site:  # optional block
  layout: index.html   # unset → built-in minimal fallback layout
  base_url: /wiki                   # default /wiki; init writes
  url_style: dir                    # default dir; init writes

Key	Required	Default	Init	Audited by
`layout`	optional (recommended)	unset — packaged minimal `index.html`	writes	`wiki build`, `wiki serve`; `check.missing_layout_file` for per-page `wazoo:layout`
`base_url`	optional	`/wiki` (`""` allowed for site root)	writes	routes, layout `%wiki.base_url%`
`url_style`	optional	`dir` (`file` → `slug.html`)	writes	output paths; overridable per CLI run

site: does not carry site name, theme color, favicon, or sidebar logo. If you want custom styling, write a custom layout template file and place custom assets under the wiki.assets directory, then configure site.layout to point to it.

CLI flags on wiki build and wiki serve can override site.base_url and site.url_style for a single run.

Link (`link:`)

Settings for the wiki link command family (separate from lint.link_style severity).

link:  # optional block
  style: standard       # default standard; init writes
  renames: {}           # default {}; init omits (commented example)

Key	Required	Default	Init	Audited by
`style`	optional	`standard` (`wikilink` for wikilinks)	writes	`wiki link --apply` only
`renames`	optional	`{}`	commented example	`wiki link --fix-broken`

wiki link --fix-broken preserves the existing link kind in each file; only --apply uses link.style.

Integrity checks (`check:`)

Under check, each rule is error, warning, or off:

check:  # optional block
  missing_layout_file: error    # default error; init writes
  frontmatter_schema: error     # default error; init writes
  missing_schema_ref: error   # default error; init writes

Key	Required	Default	Init	Audited by
`missing_layout_file`	optional	`error`	writes	`wazoo:layout` paths missing on disk
`frontmatter_schema`	optional	`error`	writes	JSON Schema validation failures
`missing_schema_ref`	optional	`error`	writes	unloadable `wazoo:jsonSchema` refs

Build-safety rules (unsafe URL characters, spaces in routes) and output URL collision detection always apply regardless of check settings.

JSON Schema frontmatter (`wazoo:jsonSchema`)

wiki check validates frontmatter against JSON Schema in parallel with SHACL. Bind schemas on shape documents with wazoo:jsonSchema beside sh:targetClass; every page whose effective type matches that class must pass the bound schema(s). Individual pages may append extra schemas with their own wazoo:jsonSchema key (scalar or YAML list). Schema refs are local paths under the wiki config root (.json only) or remote http(s) URLs.

Shape binding documents are not validated as instances — only their schema refs are checked for loadability. Authoring detail: SHACL, Style Guide.

Convention audits (`lint:`)

Under lint, each rule is error, warning, or off:

lint:  # optional block
  broken_links: warning       # default warning; init writes
  filename_pattern: warning   # default warning; init writes
  headings: off               # default off; init omits
  heading_levels: off         # default off; init omits
  duplicate_headings: off     # default off; init omits
  thematic_breaks: off        # default off; init omits
  link_style: warning         # default warning; init writes

Key	Required	Default	Init	Audited by
`broken_links`	optional	`warning`	writes	wikilinks, markdown links, fragments, assets, `wiki:` CURIEs
`filename_pattern`	optional	`warning`	writes	full filename vs `wiki.filename_pattern`
`headings`	optional	`off`	omits	ATX syntax, sentence-case H2+, numbered headings
`heading_levels`	optional	`off`	omits	heading level gaps (for example H1 then H3)
`duplicate_headings`	optional	`off`	omits	duplicate heading text on one page
`thematic_breaks`	optional	`off`	omits	horizontal rules in body prose
`link_style`	optional	`warning`	writes	Obsidian `[[wikilinks]]` when `link.style` is `standard`

ATX heading syntax is also enforced by wiki fmt (mdformat); Setext underlines are converted on format.

When link.style is standard, set lint.link_style: off to allow wikilinks in prose, or set link.style: wikilink for an Obsidian-style wiki.

Serve API

Opt-in read-only SPARQL HTTP endpoint on wiki serve:

sparql_service:  # optional block
  enabled: false        # default false; init omits (commented)
  path: /api/sparql     # default /api/sparql; init omits (commented)

Key	Required	Default	Init	Audited by
`enabled`	optional	`false`	commented example	`wiki serve` SPARQL endpoint
`path`	optional	`/api/sparql`	commented example	reserved route on serve

sparql_service.enabled accepts YAML booleans and normalizes common string forms such as true, false, on, off, yes, no, 1, and 0; prefer native YAML booleans.

Example when enabled:

sparql_service:
  enabled: true
  path: /api/sparql

The endpoint reuses the same SPARQL engine as wiki query. It is read-only and intended for local or development-oriented use. HTTP request forms, supported query types, and Accept negotiation are documented in Wiki Subcommand serve.

It is opt-in by default because enabling it exposes raw graph-query access in addition to HTML preview.

sparql_service.path must not collide with the effective site.base_url page routes or the watch endpoint. Invalid values such as /, /wiki, /wiki/foo, or /wiki/__watch are rejected when wiki serve starts.

Formatting (`fmt`)

Top-level fmt configures wiki fmt (mdformat). Two shapes are allowed — not both:

fmt:  # optional block — inline mapping (init writes)
  wrap: "no"
  end_of_line: lf
  extensions: [gfm, frontmatter, wikilink]

# Pointer mode (optional alternative):
# fmt: .mdformat.toml

Key / shape	Required	Default	Init	Audited by
`wrap`	optional (inline)	`"no"`	writes	`wiki fmt`
`end_of_line`	optional (inline)	`lf`	writes	`wiki fmt`
`extensions`	optional (inline)	`[gfm, frontmatter, wikilink]`	writes	`wiki fmt`
TOML path	optional	unset — see fallback chain below	omits (commented)	`wiki fmt`

Omit fmt entirely to use fallbacks: config_root/.mdformat.toml, then upward search from each markdown file, then Wiki CLI fmt defaults (same as inline defaults above). See Wiki Subcommand fmt for the full resolution order.

Shape	Example	When to use
Inline mapping	`fmt: { wrap: "no" }`	Default; what `wiki init` writes
Relative path	`fmt: custom.toml`	Share one TOML file or keep fmt out of yaml

Invalid inline keys or values fail when the config loads. Invalid TOML syntax fails when wiki fmt reads the file.

In library code, loaded Config.fmt is a FmtConfig with options (inline mapping) or toml (resolved path under config_root).

Page layout

When site.layout is set, the CLI renders every page through that page layout (.html). Per-page overrides use wazoo:layout in frontmatter; see Wiki Page Layouts.

Layout strategy

The first-class presentation contract in this repository is layout files referenced from site.layout (for example index.html).

The Wiki CLI owns the semantic markdown-to-HTML pipeline and layout slot contract.
Wiki page layout files are the primary built-in extension point for presentation.
Advanced themes or framework-specific sites such as Next.js, Mintlify, or other external docs stacks are treated as downstream integrations or separate layout/template repositories.

Minimal fallback

Without a configured layout file (or when the path is missing), every page is rendered with the built-in minimal fallback layout (index.html), which outputs plain, unstyled HTML containing only <h1> and content. It does not link any default CSS or assets and does not include a sidebar, tabs, infobox, table of contents, backlinks, or categories out-of-the-box.

Layout slots

Layout files use %wiki.*% slot substitution (not Jinja). On each page render, the CLI builds a slot map from the current page context and replaces every known slot in your layout file. Unknown %wiki.*% spellings are left unchanged.

Programmatic consumers and contract tests use wiki.site.layout_tokens.build_layout_token_map as the single boundary for slot production. See Wiki Programmatic API.

Canonical slot list (3 slots):

Slot	Source	Substitution
`%wiki.base_url%`	`site.base_url`	HTML-escaped text (`/wiki`, or `""` for site root)
`Wiki Configuration - Wiki`	built per page	`<title>{page title} - Wiki CLI</title>` (title HTML-escaped)
`%wiki.body%`	rendered markdown body	Pre-built HTML (not escaped)

Packaged layouts

File	When used	Typical slots
`index.html`	`site.layout` unset or missing file	`Wiki Configuration - Wiki`, `%wiki.body%`

Example excerpt (index.html):

<!DOCTYPE html>
<html lang=en>
<head>
<meta charset=UTF-8>
<meta name=viewport content=width=device-width,initial-scale=1.0>
Wiki Configuration - Wiki
</head>
<body>
%wiki.body%
</body>
</html>

Custom CSS

The Wiki CLI does not copy or link a default stylesheet out-of-the-box. To add styling to your pages:

Edit the layout file — set site.layout in wiki.yml to a custom layout file. Link stylesheets in <head>, or write inline styles.
Link wiki assets — place .css files under a directory listed in wiki.assets, then reference them from the layout, for example <link rel="stylesheet" href="%wiki.base_url%/assets/site.css">. Built assets are served at %wiki.base_url%/assets/… during wiki serve and copied into the build output.

Custom logos and icons

To customize site logos, icons, favicons, or touch icons:

Place your asset files (such as logo.svg, logo.png, favicon.ico) under a directory listed in wiki.assets.
Reference the assets from your custom layout file, for example:

<img src="%wiki.base_url%/assets/logo.svg" alt="" width="80" height="80">

You can also add <link rel="icon">, <link rel="apple-touch-icon">, or other <head> tags directly in your custom layout file.

Built assets are served at %wiki.base_url%/assets/… during wiki serve and copied into the build output.

See also Wiki Page Layouts for site.layout, wazoo:layout, and packaged layout files.

The metadata pane uses the same RDF serialization path as wiki export (compacted JSON-LD, Turtle, N3, RDF/XML, N-Triples, TriG, N-Quads). A compact Format chip row switches views without JavaScript. In wiki serve, set the initial chip with ?metadata_format=FORMAT (for example turtle or json-ld). In wiki build, all format views are embedded in the page HTML so the picker works offline.

Built-in CSS classes and IDs

The wiki builder generates these selectors in the rendered page content:

Selector	Where
`#article-top`	Read-view `<article>` wrapper around rendered markdown body.
`#firstHeading`	Read-view page title `<h1>`; also Talk / Source / Metadata pane headings. TOC “(Top)” links here.
`#siteSub`	Subtitle under Talk / Source / Metadata pane headings.
`article`	Wrapper around the rendered markdown body (`#article-top`).
`.layout-label`	Uppercase type or custom-layout badge in read view.
`.toc` / `#toc`	Table of contents container.
`#catlinks` / `.catlinks`	Category links box.
`.backlinks` / `#backlinks`	Backlinks section.
`.catlinks-label`	Categories heading label.
`.catlinks-list`	Categories `<ul>`.
`.infobox`	Typed frontmatter property table.
`.page-meta`	Infobox class (used for styling).
`.template-SLUG`	Per-template class on infobox (e.g. `template-person`).
`toclevel-N` / `lN`	TOC list item classes for heading level N.
`.wikilink`	Internal wiki page links.
`pre[data-copy]`	Block code with raw source for clipboard copy.
`.code-block`	Wrapper injected around copyable pre blocks.
`.code-copy-btn`	Copy button shown on code-block hover/focus.

JavaScript hooks

Custom layout files can utilize standard JavaScript hooks or customize their own. In premium layouts (such as template repositories), the following JavaScript features can be implemented:

Function	Purpose
`switchTab(viewName)`	Switch between read / talk / source / metadata tabs.
`loadTalkNotes()`	Load per-page local-storage notes.
`saveTalkNotes()`	Save per-page notes to localStorage.
`clearTalkNotes()`	Clear per-page notes.
`copySourceCode()`	Copy markdown source to clipboard.
`copyPreContent()`	Copy a `pre[data-copy]` block to clipboard.
`initCodeCopyButtons()`	Wrap copyable pre blocks and inject copy buttons.
`toggleToc()`	Show/hide table of contents.
`goToRandomArticle()`	Navigate to a random page.
`triggerSearch()`	Execute search and navigate to first match.
`onSearchInput(e)`	Live search suggestions.
`handleSearchKey(e)`	Keyboard navigation for search suggestions.
`navigateSearch(slug)`	Navigate to a search result.
`applyCategoryFilterFromUrl()`	Filter index page by `?category=` URL parameter.

If the configured page layout file does not exist, the packaged minimal index.html layout is used silently — no error.

Filename conventions

The CLI does not hard-code kebab-case. Projects choose a convention with wiki.filename_pattern, matched against the full filename (including .md) on markdown files only.

Wikipedia-style (recommended): preserved capitalization and underscores — Gregory_Davidson.md, Pokemon_Diamond_(copy_1).md, LLM_Wiki_CLI.md. Use a pattern such as:

wiki:
  filename_pattern: "[A-Za-z0-9_()-]+\\.md"

Kebab-case (optional): if you prefer gregory-house.md, set an explicit pattern (for example [a-z0-9-]+\\.md) and enforce it via lint.filename_pattern. Wikipedia-style and kebab-case should not be mixed in one wiki.

Page routes keep the casing from the filename; GitHub Pages URLs are case-sensitive.

wiki link --fix-broken preserves the existing link kind in each file; only --apply uses link.style.

When link.style is standard, lint.link_style (default warning) flags Obsidian wikilinks ([[Page]]) in body prose. Set lint.link_style: off to allow wikilinks while keeping standard links as the apply format, or set link.style: wikilink for an Obsidian-style wiki.

Formatting (`fmt`)

Top-level fmt configures wiki fmt (mdformat). Two shapes are allowed — not both:

Shape	Example	When to use
Inline mapping	`fmt: { wrap: "no" }`	Default; what `wiki init` writes
Relative path	`fmt: custom.toml`	Share one TOML file or keep fmt out of yaml

Omit fmt entirely to use fallbacks: config_root/.mdformat.toml, then upward search from each markdown file, then Wiki CLI fmt defaults (wrap: "no", end_of_line: lf, extensions gfm, frontmatter, wikilink). See Wiki Subcommand fmt for the full resolution order.

Invalid inline keys or values fail when the config loads. Invalid TOML syntax fails when wiki fmt reads the file.

In library code, loaded Config.fmt is a FmtConfig with options (inline mapping) or toml (resolved path under config_root); yaml shapes above are unchanged.

Integrity checks (`check`)

Under check, each rule is error, warning, or off:

Rule key	Default	What it audits
`missing_layout_file`	`error`	`wazoo:layout` paths that do not resolve to a readable `.html` file
`frontmatter_schema`	`error`	Frontmatter that fails JSON Schema validation
`missing_schema_ref`	`error`	`wazoo:jsonSchema` paths or URLs that cannot be loaded
`remote_schema_refs`	`allow`	Policy for remote `http(s)` schema refs: `allow`, `deny`, or `allowlist`
`remote_schema_hosts`	`[]`	Hostnames permitted when `remote_schema_refs` is `allowlist`

Build-safety rules (unsafe URL characters, spaces in routes) and output URL collision detection always apply regardless of check settings.

JSON Schema frontmatter (`wazoo:jsonSchema`)

Shape binding documents are not validated as instances — only their schema refs are checked for loadability. Authoring detail: SHACL, Style Guide.

Convention audits (`lint`)

Under lint, each rule is error, warning, or off:

Rule key	Default	What it audits
`broken_links`	`warning`	Wikilinks, internal markdown links, heading fragments, assets, `wiki:` CURIEs
`filename_pattern`	`warning`	Full filename vs `wiki.filename_pattern` regex
`headings`	`off`	ATX `#` headings only (no Setext underlines), sentence-case H2+, H1 title case conventional, numbered headings
`thematic_breaks`	`off`	Horizontal rules (`---`, `***`, `___`) in body prose
`link_style`	`warning`	Obsidian wikilinks (`[[Page]]`) in body prose when `link.style` is `standard`

This repository

docs/wiki.yml is the dogfood wiki config: the same structure, block order, and Init columns as wiki init (wiki.yml), plus dogfood overrides — graph.context.wiki for GitHub Pages and graph.content_predicate: schema:articleBody for SPARQL full-text.

Wiki CLI — -c and --wiki-inputs global options
Wiki Subcommand init — scaffold a new wiki project
Wiki Subcommand check — integrity checks
Wiki Subcommand lint — convention audits
Wiki Subcommand query — ad-hoc SPARQL
Wiki Subcommand render — inline SPARQL tables
Wiki Subcommand serve — #serve-api config block
Graph Cache — --cache and graph reuse
Style Guide — shapes and frontmatter

Backlinks

Categories:

TechArticle

Talk / Local Notes: Wiki Configuration

Your personal scratchpad for this page (saved locally in browser)

0 characters

View Source: Wiki Configuration

Raw Markdown source code of the document

# Wiki Configuration

The CLI loads **Config** from `wiki.yml`, `wiki.yaml`, or `wiki.json` in the working directory (or from `-c path`).

The in-memory **Config** model uses the same nested blocks as the file (`wiki`, `graph`, `site`, `link`, `check`, `lint`, `fmt`, `sparql_service`). There is no separate flat runtime shape. `Config.load()` validates the file, injects `config_root` (the directory containing the config file), and resolves relative paths under `wiki` and `site`. Library and test code can construct configs with `Config(wiki={...}, config_root=path)` or `Config.for_root(path, wiki={...})`.

Config files are validated strictly through a Pydantic schema (`extra='forbid'` on every block). Unknown keys, removed aliases, wrong nested keys under `check`, `lint`, or `sparql_service`, invalid syntax, or a non-mapping top level all fail immediately instead of being ignored.

JSON configs may use `graph.context` or `graph.@context` for prefix maps (JSON-LD compatible).

## Overview

### Terminology

| Label               | Meaning                                                                                                                                                                 |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Schema optional** | Key or block may be omitted; Pydantic applies a default. No yaml key is strictly required for `Config.load()` to succeed.                                               |
| **Init**            | Written by `wiki init` ([`wiki.yml`](https://github.com/wazootech/wiki/blob/main/src/wiki/templates/wiki.yml)); omitting an Init key is the same as the schema default. |
| **Recommended**     | Not enforced by schema, but you typically set it for a real wiki (for example `graph.context.wiki`, `wiki.filename_pattern`, `site.layout`).                            |
| **Always on**       | Behavior not gated by yaml severities (route safety, URL collisions, built-in RDF prefixes).                                                                            |

### Audit lanes

Three audit lanes map to three commands:

| Lane       | Command      | YAML block | Purpose                                                         |
| ---------- | ------------ | ---------- | --------------------------------------------------------------- |
| Integrity  | `wiki check` | `check:`   | SHACL, JSON Schema frontmatter, layout file existence           |
| Convention | `wiki lint`  | `lint:`    | Links, filename pattern severity, headings, link style in prose |
| Formatting | `wiki fmt`   | `fmt:`     | Mechanical markdown (mdformat; inline mapping or TOML path)     |

**Rule placement:** Mechanical markdown belongs under **`fmt:`**. Wiki policy and link conventions belong under **`lint:`**. SHACL, JSON Schema, and layout keys belong under **`check:`** — never under `lint:`. See [Style Guide](Style_Guide.md) for the full matrix.

- Putting a regex under `check.filename_pattern` fails at load with a hint.
- `check.filename_pattern` and `check.headings` fail at load — use `lint.filename_pattern` and `lint.headings`.

Relative **`--wiki-inputs`** paths on the CLI resolve against the config file directory (same as paths in yaml), not the shell cwd.

### Blocks

Top-level blocks follow a **compile pipeline** plus **audit lanes**, not arbitrary grouping. `wiki init` and [docs/wiki.yml](https://github.com/wazootech/wiki/blob/main/docs/wiki.yml) use the same order as the packaged scaffold [`wiki.yml`](https://github.com/wazootech/wiki/blob/main/src/wiki/templates/wiki.yml).

| Block             | Role                                                  | Command(s)                        | Schema   | Init scaffold     |
| ----------------- | ----------------------------------------------------- | --------------------------------- | -------- | ----------------- |
| `wiki:`           | Corpus on disk — inputs, assets, filename regex       | `check`, `lint`, `build`, `serve` | optional | yes               |
| `graph:`          | RDF compile — prefixes, document IRIs, body literals  | `check`, `query`, `render`        | optional | yes               |
| `site:`           | Publish routing — layout path, URL prefix, path style | `build`, `serve`                  | optional | yes               |
| `link:`           | `wiki link` apply format and rename repair map        | `wiki link`                       | optional | yes               |
| `check:`          | Integrity severities                                  | `wiki check`                      | optional | yes               |
| `lint:`           | Convention severities                                 | `wiki lint`                       | optional | yes               |
| `sparql_service:` | Opt-in SPARQL HTTP on `wiki serve`                    | `wiki serve`                      | optional | commented example |
| `fmt:`            | Mechanical markdown via mdformat                      | `wiki fmt`                        | optional | inline mapping    |

**Order in the file:** source and semantics first (`wiki`, `graph`), then publish and authoring (`site`, `link`), then severity tables (`check`, `lint`), optional serve (`sparql_service`), then `fmt` last.

**Split keys** — policy lives in one block, severity or tooling in another:

- **`wiki.filename_pattern`** — the regex string. **`lint.filename_pattern`** — how strictly to flag violations (`error`, `warning`, or `off`).
- **`link.style`** — what `wiki link --apply` inserts (`standard` page links or `wikilink`). **`lint.link_style`** — whether Obsidian `[[wikilinks]]` in body prose are flagged when `link.style` is `standard`.

For why `check`, `lint`, `fmt`, and `wiki link` are separate commands, see [Design philosophies](Design_Philosophies.md#check-lint-fmt-and-link).

### Always on

These apply regardless of yaml severities:

- **Route safety** — unsafe URL characters and spaces in routes (`wiki check`).
- **Output URL collisions** — duplicate built routes (`wiki check`).
- **SHACL** — when shape documents exist in the corpus (`wiki check`).
- **Built-in RDF prefixes** — `schema`, `wiki`, `foaf`, `rdf`, `rdfs`, `xsd`, `owl`, `dc`, `dcterms`, `sh`, `wazoo` are always merged at runtime; yaml `graph.context` entries override or add.

## Wiki (`wiki:`)

```yaml
wiki:  # optional block
  inputs: [wiki]                    # default [wiki]; init writes
  assets: [assets]                  # default [assets] if assets/ exists, else []; init writes
  exclude: []                         # default []; init omits
  filename_pattern: "[A-Za-z0-9_()-]+\\.md"  # no default; recommended; init writes
```

| Key                | Required               | Default                                     | Init   | Audited by                                 |
| ------------------ | ---------------------- | ------------------------------------------- | ------ | ------------------------------------------ |
| `inputs`           | optional               | `[wiki]`                                    | writes | indexing (`build`, `check`, `lint`, `fmt`) |
| `assets`           | optional               | `[assets]` when `assets/` exists, else `[]` | writes | `wiki build` (static copy)                 |
| `exclude`          | optional               | `[]`                                        | omits  | indexing (skipped paths)                   |
| `filename_pattern` | optional (recommended) | unset — no regex check until set            | writes | `wiki lint` (`lint.filename_pattern`)      |

Page URLs come from paths under `wiki.inputs`: `wiki/Alice.md` → `/wiki/Alice/` with default `site.base_url` and `site.url_style: dir`. `index.md` in a folder owns that folder’s route (for example `wiki/index.md` → `/wiki/`).

See [Filename conventions](#filename-conventions) for regex patterns.

## Graph (`graph:`)

RDF and document URI settings for graph build, `wiki query`, microdata, and SHACL.

```yaml
graph:  # optional block
  # base_iri: unset → graph.context.wiki → https://wiki.example.org/
  content_predicate: schema:articleBody   # unset by default; init writes when flagged
  include_file_extension: false           # default false; init omits (commented)
  implicit_types: []                      # default []; init omits (commented)
  implicit_types_policy: fallback         # default fallback; init omits (commented)
  context:                                # merges with built-in prefixes; init writes
    schema: https://schema.org/
    wiki: https://example.org/wiki/       # recommended
    wazoo: https://schema.wazoo.dev/
    foaf: http://xmlns.com/foaf/0.1/
    dc: http://purl.org/dc/elements/1.1/
    dcterms: http://purl.org/dc/terms/
    sh: http://www.w3.org/ns/shacl#
    xsd: http://www.w3.org/2001/XMLSchema#
```

| Key                      | Required                       | Default                                                    | Init                                    | Audited by                                        |
| ------------------------ | ------------------------------ | ---------------------------------------------------------- | --------------------------------------- | ------------------------------------------------- |
| `base_iri`               | optional                       | unset → `graph.context.wiki` → `https://wiki.example.org/` | commented example                       | document IRIs, `wiki query`                       |
| `context` / `@context`   | optional (recommended: `wiki`) | built-in prefixes only when unset                          | writes extended map                     | CURIE expansion, SHACL, microdata                 |
| `content_predicate`      | optional                       | unset — no body literals in graph                          | writes when `--graph-content-predicate` | SPARQL full-text                                  |
| `include_file_extension` | optional                       | `false`                                                    | omits (commented)                       | document URI generation                           |
| `implicit_types`         | optional                       | `[]`                                                       | omits (commented)                       | default `rdf:type` on untyped pages               |
| `implicit_types_policy`  | optional                       | `fallback`                                                 | omits (commented)                       | `fallback` or `append` (SHACL shapes skip append) |

When `implicit_types_policy` is `append`, frontmatter types are unioned with `implicit_types` (deduped by resolved URI).

## Site (`site:`)

Default page layout and routing for `wiki build` / `wiki serve`. Branding and chrome → [Page layout](#page-layout).

```yaml
site:  # optional block
  layout: index.html   # unset → built-in minimal fallback layout
  base_url: /wiki                   # default /wiki; init writes
  url_style: dir                    # default dir; init writes
```

| Key         | Required               | Default                               | Init   | Audited by                                                                          |
| ----------- | ---------------------- | ------------------------------------- | ------ | ----------------------------------------------------------------------------------- |
| `layout`    | optional (recommended) | unset — packaged minimal `index.html` | writes | `wiki build`, `wiki serve`; `check.missing_layout_file` for per-page `wazoo:layout` |
| `base_url`  | optional               | `/wiki` (`""` allowed for site root)  | writes | routes, layout `%wiki.base_url%`                                                    |
| `url_style` | optional               | `dir` (`file` → `slug.html`)          | writes | output paths; overridable per CLI run                                               |

`site:` does not carry site name, theme color, favicon, or sidebar logo. If you want custom styling, write a custom layout template file and place custom assets under the `wiki.assets` directory, then configure `site.layout` to point to it.

CLI flags on `wiki build` and `wiki serve` can override `site.base_url` and `site.url_style` for a single run.

## Link (`link:`)

Settings for the `wiki link` command family (separate from `lint.link_style` severity).

```yaml
link:  # optional block
  style: standard       # default standard; init writes
  renames: {}           # default {}; init omits (commented example)
```

| Key       | Required | Default                               | Init              | Audited by               |
| --------- | -------- | ------------------------------------- | ----------------- | ------------------------ |
| `style`   | optional | `standard` (`wikilink` for wikilinks) | writes            | `wiki link --apply` only |
| `renames` | optional | `{}`                                  | commented example | `wiki link --fix-broken` |

`wiki link --fix-broken` preserves the existing link kind in each file; only `--apply` uses `link.style`.

## Integrity checks (`check:`)

Under `check`, each rule is `error`, `warning`, or `off`:

```yaml
check:  # optional block
  missing_layout_file: error    # default error; init writes
  frontmatter_schema: error     # default error; init writes
  missing_schema_ref: error   # default error; init writes
```

| Key                   | Required | Default | Init   | Audited by                           |
| --------------------- | -------- | ------- | ------ | ------------------------------------ |
| `missing_layout_file` | optional | `error` | writes | `wazoo:layout` paths missing on disk |
| `frontmatter_schema`  | optional | `error` | writes | JSON Schema validation failures      |
| `missing_schema_ref`  | optional | `error` | writes | unloadable `wazoo:jsonSchema` refs   |

Build-safety rules (unsafe URL characters, spaces in routes) and output URL collision detection always apply regardless of `check` settings.

### JSON Schema frontmatter (`wazoo:jsonSchema`)

`wiki check` validates frontmatter against JSON Schema in parallel with SHACL. Bind schemas on shape documents with **`wazoo:jsonSchema`** beside **`sh:targetClass`**; every page whose effective `type` matches that class must pass the bound schema(s). Individual pages may append extra schemas with their own `wazoo:jsonSchema` key (scalar or YAML list). Schema refs are local paths under the wiki config root (`.json` only) or remote `http(s)` URLs.

Shape binding documents are not validated as instances — only their schema refs are checked for loadability. Authoring detail: [SHACL](SHACL.md), [Style Guide](Style_Guide.md).

## Convention audits (`lint:`)

Under `lint`, each rule is `error`, `warning`, or `off`:

```yaml
lint:  # optional block
  broken_links: warning       # default warning; init writes
  filename_pattern: warning   # default warning; init writes
  headings: off               # default off; init omits
  heading_levels: off         # default off; init omits
  duplicate_headings: off     # default off; init omits
  thematic_breaks: off        # default off; init omits
  link_style: warning         # default warning; init writes
```

| Key                  | Required | Default   | Init   | Audited by                                                   |
| -------------------- | -------- | --------- | ------ | ------------------------------------------------------------ |
| `broken_links`       | optional | `warning` | writes | wikilinks, markdown links, fragments, assets, `wiki:` CURIEs |
| `filename_pattern`   | optional | `warning` | writes | full filename vs `wiki.filename_pattern`                     |
| `headings`           | optional | `off`     | omits  | ATX syntax, sentence-case H2+, numbered headings             |
| `heading_levels`     | optional | `off`     | omits  | heading level gaps (for example H1 then H3)                  |
| `duplicate_headings` | optional | `off`     | omits  | duplicate heading text on one page                           |
| `thematic_breaks`    | optional | `off`     | omits  | horizontal rules in body prose                               |
| `link_style`         | optional | `warning` | writes | Obsidian `[[wikilinks]]` when `link.style` is `standard`     |

ATX heading syntax is also enforced by **`wiki fmt`** (mdformat); Setext underlines are converted on format.

When `link.style` is `standard`, set `lint.link_style: off` to allow wikilinks in prose, or set `link.style: wikilink` for an Obsidian-style wiki.

## Serve API

Opt-in read-only SPARQL HTTP endpoint on `wiki serve`:

```yaml
sparql_service:  # optional block
  enabled: false        # default false; init omits (commented)
  path: /api/sparql     # default /api/sparql; init omits (commented)
```

| Key       | Required | Default       | Init              | Audited by                   |
| --------- | -------- | ------------- | ----------------- | ---------------------------- |
| `enabled` | optional | `false`       | commented example | `wiki serve` SPARQL endpoint |
| `path`    | optional | `/api/sparql` | commented example | reserved route on serve      |

`sparql_service.enabled` accepts YAML booleans and normalizes common string forms such as `true`, `false`, `on`, `off`, `yes`, `no`, `1`, and `0`; prefer native YAML booleans.

Example when enabled:

```yaml
sparql_service:
  enabled: true
  path: /api/sparql
```

The endpoint reuses the same SPARQL engine as `wiki query`. It is read-only and intended for local or development-oriented use. HTTP request forms, supported query types, and `Accept` negotiation are documented in [Wiki Subcommand serve](Wiki_Subcommand_serve.md#sparql-endpoint).

It is **opt-in by default** because enabling it exposes raw graph-query access in addition to HTML preview.

`sparql_service.path` must not collide with the effective `site.base_url` page routes or the watch endpoint. Invalid values such as `/`, `/wiki`, `/wiki/foo`, or `/wiki/__watch` are rejected when `wiki serve` starts.

## Formatting (`fmt`)

Top-level **`fmt`** configures `wiki fmt` (mdformat). Two shapes are allowed — not both:

```yaml
fmt:  # optional block — inline mapping (init writes)
  wrap: "no"
  end_of_line: lf
  extensions: [gfm, frontmatter, wikilink]

# Pointer mode (optional alternative):
# fmt: .mdformat.toml
```

| Key / shape   | Required          | Default                          | Init              | Audited by |
| ------------- | ----------------- | -------------------------------- | ----------------- | ---------- |
| `wrap`        | optional (inline) | `"no"`                           | writes            | `wiki fmt` |
| `end_of_line` | optional (inline) | `lf`                             | writes            | `wiki fmt` |
| `extensions`  | optional (inline) | `[gfm, frontmatter, wikilink]`   | writes            | `wiki fmt` |
| TOML path     | optional          | unset — see fallback chain below | omits (commented) | `wiki fmt` |

Omit `fmt` entirely to use fallbacks: `config_root/.mdformat.toml`, then upward search from each markdown file, then **Wiki CLI fmt defaults** (same as inline defaults above). See [Wiki Subcommand fmt](Wiki_Subcommand_fmt.md) for the full resolution order.

| Shape          | Example               | When to use                                 |
| -------------- | --------------------- | ------------------------------------------- |
| Inline mapping | `fmt: { wrap: "no" }` | Default; what `wiki init` writes            |
| Relative path  | `fmt: custom.toml`    | Share one TOML file or keep fmt out of yaml |

Invalid inline keys or values fail when the config loads. Invalid TOML syntax fails when `wiki fmt` reads the file.

In library code, loaded `Config.fmt` is a `FmtConfig` with `options` (inline mapping) or `toml` (resolved path under `config_root`).

## Page layout

When `site.layout` is set, the CLI renders every page through that page layout (`.html`). Per-page overrides use `wazoo:layout` in frontmatter; see [Wiki Page Layouts](Wiki_Page_Layouts.md).

### Layout strategy

The first-class presentation contract in this repository is layout files referenced from `site.layout` (for example `index.html`).

- The [Wiki CLI](Wiki_CLI.md) owns the semantic markdown-to-HTML pipeline and layout slot contract.
- Wiki page layout files are the primary built-in extension point for presentation.
- Advanced themes or framework-specific sites such as Next.js, Mintlify, or other external docs stacks are treated as downstream integrations or separate layout/template repositories.

### Minimal fallback

Without a configured layout file (or when the path is missing), every page is rendered with the built-in minimal fallback layout (`index.html`), which outputs plain, unstyled HTML containing only `<h1>` and content. It does not link any default CSS or assets and does not include a sidebar, tabs, infobox, table of contents, backlinks, or categories out-of-the-box.

### Layout slots

Layout files use `%wiki.*%` slot substitution (not Jinja). On each page render, the CLI builds a slot map from the current page context and replaces every known slot in your layout file. Unknown `%wiki.*%` spellings are left unchanged.

Programmatic consumers and contract tests use `wiki.site.layout_tokens.build_layout_token_map` as the single boundary for slot production. See [Wiki Programmatic API](Wiki_Programmatic_API.md#layout-slot-contract).

Canonical slot list (3 slots):

| Slot              | Source                 | Substitution                                                  |
| ----------------- | ---------------------- | ------------------------------------------------------------- |
| `%wiki.base_url%` | `site.base_url`        | HTML-escaped text (`/wiki`, or `""` for site root)            |
| `<title>Wiki Configuration - Wiki</title>`     | built per page         | `<title>{page title} - Wiki CLI</title>` (title HTML-escaped) |
| `<p>The CLI loads <strong>Config</strong> from <code>wiki.yml</code>, <code>wiki.yaml</code>, or <code>wiki.json</code> in the working directory (or from <code>-c path</code>).</p>
<p>The in-memory <strong>Config</strong> model uses the same nested blocks as the file (<code>wiki</code>, <code>graph</code>, <code>site</code>, <code>link</code>, <code>check</code>, <code>lint</code>, <code>fmt</code>, <code>sparql_service</code>). There is no separate flat runtime shape. <code>Config.load()</code> validates the file, injects <code>config_root</code> (the directory containing the config file), and resolves relative paths under <code>wiki</code> and <code>site</code>. Library and test code can construct configs with <code>Config(wiki={...}, config_root=path)</code> or <code>Config.for_root(path, wiki={...})</code>.</p>
<p>Config files are validated strictly through a Pydantic schema (<code>extra='forbid'</code> on every block). Unknown keys, removed aliases, wrong nested keys under <code>check</code>, <code>lint</code>, or <code>sparql_service</code>, invalid syntax, or a non-mapping top level all fail immediately instead of being ignored.</p>
<p>JSON configs may use <code>graph.context</code> or <code>graph.@context</code> for prefix maps (JSON-LD compatible).</p>
<h2 id="overview">Overview</h2>
<h3 id="terminology">Terminology</h3>
<table>
<thead>
<tr>
<th>Label</th>
<th>Meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Schema optional</strong></td>
<td>Key or block may be omitted; Pydantic applies a default. No yaml key is strictly required for <code>Config.load()</code> to succeed.</td>
</tr>
<tr>
<td><strong>Init</strong></td>
<td>Written by <code>wiki init</code> (<a href="https://github.com/wazootech/wiki/blob/main/src/wiki/templates/wiki.yml"><code>wiki.yml</code></a>); omitting an Init key is the same as the schema default.</td>
</tr>
<tr>
<td><strong>Recommended</strong></td>
<td>Not enforced by schema, but you typically set it for a real wiki (for example <code>graph.context.wiki</code>, <code>wiki.filename_pattern</code>, <code>site.layout</code>).</td>
</tr>
<tr>
<td><strong>Always on</strong></td>
<td>Behavior not gated by yaml severities (route safety, URL collisions, built-in RDF prefixes).</td>
</tr>
</tbody>
</table>
<h3 id="audit-lanes">Audit lanes</h3>
<p>Three audit lanes map to three commands:</p>
<table>
<thead>
<tr>
<th>Lane</th>
<th>Command</th>
<th>YAML block</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td>Integrity</td>
<td><code>wiki check</code></td>
<td><code>check:</code></td>
<td>SHACL, JSON Schema frontmatter, layout file existence</td>
</tr>
<tr>
<td>Convention</td>
<td><code>wiki lint</code></td>
<td><code>lint:</code></td>
<td>Links, filename pattern severity, headings, link style in prose</td>
</tr>
<tr>
<td>Formatting</td>
<td><code>wiki fmt</code></td>
<td><code>fmt:</code></td>
<td>Mechanical markdown (mdformat; inline mapping or TOML path)</td>
</tr>
</tbody>
</table>
<p><strong>Rule placement:</strong> Mechanical markdown belongs under <strong><code>fmt:</code></strong>. Wiki policy and link conventions belong under <strong><code>lint:</code></strong>. SHACL, JSON Schema, and layout keys belong under <strong><code>check:</code></strong> — never under <code>lint:</code>. See <a href="/Style_Guide/">Style Guide</a> for the full matrix.</p>
<ul>
<li>Putting a regex under <code>check.filename_pattern</code> fails at load with a hint.</li>
<li><code>check.filename_pattern</code> and <code>check.headings</code> fail at load — use <code>lint.filename_pattern</code> and <code>lint.headings</code>.</li>
</ul>
<p>Relative <strong><code>--wiki-inputs</code></strong> paths on the CLI resolve against the config file directory (same as paths in yaml), not the shell cwd.</p>
<h3 id="blocks">Blocks</h3>
<p>Top-level blocks follow a <strong>compile pipeline</strong> plus <strong>audit lanes</strong>, not arbitrary grouping. <code>wiki init</code> and <a href="https://github.com/wazootech/wiki/blob/main/docs/wiki.yml">docs/wiki.yml</a> use the same order as the packaged scaffold <a href="https://github.com/wazootech/wiki/blob/main/src/wiki/templates/wiki.yml"><code>wiki.yml</code></a>.</p>
<table>
<thead>
<tr>
<th>Block</th>
<th>Role</th>
<th>Command(s)</th>
<th>Schema</th>
<th>Init scaffold</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>wiki:</code></td>
<td>Corpus on disk — inputs, assets, filename regex</td>
<td><code>check</code>, <code>lint</code>, <code>build</code>, <code>serve</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>graph:</code></td>
<td>RDF compile — prefixes, document IRIs, body literals</td>
<td><code>check</code>, <code>query</code>, <code>render</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>site:</code></td>
<td>Publish routing — layout path, URL prefix, path style</td>
<td><code>build</code>, <code>serve</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>link:</code></td>
<td><code>wiki link</code> apply format and rename repair map</td>
<td><code>wiki link</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>check:</code></td>
<td>Integrity severities</td>
<td><code>wiki check</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>lint:</code></td>
<td>Convention severities</td>
<td><code>wiki lint</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>sparql_service:</code></td>
<td>Opt-in SPARQL HTTP on <code>wiki serve</code></td>
<td><code>wiki serve</code></td>
<td>optional</td>
<td>commented example</td>
</tr>
<tr>
<td><code>fmt:</code></td>
<td>Mechanical markdown via mdformat</td>
<td><code>wiki fmt</code></td>
<td>optional</td>
<td>inline mapping</td>
</tr>
</tbody>
</table>
<p><strong>Order in the file:</strong> source and semantics first (<code>wiki</code>, <code>graph</code>), then publish and authoring (<code>site</code>, <code>link</code>), then severity tables (<code>check</code>, <code>lint</code>), optional serve (<code>sparql_service</code>), then <code>fmt</code> last.</p>
<p><strong>Split keys</strong> — policy lives in one block, severity or tooling in another:</p>
<ul>
<li><strong><code>wiki.filename_pattern</code></strong> — the regex string. <strong><code>lint.filename_pattern</code></strong> — how strictly to flag violations (<code>error</code>, <code>warning</code>, or <code>off</code>).</li>
<li><strong><code>link.style</code></strong> — what <code>wiki link --apply</code> inserts (<code>standard</code> page links or <code>wikilink</code>). <strong><code>lint.link_style</code></strong> — whether Obsidian <code>[[wikilinks]]</code> in body prose are flagged when <code>link.style</code> is <code>standard</code>.</li>
</ul>
<p>For why <code>check</code>, <code>lint</code>, <code>fmt</code>, and <code>wiki link</code> are separate commands, see <a href="/Design_Philosophies/#check-lint-fmt-and-link">Design philosophies</a>.</p>
<h3 id="always-on">Always on</h3>
<p>These apply regardless of yaml severities:</p>
<ul>
<li><strong>Route safety</strong> — unsafe URL characters and spaces in routes (<code>wiki check</code>).</li>
<li><strong>Output URL collisions</strong> — duplicate built routes (<code>wiki check</code>).</li>
<li><strong>SHACL</strong> — when shape documents exist in the corpus (<code>wiki check</code>).</li>
<li><strong>Built-in RDF prefixes</strong> — <code>schema</code>, <code>wiki</code>, <code>foaf</code>, <code>rdf</code>, <code>rdfs</code>, <code>xsd</code>, <code>owl</code>, <code>dc</code>, <code>dcterms</code>, <code>sh</code>, <code>wazoo</code> are always merged at runtime; yaml <code>graph.context</code> entries override or add.</li>
</ul>
<h2 id="wiki-wiki">Wiki (<code>wiki:</code>)</h2>
<pre data-copy="wiki:  # optional block
  inputs: [wiki]                    # default [wiki]; init writes
  assets: [assets]                  # default [assets] if assets/ exists, else []; init writes
  exclude: []                         # default []; init omits
  filename_pattern: "[A-Za-z0-9_()-]+\\.md"  # no default; recommended; init writes
" class="highlight"><code class="language-yaml"><span class="nt">wiki</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">inputs</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[</span><span class="nv">wiki</span><span class="p p-Indicator">]</span><span class="w">                    </span><span class="c1"># default [wiki]; init writes</span>
<span class="w">  </span><span class="nt">assets</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[</span><span class="nv">assets</span><span class="p p-Indicator">]</span><span class="w">                  </span><span class="c1"># default [assets] if assets/ exists, else []; init writes</span>
<span class="w">  </span><span class="nt">exclude</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[]</span><span class="w">                         </span><span class="c1"># default []; init omits</span>
<span class="w">  </span><span class="nt">filename_pattern</span><span class="p">:</span><span class="w"> </span><span class="s">"[A-Za-z0-9_()-]+\\.md"</span><span class="w">  </span><span class="c1"># no default; recommended; init writes</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>inputs</code></td>
<td>optional</td>
<td><code>[wiki]</code></td>
<td>writes</td>
<td>indexing (<code>build</code>, <code>check</code>, <code>lint</code>, <code>fmt</code>)</td>
</tr>
<tr>
<td><code>assets</code></td>
<td>optional</td>
<td><code>[assets]</code> when <code>assets/</code> exists, else <code>[]</code></td>
<td>writes</td>
<td><code>wiki build</code> (static copy)</td>
</tr>
<tr>
<td><code>exclude</code></td>
<td>optional</td>
<td><code>[]</code></td>
<td>omits</td>
<td>indexing (skipped paths)</td>
</tr>
<tr>
<td><code>filename_pattern</code></td>
<td>optional (recommended)</td>
<td>unset — no regex check until set</td>
<td>writes</td>
<td><code>wiki lint</code> (<code>lint.filename_pattern</code>)</td>
</tr>
</tbody>
</table>
<p>Page URLs come from paths under <code>wiki.inputs</code>: <code>wiki/Alice.md</code> → <code>/wiki/Alice/</code> with default <code>site.base_url</code> and <code>site.url_style: dir</code>. <code>index.md</code> in a folder owns that folder’s route (for example <code>wiki/index.md</code> → <code>/wiki/</code>).</p>
<p>See <a href="#filename-conventions">Filename conventions</a> for regex patterns.</p>
<h2 id="graph-graph">Graph (<code>graph:</code>)</h2>
<p>RDF and document URI settings for graph build, <code>wiki query</code>, microdata, and SHACL.</p>
<pre data-copy="graph:  # optional block
  # base_iri: unset → graph.context.wiki → https://wiki.example.org/
  content_predicate: schema:articleBody   # unset by default; init writes when flagged
  include_file_extension: false           # default false; init omits (commented)
  implicit_types: []                      # default []; init omits (commented)
  implicit_types_policy: fallback         # default fallback; init omits (commented)
  context:                                # merges with built-in prefixes; init writes
    schema: https://schema.org/
    wiki: https://example.org/wiki/       # recommended
    wazoo: https://schema.wazoo.dev/
    foaf: http://xmlns.com/foaf/0.1/
    dc: http://purl.org/dc/elements/1.1/
    dcterms: http://purl.org/dc/terms/
    sh: http://www.w3.org/ns/shacl#
    xsd: http://www.w3.org/2001/XMLSchema#
" class="highlight"><code class="language-yaml"><span class="nt">graph</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="c1"># base_iri: unset → graph.context.wiki → https://wiki.example.org/</span>
<span class="w">  </span><span class="nt">content_predicate</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">schema:articleBody</span><span class="w">   </span><span class="c1"># unset by default; init writes when flagged</span>
<span class="w">  </span><span class="nt">include_file_extension</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">false</span><span class="w">           </span><span class="c1"># default false; init omits (commented)</span>
<span class="w">  </span><span class="nt">implicit_types</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[]</span><span class="w">                      </span><span class="c1"># default []; init omits (commented)</span>
<span class="w">  </span><span class="nt">implicit_types_policy</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">fallback</span><span class="w">         </span><span class="c1"># default fallback; init omits (commented)</span>
<span class="w">  </span><span class="nt">context</span><span class="p">:</span><span class="w">                                </span><span class="c1"># merges with built-in prefixes; init writes</span>
<span class="w">    </span><span class="nt">schema</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">https://schema.org/</span>
<span class="w">    </span><span class="nt">wiki</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">https://example.org/wiki/</span><span class="w">       </span><span class="c1"># recommended</span>
<span class="w">    </span><span class="nt">wazoo</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">https://schema.wazoo.dev/</span>
<span class="w">    </span><span class="nt">foaf</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">http://xmlns.com/foaf/0.1/</span>
<span class="w">    </span><span class="nt">dc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">http://purl.org/dc/elements/1.1/</span>
<span class="w">    </span><span class="nt">dcterms</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">http://purl.org/dc/terms/</span>
<span class="w">    </span><span class="nt">sh</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">http://www.w3.org/ns/shacl#</span>
<span class="w">    </span><span class="nt">xsd</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">http://www.w3.org/2001/XMLSchema#</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>base_iri</code></td>
<td>optional</td>
<td>unset → <code>graph.context.wiki</code> → <code>https://wiki.example.org/</code></td>
<td>commented example</td>
<td>document IRIs, <code>wiki query</code></td>
</tr>
<tr>
<td><code>context</code> / <code>@context</code></td>
<td>optional (recommended: <code>wiki</code>)</td>
<td>built-in prefixes only when unset</td>
<td>writes extended map</td>
<td>CURIE expansion, SHACL, microdata</td>
</tr>
<tr>
<td><code>content_predicate</code></td>
<td>optional</td>
<td>unset — no body literals in graph</td>
<td>writes when <code>--graph-content-predicate</code></td>
<td>SPARQL full-text</td>
</tr>
<tr>
<td><code>include_file_extension</code></td>
<td>optional</td>
<td><code>false</code></td>
<td>omits (commented)</td>
<td>document URI generation</td>
</tr>
<tr>
<td><code>implicit_types</code></td>
<td>optional</td>
<td><code>[]</code></td>
<td>omits (commented)</td>
<td>default <code>rdf:type</code> on untyped pages</td>
</tr>
<tr>
<td><code>implicit_types_policy</code></td>
<td>optional</td>
<td><code>fallback</code></td>
<td>omits (commented)</td>
<td><code>fallback</code> or <code>append</code> (SHACL shapes skip append)</td>
</tr>
</tbody>
</table>
<p>When <code>implicit_types_policy</code> is <code>append</code>, frontmatter types are unioned with <code>implicit_types</code> (deduped by resolved URI).</p>
<h2 id="site-site">Site (<code>site:</code>)</h2>
<p>Default page layout and routing for <code>wiki build</code> / <code>wiki serve</code>. Branding and chrome → <a href="#page-layout">Page layout</a>.</p>
<pre data-copy="site:  # optional block
  layout: index.html   # unset → built-in minimal fallback layout
  base_url: /wiki                   # default /wiki; init writes
  url_style: dir                    # default dir; init writes
" class="highlight"><code class="language-yaml"><span class="nt">site</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">layout</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">index.html</span><span class="w">   </span><span class="c1"># unset → built-in minimal fallback layout</span>
<span class="w">  </span><span class="nt">base_url</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">/wiki</span><span class="w">                   </span><span class="c1"># default /wiki; init writes</span>
<span class="w">  </span><span class="nt">url_style</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">dir</span><span class="w">                    </span><span class="c1"># default dir; init writes</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>layout</code></td>
<td>optional (recommended)</td>
<td>unset — packaged minimal <code>index.html</code></td>
<td>writes</td>
<td><code>wiki build</code>, <code>wiki serve</code>; <code>check.missing_layout_file</code> for per-page <code>wazoo:layout</code></td>
</tr>
<tr>
<td><code>base_url</code></td>
<td>optional</td>
<td><code>/wiki</code> (<code>""</code> allowed for site root)</td>
<td>writes</td>
<td>routes, layout <code>%wiki.base_url%</code></td>
</tr>
<tr>
<td><code>url_style</code></td>
<td>optional</td>
<td><code>dir</code> (<code>file</code> → <code>slug.html</code>)</td>
<td>writes</td>
<td>output paths; overridable per CLI run</td>
</tr>
</tbody>
</table>
<p><code>site:</code> does not carry site name, theme color, favicon, or sidebar logo. If you want custom styling, write a custom layout template file and place custom assets under the <code>wiki.assets</code> directory, then configure <code>site.layout</code> to point to it.</p>
<p>CLI flags on <code>wiki build</code> and <code>wiki serve</code> can override <code>site.base_url</code> and <code>site.url_style</code> for a single run.</p>
<h2 id="link-link">Link (<code>link:</code>)</h2>
<p>Settings for the <code>wiki link</code> command family (separate from <code>lint.link_style</code> severity).</p>
<pre data-copy="link:  # optional block
  style: standard       # default standard; init writes
  renames: {}           # default {}; init omits (commented example)
" class="highlight"><code class="language-yaml"><span class="nt">link</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">style</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">standard</span><span class="w">       </span><span class="c1"># default standard; init writes</span>
<span class="w">  </span><span class="nt">renames</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">{}</span><span class="w">           </span><span class="c1"># default {}; init omits (commented example)</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>style</code></td>
<td>optional</td>
<td><code>standard</code> (<code>wikilink</code> for wikilinks)</td>
<td>writes</td>
<td><code>wiki link --apply</code> only</td>
</tr>
<tr>
<td><code>renames</code></td>
<td>optional</td>
<td><code>{}</code></td>
<td>commented example</td>
<td><code>wiki link --fix-broken</code></td>
</tr>
</tbody>
</table>
<p><code>wiki link --fix-broken</code> preserves the existing link kind in each file; only <code>--apply</code> uses <code>link.style</code>.</p>
<h2 id="integrity-checks-check">Integrity checks (<code>check:</code>)</h2>
<p>Under <code>check</code>, each rule is <code>error</code>, <code>warning</code>, or <code>off</code>:</p>
<pre data-copy="check:  # optional block
  missing_layout_file: error    # default error; init writes
  frontmatter_schema: error     # default error; init writes
  missing_schema_ref: error   # default error; init writes
" class="highlight"><code class="language-yaml"><span class="nt">check</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">missing_layout_file</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">error</span><span class="w">    </span><span class="c1"># default error; init writes</span>
<span class="w">  </span><span class="nt">frontmatter_schema</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">error</span><span class="w">     </span><span class="c1"># default error; init writes</span>
<span class="w">  </span><span class="nt">missing_schema_ref</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">error</span><span class="w">   </span><span class="c1"># default error; init writes</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>missing_layout_file</code></td>
<td>optional</td>
<td><code>error</code></td>
<td>writes</td>
<td><code>wazoo:layout</code> paths missing on disk</td>
</tr>
<tr>
<td><code>frontmatter_schema</code></td>
<td>optional</td>
<td><code>error</code></td>
<td>writes</td>
<td>JSON Schema validation failures</td>
</tr>
<tr>
<td><code>missing_schema_ref</code></td>
<td>optional</td>
<td><code>error</code></td>
<td>writes</td>
<td>unloadable <code>wazoo:jsonSchema</code> refs</td>
</tr>
</tbody>
</table>
<p>Build-safety rules (unsafe URL characters, spaces in routes) and output URL collision detection always apply regardless of <code>check</code> settings.</p>
<h3 id="json-schema-frontmatter-wazoojsonschema">JSON Schema frontmatter (<code>wazoo:jsonSchema</code>)</h3>
<p><code>wiki check</code> validates frontmatter against JSON Schema in parallel with SHACL. Bind schemas on shape documents with <strong><code>wazoo:jsonSchema</code></strong> beside <strong><code>sh:targetClass</code></strong>; every page whose effective <code>type</code> matches that class must pass the bound schema(s). Individual pages may append extra schemas with their own <code>wazoo:jsonSchema</code> key (scalar or YAML list). Schema refs are local paths under the wiki config root (<code>.json</code> only) or remote <code>http(s)</code> URLs.</p>
<p>Shape binding documents are not validated as instances — only their schema refs are checked for loadability. Authoring detail: <a href="/SHACL/">SHACL</a>, <a href="/Style_Guide/">Style Guide</a>.</p>
<h2 id="convention-audits-lint">Convention audits (<code>lint:</code>)</h2>
<p>Under <code>lint</code>, each rule is <code>error</code>, <code>warning</code>, or <code>off</code>:</p>
<pre data-copy="lint:  # optional block
  broken_links: warning       # default warning; init writes
  filename_pattern: warning   # default warning; init writes
  headings: off               # default off; init omits
  heading_levels: off         # default off; init omits
  duplicate_headings: off     # default off; init omits
  thematic_breaks: off        # default off; init omits
  link_style: warning         # default warning; init writes
" class="highlight"><code class="language-yaml"><span class="nt">lint</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">broken_links</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">warning</span><span class="w">       </span><span class="c1"># default warning; init writes</span>
<span class="w">  </span><span class="nt">filename_pattern</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">warning</span><span class="w">   </span><span class="c1"># default warning; init writes</span>
<span class="w">  </span><span class="nt">headings</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">off</span><span class="w">               </span><span class="c1"># default off; init omits</span>
<span class="w">  </span><span class="nt">heading_levels</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">off</span><span class="w">         </span><span class="c1"># default off; init omits</span>
<span class="w">  </span><span class="nt">duplicate_headings</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">off</span><span class="w">     </span><span class="c1"># default off; init omits</span>
<span class="w">  </span><span class="nt">thematic_breaks</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">off</span><span class="w">        </span><span class="c1"># default off; init omits</span>
<span class="w">  </span><span class="nt">link_style</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">warning</span><span class="w">         </span><span class="c1"># default warning; init writes</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>broken_links</code></td>
<td>optional</td>
<td><code>warning</code></td>
<td>writes</td>
<td>wikilinks, markdown links, fragments, assets, <code>wiki:</code> CURIEs</td>
</tr>
<tr>
<td><code>filename_pattern</code></td>
<td>optional</td>
<td><code>warning</code></td>
<td>writes</td>
<td>full filename vs <code>wiki.filename_pattern</code></td>
</tr>
<tr>
<td><code>headings</code></td>
<td>optional</td>
<td><code>off</code></td>
<td>omits</td>
<td>ATX syntax, sentence-case H2+, numbered headings</td>
</tr>
<tr>
<td><code>heading_levels</code></td>
<td>optional</td>
<td><code>off</code></td>
<td>omits</td>
<td>heading level gaps (for example H1 then H3)</td>
</tr>
<tr>
<td><code>duplicate_headings</code></td>
<td>optional</td>
<td><code>off</code></td>
<td>omits</td>
<td>duplicate heading text on one page</td>
</tr>
<tr>
<td><code>thematic_breaks</code></td>
<td>optional</td>
<td><code>off</code></td>
<td>omits</td>
<td>horizontal rules in body prose</td>
</tr>
<tr>
<td><code>link_style</code></td>
<td>optional</td>
<td><code>warning</code></td>
<td>writes</td>
<td>Obsidian <code>[[wikilinks]]</code> when <code>link.style</code> is <code>standard</code></td>
</tr>
</tbody>
</table>
<p>ATX heading syntax is also enforced by <strong><code>wiki fmt</code></strong> (mdformat); Setext underlines are converted on format.</p>
<p>When <code>link.style</code> is <code>standard</code>, set <code>lint.link_style: off</code> to allow wikilinks in prose, or set <code>link.style: wikilink</code> for an Obsidian-style wiki.</p>
<h2 id="serve-api">Serve API</h2>
<p>Opt-in read-only SPARQL HTTP endpoint on <code>wiki serve</code>:</p>
<pre data-copy="sparql_service:  # optional block
  enabled: false        # default false; init omits (commented)
  path: /api/sparql     # default /api/sparql; init omits (commented)
" class="highlight"><code class="language-yaml"><span class="nt">sparql_service</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">enabled</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">false</span><span class="w">        </span><span class="c1"># default false; init omits (commented)</span>
<span class="w">  </span><span class="nt">path</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">/api/sparql</span><span class="w">     </span><span class="c1"># default /api/sparql; init omits (commented)</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>enabled</code></td>
<td>optional</td>
<td><code>false</code></td>
<td>commented example</td>
<td><code>wiki serve</code> SPARQL endpoint</td>
</tr>
<tr>
<td><code>path</code></td>
<td>optional</td>
<td><code>/api/sparql</code></td>
<td>commented example</td>
<td>reserved route on serve</td>
</tr>
</tbody>
</table>
<p><code>sparql_service.enabled</code> accepts YAML booleans and normalizes common string forms such as <code>true</code>, <code>false</code>, <code>on</code>, <code>off</code>, <code>yes</code>, <code>no</code>, <code>1</code>, and <code>0</code>; prefer native YAML booleans.</p>
<p>Example when enabled:</p>
<pre data-copy="sparql_service:
  enabled: true
  path: /api/sparql
" class="highlight"><code class="language-yaml"><span class="nt">sparql_service</span><span class="p">:</span>
<span class="w">  </span><span class="nt">enabled</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">true</span>
<span class="w">  </span><span class="nt">path</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">/api/sparql</span>
</code></pre>
<p>The endpoint reuses the same SPARQL engine as <code>wiki query</code>. It is read-only and intended for local or development-oriented use. HTTP request forms, supported query types, and <code>Accept</code> negotiation are documented in <a href="/Wiki_Subcommand_serve/#sparql-endpoint">Wiki Subcommand serve</a>.</p>
<p>It is <strong>opt-in by default</strong> because enabling it exposes raw graph-query access in addition to HTML preview.</p>
<p><code>sparql_service.path</code> must not collide with the effective <code>site.base_url</code> page routes or the watch endpoint. Invalid values such as <code>/</code>, <code>/wiki</code>, <code>/wiki/foo</code>, or <code>/wiki/__watch</code> are rejected when <code>wiki serve</code> starts.</p>
<h2 id="formatting-fmt">Formatting (<code>fmt</code>)</h2>
<p>Top-level <strong><code>fmt</code></strong> configures <code>wiki fmt</code> (mdformat). Two shapes are allowed — not both:</p>
<pre data-copy="fmt:  # optional block — inline mapping (init writes)
  wrap: "no"
  end_of_line: lf
  extensions: [gfm, frontmatter, wikilink]

# Pointer mode (optional alternative):
# fmt: .mdformat.toml
" class="highlight"><code class="language-yaml"><span class="nt">fmt</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block — inline mapping (init writes)</span>
<span class="w">  </span><span class="nt">wrap</span><span class="p">:</span><span class="w"> </span><span class="s">"no"</span>
<span class="w">  </span><span class="nt">end_of_line</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">lf</span>
<span class="w">  </span><span class="nt">extensions</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[</span><span class="nv">gfm</span><span class="p p-Indicator">,</span><span class="w"> </span><span class="nv">frontmatter</span><span class="p p-Indicator">,</span><span class="w"> </span><span class="nv">wikilink</span><span class="p p-Indicator">]</span>

<span class="c1"># Pointer mode (optional alternative):</span>
<span class="c1"># fmt: .mdformat.toml</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key / shape</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>wrap</code></td>
<td>optional (inline)</td>
<td><code>"no"</code></td>
<td>writes</td>
<td><code>wiki fmt</code></td>
</tr>
<tr>
<td><code>end_of_line</code></td>
<td>optional (inline)</td>
<td><code>lf</code></td>
<td>writes</td>
<td><code>wiki fmt</code></td>
</tr>
<tr>
<td><code>extensions</code></td>
<td>optional (inline)</td>
<td><code>[gfm, frontmatter, wikilink]</code></td>
<td>writes</td>
<td><code>wiki fmt</code></td>
</tr>
<tr>
<td>TOML path</td>
<td>optional</td>
<td>unset — see fallback chain below</td>
<td>omits (commented)</td>
<td><code>wiki fmt</code></td>
</tr>
</tbody>
</table>
<p>Omit <code>fmt</code> entirely to use fallbacks: <code>config_root/.mdformat.toml</code>, then upward search from each markdown file, then <strong>Wiki CLI fmt defaults</strong> (same as inline defaults above). See <a href="/Wiki_Subcommand_fmt/">Wiki Subcommand fmt</a> for the full resolution order.</p>
<table>
<thead>
<tr>
<th>Shape</th>
<th>Example</th>
<th>When to use</th>
</tr>
</thead>
<tbody>
<tr>
<td>Inline mapping</td>
<td><code>fmt: { wrap: "no" }</code></td>
<td>Default; what <code>wiki init</code> writes</td>
</tr>
<tr>
<td>Relative path</td>
<td><code>fmt: custom.toml</code></td>
<td>Share one TOML file or keep fmt out of yaml</td>
</tr>
</tbody>
</table>
<p>Invalid inline keys or values fail when the config loads. Invalid TOML syntax fails when <code>wiki fmt</code> reads the file.</p>
<p>In library code, loaded <code>Config.fmt</code> is a <code>FmtConfig</code> with <code>options</code> (inline mapping) or <code>toml</code> (resolved path under <code>config_root</code>).</p>
<h2 id="page-layout">Page layout</h2>
<p>When <code>site.layout</code> is set, the CLI renders every page through that page layout (<code>.html</code>). Per-page overrides use <code>wazoo:layout</code> in frontmatter; see <a href="/Wiki_Page_Layouts/">Wiki Page Layouts</a>.</p>
<h3 id="layout-strategy">Layout strategy</h3>
<p>The first-class presentation contract in this repository is layout files referenced from <code>site.layout</code> (for example <code>index.html</code>).</p>
<ul>
<li>The <a href="/Wiki_CLI/">Wiki CLI</a> owns the semantic markdown-to-HTML pipeline and layout slot contract.</li>
<li>Wiki page layout files are the primary built-in extension point for presentation.</li>
<li>Advanced themes or framework-specific sites such as Next.js, Mintlify, or other external docs stacks are treated as downstream integrations or separate layout/template repositories.</li>
</ul>
<h3 id="minimal-fallback">Minimal fallback</h3>
<p>Without a configured layout file (or when the path is missing), every page is rendered with the built-in minimal fallback layout (<code>index.html</code>), which outputs plain, unstyled HTML containing only <code><h1></code> and content. It does not link any default CSS or assets and does not include a sidebar, tabs, infobox, table of contents, backlinks, or categories out-of-the-box.</p>
<h3 id="layout-slots">Layout slots</h3>
<p>Layout files use <code>%wiki.*%</code> slot substitution (not Jinja). On each page render, the CLI builds a slot map from the current page context and replaces every known slot in your layout file. Unknown <code>%wiki.*%</code> spellings are left unchanged.</p>
<p>Programmatic consumers and contract tests use <code>wiki.site.layout_tokens.build_layout_token_map</code> as the single boundary for slot production. See <a href="/Wiki_Programmatic_API/#layout-slot-contract">Wiki Programmatic API</a>.</p>
<p>Canonical slot list (3 slots):</p>
<table>
<thead>
<tr>
<th>Slot</th>
<th>Source</th>
<th>Substitution</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>%wiki.base_url%</code></td>
<td><code>site.base_url</code></td>
<td>HTML-escaped text (<code>/wiki</code>, or <code>""</code> for site root)</td>
</tr>
<tr>
<td><code><title>Wiki Configuration - Wiki</title></code></td>
<td>built per page</td>
<td><code><title>{page title} - Wiki CLI</title></code> (title HTML-escaped)</td>
</tr>
<tr>
<td><code>%wiki.body%</code></td>
<td>rendered markdown body</td>
<td>Pre-built HTML (not escaped)</td>
</tr>
</tbody>
</table>
<p><strong>Packaged layouts</strong></p>
<table>
<thead>
<tr>
<th>File</th>
<th>When used</th>
<th>Typical slots</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>index.html</code></td>
<td><code>site.layout</code> unset or missing file</td>
<td><code><title>Wiki Configuration - Wiki</title></code>, <code>%wiki.body%</code></td>
</tr>
</tbody>
</table>
<p>Example excerpt (<code>index.html</code>):</p>
<pre data-copy="<!DOCTYPE html>
<html lang=en>
<head>
<meta charset=UTF-8>
<meta name=viewport content=width=device-width,initial-scale=1.0>
<title>Wiki Configuration - Wiki</title>
</head>
<body>
%wiki.body%
</body>
</html>
" class="highlight"><code class="language-html"><span class="cp"><!DOCTYPE html></span>
<span class="p"><</span><span class="nt">html</span> <span class="na">lang</span><span class="o">=</span><span class="s">en</span><span class="p">></span>
<span class="p"><</span><span class="nt">head</span><span class="p">></span>
<span class="p"><</span><span class="nt">meta</span> <span class="na">charset</span><span class="o">=</span><span class="s">UTF-8</span><span class="p">></span>
<span class="p"><</span><span class="nt">meta</span> <span class="na">name</span><span class="o">=</span><span class="s">viewport</span> <span class="na">content</span><span class="o">=</span><span class="s">width=device-width,initial-scale=1.0</span><span class="p">></span>
<title>Wiki Configuration - Wiki</title>
<span class="p"></</span><span class="nt">head</span><span class="p">></span>
<span class="p"><</span><span class="nt">body</span><span class="p">></span>
%wiki.body%
<span class="p"></</span><span class="nt">body</span><span class="p">></span>
<span class="p"></</span><span class="nt">html</span><span class="p">></span>
</code></pre>
<h3 id="custom-css">Custom CSS</h3>
<p>The Wiki CLI does not copy or link a default stylesheet out-of-the-box. To add styling to your pages:</p>
<ol>
<li><strong>Edit the layout file</strong> — set <code>site.layout</code> in <code>wiki.yml</code> to a custom layout file. Link stylesheets in <code><head></code>, or write inline styles.</li>
<li><strong>Link wiki assets</strong> — place <code>.css</code> files under a directory listed in <code>wiki.assets</code>, then reference them from the layout, for example <code><link rel="stylesheet" href="%wiki.base_url%/assets/site.css"></code>. Built assets are served at <code>%wiki.base_url%/assets/…</code> during <code>wiki serve</code> and copied into the build output.</li>
</ol>
<h3 id="custom-logos-and-icons">Custom logos and icons</h3>
<p>To customize site logos, icons, favicons, or touch icons:</p>
<ol>
<li>Place your asset files (such as <code>logo.svg</code>, <code>logo.png</code>, <code>favicon.ico</code>) under a directory listed in <code>wiki.assets</code>.</li>
<li>Reference the assets from your custom layout file, for example:</li>
</ol>
<pre data-copy="<img src="%wiki.base_url%/assets/logo.svg" alt="" width="80" height="80">
" class="highlight"><code class="language-html"><span class="p"><</span><span class="nt">img</span> <span class="na">src</span><span class="o">=</span><span class="s">"%wiki.base_url%/assets/logo.svg"</span> <span class="na">alt</span><span class="o">=</span><span class="s">""</span> <span class="na">width</span><span class="o">=</span><span class="s">"80"</span> <span class="na">height</span><span class="o">=</span><span class="s">"80"</span><span class="p">></span>
</code></pre>
<p>You can also add <code><link rel="icon"></code>, <code><link rel="apple-touch-icon"></code>, or other <code><head></code> tags directly in your custom layout file.</p>
<p>Built assets are served at <code>%wiki.base_url%/assets/…</code> during <code>wiki serve</code> and copied into the build output.</p>
<p>See also <a href="/Wiki_Page_Layouts/">Wiki Page Layouts</a> for <code>site.layout</code>, <code>wazoo:layout</code>, and packaged layout files.</p>
<p>The metadata pane uses the same RDF serialization path as <code>wiki export</code> (compacted JSON-LD, Turtle, N3, RDF/XML, N-Triples, TriG, N-Quads). A compact <strong>Format</strong> chip row switches views without JavaScript. In <code>wiki serve</code>, set the initial chip with <code>?metadata_format=FORMAT</code> (for example <code>turtle</code> or <code>json-ld</code>). In <code>wiki build</code>, all format views are embedded in the page HTML so the picker works offline.</p>
<h3 id="built-in-css-classes-and-ids">Built-in CSS classes and IDs</h3>
<p>The wiki builder generates these selectors in the rendered page content:</p>
<table>
<thead>
<tr>
<th>Selector</th>
<th>Where</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>#article-top</code></td>
<td>Read-view <code><article></code> wrapper around rendered markdown body.</td>
</tr>
<tr>
<td><code>#firstHeading</code></td>
<td>Read-view page title <code><h1></code>; also Talk / Source / Metadata pane headings. TOC “(Top)” links here.</td>
</tr>
<tr>
<td><code>#siteSub</code></td>
<td>Subtitle under Talk / Source / Metadata pane headings.</td>
</tr>
<tr>
<td><code>article</code></td>
<td>Wrapper around the rendered markdown body (<code>#article-top</code>).</td>
</tr>
<tr>
<td><code>.layout-label</code></td>
<td>Uppercase type or custom-layout badge in read view.</td>
</tr>
<tr>
<td><code>.toc</code> / <code>#toc</code></td>
<td>Table of contents container.</td>
</tr>
<tr>
<td><code>#catlinks</code> / <code>.catlinks</code></td>
<td>Category links box.</td>
</tr>
<tr>
<td><code>.backlinks</code> / <code>#backlinks</code></td>
<td>Backlinks section.</td>
</tr>
<tr>
<td><code>.catlinks-label</code></td>
<td>Categories heading label.</td>
</tr>
<tr>
<td><code>.catlinks-list</code></td>
<td>Categories <code><ul></code>.</td>
</tr>
<tr>
<td><code>.infobox</code></td>
<td>Typed frontmatter property table.</td>
</tr>
<tr>
<td><code>.page-meta</code></td>
<td>Infobox class (used for styling).</td>
</tr>
<tr>
<td><code>.template-SLUG</code></td>
<td>Per-template class on infobox (e.g. <code>template-person</code>).</td>
</tr>
<tr>
<td><code>toclevel-N</code> / <code>lN</code></td>
<td>TOC list item classes for heading level N.</td>
</tr>
<tr>
<td><code>.wikilink</code></td>
<td>Internal wiki page links.</td>
</tr>
<tr>
<td><code>pre[data-copy]</code></td>
<td>Block code with raw source for clipboard copy.</td>
</tr>
<tr>
<td><code>.code-block</code></td>
<td>Wrapper injected around copyable pre blocks.</td>
</tr>
<tr>
<td><code>.code-copy-btn</code></td>
<td>Copy button shown on code-block hover/focus.</td>
</tr>
</tbody>
</table>
<h3 id="javascript-hooks">JavaScript hooks</h3>
<p>Custom layout files can utilize standard JavaScript hooks or customize their own. In premium layouts (such as template repositories), the following JavaScript features can be implemented:</p>
<table>
<thead>
<tr>
<th>Function</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>switchTab(viewName)</code></td>
<td>Switch between read / talk / source / metadata tabs.</td>
</tr>
<tr>
<td><code>loadTalkNotes()</code></td>
<td>Load per-page local-storage notes.</td>
</tr>
<tr>
<td><code>saveTalkNotes()</code></td>
<td>Save per-page notes to localStorage.</td>
</tr>
<tr>
<td><code>clearTalkNotes()</code></td>
<td>Clear per-page notes.</td>
</tr>
<tr>
<td><code>copySourceCode()</code></td>
<td>Copy markdown source to clipboard.</td>
</tr>
<tr>
<td><code>copyPreContent()</code></td>
<td>Copy a <code>pre[data-copy]</code> block to clipboard.</td>
</tr>
<tr>
<td><code>initCodeCopyButtons()</code></td>
<td>Wrap copyable pre blocks and inject copy buttons.</td>
</tr>
<tr>
<td><code>toggleToc()</code></td>
<td>Show/hide table of contents.</td>
</tr>
<tr>
<td><code>goToRandomArticle()</code></td>
<td>Navigate to a random page.</td>
</tr>
<tr>
<td><code>triggerSearch()</code></td>
<td>Execute search and navigate to first match.</td>
</tr>
<tr>
<td><code>onSearchInput(e)</code></td>
<td>Live search suggestions.</td>
</tr>
<tr>
<td><code>handleSearchKey(e)</code></td>
<td>Keyboard navigation for search suggestions.</td>
</tr>
<tr>
<td><code>navigateSearch(slug)</code></td>
<td>Navigate to a search result.</td>
</tr>
<tr>
<td><code>applyCategoryFilterFromUrl()</code></td>
<td>Filter index page by <code>?category=</code> URL parameter.</td>
</tr>
</tbody>
</table>
<p>If the configured page layout file does not exist, the packaged minimal <code>index.html</code> layout is used silently — no error.</p>
<h2 id="filename-conventions">Filename conventions</h2>
<p>The CLI does not hard-code kebab-case. Projects choose a convention with <strong><code>wiki.filename_pattern</code></strong>, matched against the <strong>full filename</strong> (including <code>.md</code>) on markdown files only.</p>
<p><strong>Wikipedia-style (recommended):</strong> preserved capitalization and underscores — <code>Gregory_Davidson.md</code>, <code>Pokemon_Diamond_(copy_1).md</code>, <code>LLM_Wiki_CLI.md</code>. Use a pattern such as:</p>
<pre data-copy="wiki:
  filename_pattern: "[A-Za-z0-9_()-]+\\.md"
" class="highlight"><code class="language-yaml"><span class="nt">wiki</span><span class="p">:</span>
<span class="w">  </span><span class="nt">filename_pattern</span><span class="p">:</span><span class="w"> </span><span class="s">"[A-Za-z0-9_()-]+\\.md"</span>
</code></pre>
<p><strong>Kebab-case (optional):</strong> if you prefer <code>gregory-house.md</code>, set an explicit pattern (for example <code>[a-z0-9-]+\\.md</code>) and enforce it via <code>lint.filename_pattern</code>. Wikipedia-style and kebab-case should not be mixed in one wiki.</p>
<p>Page routes keep the casing from the filename; GitHub Pages URLs are case-sensitive.</p>
<p><code>wiki link --fix-broken</code> preserves the existing link kind in each file; only <code>--apply</code> uses <code>link.style</code>.</p>
<p>When <code>link.style</code> is <code>standard</code>, <code>lint.link_style</code> (default <code>warning</code>) flags Obsidian wikilinks (<code>[[Page]]</code>) in body prose. Set <code>lint.link_style: off</code> to allow wikilinks while keeping standard links as the apply format, or set <code>link.style: wikilink</code> for an Obsidian-style wiki.</p>
<h2 id="formatting-fmt-1">Formatting (<code>fmt</code>)</h2>
<p>Top-level <strong><code>fmt</code></strong> configures <code>wiki fmt</code> (mdformat). Two shapes are allowed — not both:</p>
<table>
<thead>
<tr>
<th>Shape</th>
<th>Example</th>
<th>When to use</th>
</tr>
</thead>
<tbody>
<tr>
<td>Inline mapping</td>
<td><code>fmt: { wrap: "no" }</code></td>
<td>Default; what <code>wiki init</code> writes</td>
</tr>
<tr>
<td>Relative path</td>
<td><code>fmt: custom.toml</code></td>
<td>Share one TOML file or keep fmt out of yaml</td>
</tr>
</tbody>
</table>
<p>Omit <code>fmt</code> entirely to use fallbacks: <code>config_root/.mdformat.toml</code>, then upward search from each markdown file, then <strong>Wiki CLI fmt defaults</strong> (<code>wrap: "no"</code>, <code>end_of_line: lf</code>, extensions <code>gfm</code>, <code>frontmatter</code>, <code>wikilink</code>). See <a href="/Wiki_Subcommand_fmt/">Wiki Subcommand fmt</a> for the full resolution order.</p>
<p>Invalid inline keys or values fail when the config loads. Invalid TOML syntax fails when <code>wiki fmt</code> reads the file.</p>
<p>In library code, loaded <code>Config.fmt</code> is a <code>FmtConfig</code> with <code>options</code> (inline mapping) or <code>toml</code> (resolved path under <code>config_root</code>); yaml shapes above are unchanged.</p>
<h2 id="integrity-checks-check-1">Integrity checks (<code>check</code>)</h2>
<p>Under <code>check</code>, each rule is <code>error</code>, <code>warning</code>, or <code>off</code>:</p>
<table>
<thead>
<tr>
<th>Rule key</th>
<th>Default</th>
<th>What it audits</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>missing_layout_file</code></td>
<td><code>error</code></td>
<td><code>wazoo:layout</code> paths that do not resolve to a readable <code>.html</code> file</td>
</tr>
<tr>
<td><code>frontmatter_schema</code></td>
<td><code>error</code></td>
<td>Frontmatter that fails JSON Schema validation</td>
</tr>
<tr>
<td><code>missing_schema_ref</code></td>
<td><code>error</code></td>
<td><code>wazoo:jsonSchema</code> paths or URLs that cannot be loaded</td>
</tr>
<tr>
<td><code>remote_schema_refs</code></td>
<td><code>allow</code></td>
<td>Policy for remote <code>http(s)</code> schema refs: <code>allow</code>, <code>deny</code>, or <code>allowlist</code></td>
</tr>
<tr>
<td><code>remote_schema_hosts</code></td>
<td><code>[]</code></td>
<td>Hostnames permitted when <code>remote_schema_refs</code> is <code>allowlist</code></td>
</tr>
</tbody>
</table>
<p>Build-safety rules (unsafe URL characters, spaces in routes) and output URL collision detection always apply regardless of <code>check</code> settings.</p>
<h3 id="json-schema-frontmatter-wazoojsonschema-1">JSON Schema frontmatter (<code>wazoo:jsonSchema</code>)</h3>
<p><code>wiki check</code> validates frontmatter against JSON Schema in parallel with SHACL. Bind schemas on shape documents with <strong><code>wazoo:jsonSchema</code></strong> beside <strong><code>sh:targetClass</code></strong>; every page whose effective <code>type</code> matches that class must pass the bound schema(s). Individual pages may append extra schemas with their own <code>wazoo:jsonSchema</code> key (scalar or YAML list). Schema refs are local paths under the wiki config root (<code>.json</code> only) or remote <code>http(s)</code> URLs. Remote refs can trigger outbound network requests; set <code>check.remote_schema_refs: deny</code> in CI over untrusted wikis, or <code>allowlist</code> with <code>check.remote_schema_hosts</code> for trusted hosts only.</p>
<p>Shape binding documents are not validated as instances — only their schema refs are checked for loadability. Authoring detail: <a href="/SHACL/">SHACL</a>, <a href="/Style_Guide/">Style Guide</a>.</p>
<h2 id="convention-audits-lint-1">Convention audits (<code>lint</code>)</h2>
<p>Under <code>lint</code>, each rule is <code>error</code>, <code>warning</code>, or <code>off</code>:</p>
<table>
<thead>
<tr>
<th>Rule key</th>
<th>Default</th>
<th>What it audits</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>broken_links</code></td>
<td><code>warning</code></td>
<td>Wikilinks, internal markdown links, heading fragments, assets, <code>wiki:</code> CURIEs</td>
</tr>
<tr>
<td><code>filename_pattern</code></td>
<td><code>warning</code></td>
<td>Full filename vs <code>wiki.filename_pattern</code> regex</td>
</tr>
<tr>
<td><code>headings</code></td>
<td><code>off</code></td>
<td>ATX <code>#</code> headings only (no Setext underlines), sentence-case H2+, H1 title case conventional, numbered headings</td>
</tr>
<tr>
<td><code>thematic_breaks</code></td>
<td><code>off</code></td>
<td>Horizontal rules (<code>---</code>, <code>***</code>, <code>___</code>) in body prose</td>
</tr>
<tr>
<td><code>link_style</code></td>
<td><code>warning</code></td>
<td>Obsidian wikilinks (<code>[[Page]]</code>) in body prose when <code>link.style</code> is <code>standard</code></td>
</tr>
</tbody>
</table>
<h2 id="this-repository">This repository</h2>
<p><code>docs/wiki.yml</code> is the dogfood wiki config: the same structure, block order, and Init columns as <code>wiki init</code> (<a href="https://github.com/wazootech/wiki/blob/main/src/wiki/templates/wiki.yml"><code>wiki.yml</code></a>), plus dogfood overrides — <code>graph.context.wiki</code> for GitHub Pages and <code>graph.content_predicate: schema:articleBody</code> for SPARQL full-text.</p>
<h2 id="related">Related</h2>
<ul>
<li><a href="/Wiki_CLI/#global-options">Wiki CLI</a> — <code>-c</code> and <code>--wiki-inputs</code> global options</li>
<li><a href="/Wiki_Subcommand_init/">Wiki Subcommand init</a> — scaffold a new wiki project</li>
<li><a href="/Wiki_Subcommand_check/">Wiki Subcommand check</a> — integrity checks</li>
<li><a href="/Wiki_Subcommand_lint/">Wiki Subcommand lint</a> — convention audits</li>
<li><a href="/Wiki_Subcommand_query/">Wiki Subcommand query</a> — ad-hoc SPARQL</li>
<li><a href="/Wiki_Subcommand_render/">Wiki Subcommand render</a> — inline SPARQL tables</li>
<li><a href="/Wiki_Subcommand_serve/#sparql-endpoint">Wiki Subcommand serve</a> — <code>#serve-api</code> config block</li>
<li><a href="/Graph_Cache/">Graph Cache</a> — <code>--cache</code> and graph reuse</li>
<li><a href="/Style_Guide/">Style Guide</a> — shapes and frontmatter</li>
</ul>
`     | rendered markdown body | Pre-built HTML (not escaped)                                  |

**Packaged layouts**

| File         | When used                           | Typical slots                |
| ------------ | ----------------------------------- | ---------------------------- |
| `index.html` | `site.layout` unset or missing file | `<title>Wiki Configuration - Wiki</title>`, `<p>The CLI loads <strong>Config</strong> from <code>wiki.yml</code>, <code>wiki.yaml</code>, or <code>wiki.json</code> in the working directory (or from <code>-c path</code>).</p>
<p>The in-memory <strong>Config</strong> model uses the same nested blocks as the file (<code>wiki</code>, <code>graph</code>, <code>site</code>, <code>link</code>, <code>check</code>, <code>lint</code>, <code>fmt</code>, <code>sparql_service</code>). There is no separate flat runtime shape. <code>Config.load()</code> validates the file, injects <code>config_root</code> (the directory containing the config file), and resolves relative paths under <code>wiki</code> and <code>site</code>. Library and test code can construct configs with <code>Config(wiki={...}, config_root=path)</code> or <code>Config.for_root(path, wiki={...})</code>.</p>
<p>Config files are validated strictly through a Pydantic schema (<code>extra='forbid'</code> on every block). Unknown keys, removed aliases, wrong nested keys under <code>check</code>, <code>lint</code>, or <code>sparql_service</code>, invalid syntax, or a non-mapping top level all fail immediately instead of being ignored.</p>
<p>JSON configs may use <code>graph.context</code> or <code>graph.@context</code> for prefix maps (JSON-LD compatible).</p>
<h2 id="overview">Overview</h2>
<h3 id="terminology">Terminology</h3>
<table>
<thead>
<tr>
<th>Label</th>
<th>Meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Schema optional</strong></td>
<td>Key or block may be omitted; Pydantic applies a default. No yaml key is strictly required for <code>Config.load()</code> to succeed.</td>
</tr>
<tr>
<td><strong>Init</strong></td>
<td>Written by <code>wiki init</code> (<a href="https://github.com/wazootech/wiki/blob/main/src/wiki/templates/wiki.yml"><code>wiki.yml</code></a>); omitting an Init key is the same as the schema default.</td>
</tr>
<tr>
<td><strong>Recommended</strong></td>
<td>Not enforced by schema, but you typically set it for a real wiki (for example <code>graph.context.wiki</code>, <code>wiki.filename_pattern</code>, <code>site.layout</code>).</td>
</tr>
<tr>
<td><strong>Always on</strong></td>
<td>Behavior not gated by yaml severities (route safety, URL collisions, built-in RDF prefixes).</td>
</tr>
</tbody>
</table>
<h3 id="audit-lanes">Audit lanes</h3>
<p>Three audit lanes map to three commands:</p>
<table>
<thead>
<tr>
<th>Lane</th>
<th>Command</th>
<th>YAML block</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td>Integrity</td>
<td><code>wiki check</code></td>
<td><code>check:</code></td>
<td>SHACL, JSON Schema frontmatter, layout file existence</td>
</tr>
<tr>
<td>Convention</td>
<td><code>wiki lint</code></td>
<td><code>lint:</code></td>
<td>Links, filename pattern severity, headings, link style in prose</td>
</tr>
<tr>
<td>Formatting</td>
<td><code>wiki fmt</code></td>
<td><code>fmt:</code></td>
<td>Mechanical markdown (mdformat; inline mapping or TOML path)</td>
</tr>
</tbody>
</table>
<p><strong>Rule placement:</strong> Mechanical markdown belongs under <strong><code>fmt:</code></strong>. Wiki policy and link conventions belong under <strong><code>lint:</code></strong>. SHACL, JSON Schema, and layout keys belong under <strong><code>check:</code></strong> — never under <code>lint:</code>. See <a href="/Style_Guide/">Style Guide</a> for the full matrix.</p>
<ul>
<li>Putting a regex under <code>check.filename_pattern</code> fails at load with a hint.</li>
<li><code>check.filename_pattern</code> and <code>check.headings</code> fail at load — use <code>lint.filename_pattern</code> and <code>lint.headings</code>.</li>
</ul>
<p>Relative <strong><code>--wiki-inputs</code></strong> paths on the CLI resolve against the config file directory (same as paths in yaml), not the shell cwd.</p>
<h3 id="blocks">Blocks</h3>
<p>Top-level blocks follow a <strong>compile pipeline</strong> plus <strong>audit lanes</strong>, not arbitrary grouping. <code>wiki init</code> and <a href="https://github.com/wazootech/wiki/blob/main/docs/wiki.yml">docs/wiki.yml</a> use the same order as the packaged scaffold <a href="https://github.com/wazootech/wiki/blob/main/src/wiki/templates/wiki.yml"><code>wiki.yml</code></a>.</p>
<table>
<thead>
<tr>
<th>Block</th>
<th>Role</th>
<th>Command(s)</th>
<th>Schema</th>
<th>Init scaffold</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>wiki:</code></td>
<td>Corpus on disk — inputs, assets, filename regex</td>
<td><code>check</code>, <code>lint</code>, <code>build</code>, <code>serve</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>graph:</code></td>
<td>RDF compile — prefixes, document IRIs, body literals</td>
<td><code>check</code>, <code>query</code>, <code>render</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>site:</code></td>
<td>Publish routing — layout path, URL prefix, path style</td>
<td><code>build</code>, <code>serve</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>link:</code></td>
<td><code>wiki link</code> apply format and rename repair map</td>
<td><code>wiki link</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>check:</code></td>
<td>Integrity severities</td>
<td><code>wiki check</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>lint:</code></td>
<td>Convention severities</td>
<td><code>wiki lint</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>sparql_service:</code></td>
<td>Opt-in SPARQL HTTP on <code>wiki serve</code></td>
<td><code>wiki serve</code></td>
<td>optional</td>
<td>commented example</td>
</tr>
<tr>
<td><code>fmt:</code></td>
<td>Mechanical markdown via mdformat</td>
<td><code>wiki fmt</code></td>
<td>optional</td>
<td>inline mapping</td>
</tr>
</tbody>
</table>
<p><strong>Order in the file:</strong> source and semantics first (<code>wiki</code>, <code>graph</code>), then publish and authoring (<code>site</code>, <code>link</code>), then severity tables (<code>check</code>, <code>lint</code>), optional serve (<code>sparql_service</code>), then <code>fmt</code> last.</p>
<p><strong>Split keys</strong> — policy lives in one block, severity or tooling in another:</p>
<ul>
<li><strong><code>wiki.filename_pattern</code></strong> — the regex string. <strong><code>lint.filename_pattern</code></strong> — how strictly to flag violations (<code>error</code>, <code>warning</code>, or <code>off</code>).</li>
<li><strong><code>link.style</code></strong> — what <code>wiki link --apply</code> inserts (<code>standard</code> page links or <code>wikilink</code>). <strong><code>lint.link_style</code></strong> — whether Obsidian <code>[[wikilinks]]</code> in body prose are flagged when <code>link.style</code> is <code>standard</code>.</li>
</ul>
<p>For why <code>check</code>, <code>lint</code>, <code>fmt</code>, and <code>wiki link</code> are separate commands, see <a href="/Design_Philosophies/#check-lint-fmt-and-link">Design philosophies</a>.</p>
<h3 id="always-on">Always on</h3>
<p>These apply regardless of yaml severities:</p>
<ul>
<li><strong>Route safety</strong> — unsafe URL characters and spaces in routes (<code>wiki check</code>).</li>
<li><strong>Output URL collisions</strong> — duplicate built routes (<code>wiki check</code>).</li>
<li><strong>SHACL</strong> — when shape documents exist in the corpus (<code>wiki check</code>).</li>
<li><strong>Built-in RDF prefixes</strong> — <code>schema</code>, <code>wiki</code>, <code>foaf</code>, <code>rdf</code>, <code>rdfs</code>, <code>xsd</code>, <code>owl</code>, <code>dc</code>, <code>dcterms</code>, <code>sh</code>, <code>wazoo</code> are always merged at runtime; yaml <code>graph.context</code> entries override or add.</li>
</ul>
<h2 id="wiki-wiki">Wiki (<code>wiki:</code>)</h2>
<pre data-copy="wiki:  # optional block
  inputs: [wiki]                    # default [wiki]; init writes
  assets: [assets]                  # default [assets] if assets/ exists, else []; init writes
  exclude: []                         # default []; init omits
  filename_pattern: "[A-Za-z0-9_()-]+\\.md"  # no default; recommended; init writes
" class="highlight"><code class="language-yaml"><span class="nt">wiki</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">inputs</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[</span><span class="nv">wiki</span><span class="p p-Indicator">]</span><span class="w">                    </span><span class="c1"># default [wiki]; init writes</span>
<span class="w">  </span><span class="nt">assets</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[</span><span class="nv">assets</span><span class="p p-Indicator">]</span><span class="w">                  </span><span class="c1"># default [assets] if assets/ exists, else []; init writes</span>
<span class="w">  </span><span class="nt">exclude</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[]</span><span class="w">                         </span><span class="c1"># default []; init omits</span>
<span class="w">  </span><span class="nt">filename_pattern</span><span class="p">:</span><span class="w"> </span><span class="s">"[A-Za-z0-9_()-]+\\.md"</span><span class="w">  </span><span class="c1"># no default; recommended; init writes</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>inputs</code></td>
<td>optional</td>
<td><code>[wiki]</code></td>
<td>writes</td>
<td>indexing (<code>build</code>, <code>check</code>, <code>lint</code>, <code>fmt</code>)</td>
</tr>
<tr>
<td><code>assets</code></td>
<td>optional</td>
<td><code>[assets]</code> when <code>assets/</code> exists, else <code>[]</code></td>
<td>writes</td>
<td><code>wiki build</code> (static copy)</td>
</tr>
<tr>
<td><code>exclude</code></td>
<td>optional</td>
<td><code>[]</code></td>
<td>omits</td>
<td>indexing (skipped paths)</td>
</tr>
<tr>
<td><code>filename_pattern</code></td>
<td>optional (recommended)</td>
<td>unset — no regex check until set</td>
<td>writes</td>
<td><code>wiki lint</code> (<code>lint.filename_pattern</code>)</td>
</tr>
</tbody>
</table>
<p>Page URLs come from paths under <code>wiki.inputs</code>: <code>wiki/Alice.md</code> → <code>/wiki/Alice/</code> with default <code>site.base_url</code> and <code>site.url_style: dir</code>. <code>index.md</code> in a folder owns that folder’s route (for example <code>wiki/index.md</code> → <code>/wiki/</code>).</p>
<p>See <a href="#filename-conventions">Filename conventions</a> for regex patterns.</p>
<h2 id="graph-graph">Graph (<code>graph:</code>)</h2>
<p>RDF and document URI settings for graph build, <code>wiki query</code>, microdata, and SHACL.</p>
<pre data-copy="graph:  # optional block
  # base_iri: unset → graph.context.wiki → https://wiki.example.org/
  content_predicate: schema:articleBody   # unset by default; init writes when flagged
  include_file_extension: false           # default false; init omits (commented)
  implicit_types: []                      # default []; init omits (commented)
  implicit_types_policy: fallback         # default fallback; init omits (commented)
  context:                                # merges with built-in prefixes; init writes
    schema: https://schema.org/
    wiki: https://example.org/wiki/       # recommended
    wazoo: https://schema.wazoo.dev/
    foaf: http://xmlns.com/foaf/0.1/
    dc: http://purl.org/dc/elements/1.1/
    dcterms: http://purl.org/dc/terms/
    sh: http://www.w3.org/ns/shacl#
    xsd: http://www.w3.org/2001/XMLSchema#
" class="highlight"><code class="language-yaml"><span class="nt">graph</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="c1"># base_iri: unset → graph.context.wiki → https://wiki.example.org/</span>
<span class="w">  </span><span class="nt">content_predicate</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">schema:articleBody</span><span class="w">   </span><span class="c1"># unset by default; init writes when flagged</span>
<span class="w">  </span><span class="nt">include_file_extension</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">false</span><span class="w">           </span><span class="c1"># default false; init omits (commented)</span>
<span class="w">  </span><span class="nt">implicit_types</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[]</span><span class="w">                      </span><span class="c1"># default []; init omits (commented)</span>
<span class="w">  </span><span class="nt">implicit_types_policy</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">fallback</span><span class="w">         </span><span class="c1"># default fallback; init omits (commented)</span>
<span class="w">  </span><span class="nt">context</span><span class="p">:</span><span class="w">                                </span><span class="c1"># merges with built-in prefixes; init writes</span>
<span class="w">    </span><span class="nt">schema</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">https://schema.org/</span>
<span class="w">    </span><span class="nt">wiki</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">https://example.org/wiki/</span><span class="w">       </span><span class="c1"># recommended</span>
<span class="w">    </span><span class="nt">wazoo</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">https://schema.wazoo.dev/</span>
<span class="w">    </span><span class="nt">foaf</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">http://xmlns.com/foaf/0.1/</span>
<span class="w">    </span><span class="nt">dc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">http://purl.org/dc/elements/1.1/</span>
<span class="w">    </span><span class="nt">dcterms</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">http://purl.org/dc/terms/</span>
<span class="w">    </span><span class="nt">sh</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">http://www.w3.org/ns/shacl#</span>
<span class="w">    </span><span class="nt">xsd</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">http://www.w3.org/2001/XMLSchema#</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>base_iri</code></td>
<td>optional</td>
<td>unset → <code>graph.context.wiki</code> → <code>https://wiki.example.org/</code></td>
<td>commented example</td>
<td>document IRIs, <code>wiki query</code></td>
</tr>
<tr>
<td><code>context</code> / <code>@context</code></td>
<td>optional (recommended: <code>wiki</code>)</td>
<td>built-in prefixes only when unset</td>
<td>writes extended map</td>
<td>CURIE expansion, SHACL, microdata</td>
</tr>
<tr>
<td><code>content_predicate</code></td>
<td>optional</td>
<td>unset — no body literals in graph</td>
<td>writes when <code>--graph-content-predicate</code></td>
<td>SPARQL full-text</td>
</tr>
<tr>
<td><code>include_file_extension</code></td>
<td>optional</td>
<td><code>false</code></td>
<td>omits (commented)</td>
<td>document URI generation</td>
</tr>
<tr>
<td><code>implicit_types</code></td>
<td>optional</td>
<td><code>[]</code></td>
<td>omits (commented)</td>
<td>default <code>rdf:type</code> on untyped pages</td>
</tr>
<tr>
<td><code>implicit_types_policy</code></td>
<td>optional</td>
<td><code>fallback</code></td>
<td>omits (commented)</td>
<td><code>fallback</code> or <code>append</code> (SHACL shapes skip append)</td>
</tr>
</tbody>
</table>
<p>When <code>implicit_types_policy</code> is <code>append</code>, frontmatter types are unioned with <code>implicit_types</code> (deduped by resolved URI).</p>
<h2 id="site-site">Site (<code>site:</code>)</h2>
<p>Default page layout and routing for <code>wiki build</code> / <code>wiki serve</code>. Branding and chrome → <a href="#page-layout">Page layout</a>.</p>
<pre data-copy="site:  # optional block
  layout: index.html   # unset → built-in minimal fallback layout
  base_url: /wiki                   # default /wiki; init writes
  url_style: dir                    # default dir; init writes
" class="highlight"><code class="language-yaml"><span class="nt">site</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">layout</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">index.html</span><span class="w">   </span><span class="c1"># unset → built-in minimal fallback layout</span>
<span class="w">  </span><span class="nt">base_url</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">/wiki</span><span class="w">                   </span><span class="c1"># default /wiki; init writes</span>
<span class="w">  </span><span class="nt">url_style</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">dir</span><span class="w">                    </span><span class="c1"># default dir; init writes</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>layout</code></td>
<td>optional (recommended)</td>
<td>unset — packaged minimal <code>index.html</code></td>
<td>writes</td>
<td><code>wiki build</code>, <code>wiki serve</code>; <code>check.missing_layout_file</code> for per-page <code>wazoo:layout</code></td>
</tr>
<tr>
<td><code>base_url</code></td>
<td>optional</td>
<td><code>/wiki</code> (<code>""</code> allowed for site root)</td>
<td>writes</td>
<td>routes, layout <code>%wiki.base_url%</code></td>
</tr>
<tr>
<td><code>url_style</code></td>
<td>optional</td>
<td><code>dir</code> (<code>file</code> → <code>slug.html</code>)</td>
<td>writes</td>
<td>output paths; overridable per CLI run</td>
</tr>
</tbody>
</table>
<p><code>site:</code> does not carry site name, theme color, favicon, or sidebar logo. If you want custom styling, write a custom layout template file and place custom assets under the <code>wiki.assets</code> directory, then configure <code>site.layout</code> to point to it.</p>
<p>CLI flags on <code>wiki build</code> and <code>wiki serve</code> can override <code>site.base_url</code> and <code>site.url_style</code> for a single run.</p>
<h2 id="link-link">Link (<code>link:</code>)</h2>
<p>Settings for the <code>wiki link</code> command family (separate from <code>lint.link_style</code> severity).</p>
<pre data-copy="link:  # optional block
  style: standard       # default standard; init writes
  renames: {}           # default {}; init omits (commented example)
" class="highlight"><code class="language-yaml"><span class="nt">link</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">style</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">standard</span><span class="w">       </span><span class="c1"># default standard; init writes</span>
<span class="w">  </span><span class="nt">renames</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">{}</span><span class="w">           </span><span class="c1"># default {}; init omits (commented example)</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>style</code></td>
<td>optional</td>
<td><code>standard</code> (<code>wikilink</code> for wikilinks)</td>
<td>writes</td>
<td><code>wiki link --apply</code> only</td>
</tr>
<tr>
<td><code>renames</code></td>
<td>optional</td>
<td><code>{}</code></td>
<td>commented example</td>
<td><code>wiki link --fix-broken</code></td>
</tr>
</tbody>
</table>
<p><code>wiki link --fix-broken</code> preserves the existing link kind in each file; only <code>--apply</code> uses <code>link.style</code>.</p>
<h2 id="integrity-checks-check">Integrity checks (<code>check:</code>)</h2>
<p>Under <code>check</code>, each rule is <code>error</code>, <code>warning</code>, or <code>off</code>:</p>
<pre data-copy="check:  # optional block
  missing_layout_file: error    # default error; init writes
  frontmatter_schema: error     # default error; init writes
  missing_schema_ref: error   # default error; init writes
" class="highlight"><code class="language-yaml"><span class="nt">check</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">missing_layout_file</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">error</span><span class="w">    </span><span class="c1"># default error; init writes</span>
<span class="w">  </span><span class="nt">frontmatter_schema</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">error</span><span class="w">     </span><span class="c1"># default error; init writes</span>
<span class="w">  </span><span class="nt">missing_schema_ref</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">error</span><span class="w">   </span><span class="c1"># default error; init writes</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>missing_layout_file</code></td>
<td>optional</td>
<td><code>error</code></td>
<td>writes</td>
<td><code>wazoo:layout</code> paths missing on disk</td>
</tr>
<tr>
<td><code>frontmatter_schema</code></td>
<td>optional</td>
<td><code>error</code></td>
<td>writes</td>
<td>JSON Schema validation failures</td>
</tr>
<tr>
<td><code>missing_schema_ref</code></td>
<td>optional</td>
<td><code>error</code></td>
<td>writes</td>
<td>unloadable <code>wazoo:jsonSchema</code> refs</td>
</tr>
</tbody>
</table>
<p>Build-safety rules (unsafe URL characters, spaces in routes) and output URL collision detection always apply regardless of <code>check</code> settings.</p>
<h3 id="json-schema-frontmatter-wazoojsonschema">JSON Schema frontmatter (<code>wazoo:jsonSchema</code>)</h3>
<p><code>wiki check</code> validates frontmatter against JSON Schema in parallel with SHACL. Bind schemas on shape documents with <strong><code>wazoo:jsonSchema</code></strong> beside <strong><code>sh:targetClass</code></strong>; every page whose effective <code>type</code> matches that class must pass the bound schema(s). Individual pages may append extra schemas with their own <code>wazoo:jsonSchema</code> key (scalar or YAML list). Schema refs are local paths under the wiki config root (<code>.json</code> only) or remote <code>http(s)</code> URLs.</p>
<p>Shape binding documents are not validated as instances — only their schema refs are checked for loadability. Authoring detail: <a href="/SHACL/">SHACL</a>, <a href="/Style_Guide/">Style Guide</a>.</p>
<h2 id="convention-audits-lint">Convention audits (<code>lint:</code>)</h2>
<p>Under <code>lint</code>, each rule is <code>error</code>, <code>warning</code>, or <code>off</code>:</p>
<pre data-copy="lint:  # optional block
  broken_links: warning       # default warning; init writes
  filename_pattern: warning   # default warning; init writes
  headings: off               # default off; init omits
  heading_levels: off         # default off; init omits
  duplicate_headings: off     # default off; init omits
  thematic_breaks: off        # default off; init omits
  link_style: warning         # default warning; init writes
" class="highlight"><code class="language-yaml"><span class="nt">lint</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">broken_links</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">warning</span><span class="w">       </span><span class="c1"># default warning; init writes</span>
<span class="w">  </span><span class="nt">filename_pattern</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">warning</span><span class="w">   </span><span class="c1"># default warning; init writes</span>
<span class="w">  </span><span class="nt">headings</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">off</span><span class="w">               </span><span class="c1"># default off; init omits</span>
<span class="w">  </span><span class="nt">heading_levels</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">off</span><span class="w">         </span><span class="c1"># default off; init omits</span>
<span class="w">  </span><span class="nt">duplicate_headings</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">off</span><span class="w">     </span><span class="c1"># default off; init omits</span>
<span class="w">  </span><span class="nt">thematic_breaks</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">off</span><span class="w">        </span><span class="c1"># default off; init omits</span>
<span class="w">  </span><span class="nt">link_style</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">warning</span><span class="w">         </span><span class="c1"># default warning; init writes</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>broken_links</code></td>
<td>optional</td>
<td><code>warning</code></td>
<td>writes</td>
<td>wikilinks, markdown links, fragments, assets, <code>wiki:</code> CURIEs</td>
</tr>
<tr>
<td><code>filename_pattern</code></td>
<td>optional</td>
<td><code>warning</code></td>
<td>writes</td>
<td>full filename vs <code>wiki.filename_pattern</code></td>
</tr>
<tr>
<td><code>headings</code></td>
<td>optional</td>
<td><code>off</code></td>
<td>omits</td>
<td>ATX syntax, sentence-case H2+, numbered headings</td>
</tr>
<tr>
<td><code>heading_levels</code></td>
<td>optional</td>
<td><code>off</code></td>
<td>omits</td>
<td>heading level gaps (for example H1 then H3)</td>
</tr>
<tr>
<td><code>duplicate_headings</code></td>
<td>optional</td>
<td><code>off</code></td>
<td>omits</td>
<td>duplicate heading text on one page</td>
</tr>
<tr>
<td><code>thematic_breaks</code></td>
<td>optional</td>
<td><code>off</code></td>
<td>omits</td>
<td>horizontal rules in body prose</td>
</tr>
<tr>
<td><code>link_style</code></td>
<td>optional</td>
<td><code>warning</code></td>
<td>writes</td>
<td>Obsidian <code>[[wikilinks]]</code> when <code>link.style</code> is <code>standard</code></td>
</tr>
</tbody>
</table>
<p>ATX heading syntax is also enforced by <strong><code>wiki fmt</code></strong> (mdformat); Setext underlines are converted on format.</p>
<p>When <code>link.style</code> is <code>standard</code>, set <code>lint.link_style: off</code> to allow wikilinks in prose, or set <code>link.style: wikilink</code> for an Obsidian-style wiki.</p>
<h2 id="serve-api">Serve API</h2>
<p>Opt-in read-only SPARQL HTTP endpoint on <code>wiki serve</code>:</p>
<pre data-copy="sparql_service:  # optional block
  enabled: false        # default false; init omits (commented)
  path: /api/sparql     # default /api/sparql; init omits (commented)
" class="highlight"><code class="language-yaml"><span class="nt">sparql_service</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">enabled</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">false</span><span class="w">        </span><span class="c1"># default false; init omits (commented)</span>
<span class="w">  </span><span class="nt">path</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">/api/sparql</span><span class="w">     </span><span class="c1"># default /api/sparql; init omits (commented)</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>enabled</code></td>
<td>optional</td>
<td><code>false</code></td>
<td>commented example</td>
<td><code>wiki serve</code> SPARQL endpoint</td>
</tr>
<tr>
<td><code>path</code></td>
<td>optional</td>
<td><code>/api/sparql</code></td>
<td>commented example</td>
<td>reserved route on serve</td>
</tr>
</tbody>
</table>
<p><code>sparql_service.enabled</code> accepts YAML booleans and normalizes common string forms such as <code>true</code>, <code>false</code>, <code>on</code>, <code>off</code>, <code>yes</code>, <code>no</code>, <code>1</code>, and <code>0</code>; prefer native YAML booleans.</p>
<p>Example when enabled:</p>
<pre data-copy="sparql_service:
  enabled: true
  path: /api/sparql
" class="highlight"><code class="language-yaml"><span class="nt">sparql_service</span><span class="p">:</span>
<span class="w">  </span><span class="nt">enabled</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">true</span>
<span class="w">  </span><span class="nt">path</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">/api/sparql</span>
</code></pre>
<p>The endpoint reuses the same SPARQL engine as <code>wiki query</code>. It is read-only and intended for local or development-oriented use. HTTP request forms, supported query types, and <code>Accept</code> negotiation are documented in <a href="/Wiki_Subcommand_serve/#sparql-endpoint">Wiki Subcommand serve</a>.</p>
<p>It is <strong>opt-in by default</strong> because enabling it exposes raw graph-query access in addition to HTML preview.</p>
<p><code>sparql_service.path</code> must not collide with the effective <code>site.base_url</code> page routes or the watch endpoint. Invalid values such as <code>/</code>, <code>/wiki</code>, <code>/wiki/foo</code>, or <code>/wiki/__watch</code> are rejected when <code>wiki serve</code> starts.</p>
<h2 id="formatting-fmt">Formatting (<code>fmt</code>)</h2>
<p>Top-level <strong><code>fmt</code></strong> configures <code>wiki fmt</code> (mdformat). Two shapes are allowed — not both:</p>
<pre data-copy="fmt:  # optional block — inline mapping (init writes)
  wrap: "no"
  end_of_line: lf
  extensions: [gfm, frontmatter, wikilink]

# Pointer mode (optional alternative):
# fmt: .mdformat.toml
" class="highlight"><code class="language-yaml"><span class="nt">fmt</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block — inline mapping (init writes)</span>
<span class="w">  </span><span class="nt">wrap</span><span class="p">:</span><span class="w"> </span><span class="s">"no"</span>
<span class="w">  </span><span class="nt">end_of_line</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">lf</span>
<span class="w">  </span><span class="nt">extensions</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[</span><span class="nv">gfm</span><span class="p p-Indicator">,</span><span class="w"> </span><span class="nv">frontmatter</span><span class="p p-Indicator">,</span><span class="w"> </span><span class="nv">wikilink</span><span class="p p-Indicator">]</span>

<span class="c1"># Pointer mode (optional alternative):</span>
<span class="c1"># fmt: .mdformat.toml</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key / shape</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>wrap</code></td>
<td>optional (inline)</td>
<td><code>"no"</code></td>
<td>writes</td>
<td><code>wiki fmt</code></td>
</tr>
<tr>
<td><code>end_of_line</code></td>
<td>optional (inline)</td>
<td><code>lf</code></td>
<td>writes</td>
<td><code>wiki fmt</code></td>
</tr>
<tr>
<td><code>extensions</code></td>
<td>optional (inline)</td>
<td><code>[gfm, frontmatter, wikilink]</code></td>
<td>writes</td>
<td><code>wiki fmt</code></td>
</tr>
<tr>
<td>TOML path</td>
<td>optional</td>
<td>unset — see fallback chain below</td>
<td>omits (commented)</td>
<td><code>wiki fmt</code></td>
</tr>
</tbody>
</table>
<p>Omit <code>fmt</code> entirely to use fallbacks: <code>config_root/.mdformat.toml</code>, then upward search from each markdown file, then <strong>Wiki CLI fmt defaults</strong> (same as inline defaults above). See <a href="/Wiki_Subcommand_fmt/">Wiki Subcommand fmt</a> for the full resolution order.</p>
<table>
<thead>
<tr>
<th>Shape</th>
<th>Example</th>
<th>When to use</th>
</tr>
</thead>
<tbody>
<tr>
<td>Inline mapping</td>
<td><code>fmt: { wrap: "no" }</code></td>
<td>Default; what <code>wiki init</code> writes</td>
</tr>
<tr>
<td>Relative path</td>
<td><code>fmt: custom.toml</code></td>
<td>Share one TOML file or keep fmt out of yaml</td>
</tr>
</tbody>
</table>
<p>Invalid inline keys or values fail when the config loads. Invalid TOML syntax fails when <code>wiki fmt</code> reads the file.</p>
<p>In library code, loaded <code>Config.fmt</code> is a <code>FmtConfig</code> with <code>options</code> (inline mapping) or <code>toml</code> (resolved path under <code>config_root</code>).</p>
<h2 id="page-layout">Page layout</h2>
<p>When <code>site.layout</code> is set, the CLI renders every page through that page layout (<code>.html</code>). Per-page overrides use <code>wazoo:layout</code> in frontmatter; see <a href="/Wiki_Page_Layouts/">Wiki Page Layouts</a>.</p>
<h3 id="layout-strategy">Layout strategy</h3>
<p>The first-class presentation contract in this repository is layout files referenced from <code>site.layout</code> (for example <code>index.html</code>).</p>
<ul>
<li>The <a href="/Wiki_CLI/">Wiki CLI</a> owns the semantic markdown-to-HTML pipeline and layout slot contract.</li>
<li>Wiki page layout files are the primary built-in extension point for presentation.</li>
<li>Advanced themes or framework-specific sites such as Next.js, Mintlify, or other external docs stacks are treated as downstream integrations or separate layout/template repositories.</li>
</ul>
<h3 id="minimal-fallback">Minimal fallback</h3>
<p>Without a configured layout file (or when the path is missing), every page is rendered with the built-in minimal fallback layout (<code>index.html</code>), which outputs plain, unstyled HTML containing only <code><h1></code> and content. It does not link any default CSS or assets and does not include a sidebar, tabs, infobox, table of contents, backlinks, or categories out-of-the-box.</p>
<h3 id="layout-slots">Layout slots</h3>
<p>Layout files use <code>%wiki.*%</code> slot substitution (not Jinja). On each page render, the CLI builds a slot map from the current page context and replaces every known slot in your layout file. Unknown <code>%wiki.*%</code> spellings are left unchanged.</p>
<p>Programmatic consumers and contract tests use <code>wiki.site.layout_tokens.build_layout_token_map</code> as the single boundary for slot production. See <a href="/Wiki_Programmatic_API/#layout-slot-contract">Wiki Programmatic API</a>.</p>
<p>Canonical slot list (3 slots):</p>
<table>
<thead>
<tr>
<th>Slot</th>
<th>Source</th>
<th>Substitution</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>%wiki.base_url%</code></td>
<td><code>site.base_url</code></td>
<td>HTML-escaped text (<code>/wiki</code>, or <code>""</code> for site root)</td>
</tr>
<tr>
<td><code><title>Wiki Configuration - Wiki</title></code></td>
<td>built per page</td>
<td><code><title>{page title} - Wiki CLI</title></code> (title HTML-escaped)</td>
</tr>
<tr>
<td><code>%wiki.body%</code></td>
<td>rendered markdown body</td>
<td>Pre-built HTML (not escaped)</td>
</tr>
</tbody>
</table>
<p><strong>Packaged layouts</strong></p>
<table>
<thead>
<tr>
<th>File</th>
<th>When used</th>
<th>Typical slots</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>index.html</code></td>
<td><code>site.layout</code> unset or missing file</td>
<td><code><title>Wiki Configuration - Wiki</title></code>, <code>%wiki.body%</code></td>
</tr>
</tbody>
</table>
<p>Example excerpt (<code>index.html</code>):</p>
<pre data-copy="<!DOCTYPE html>
<html lang=en>
<head>
<meta charset=UTF-8>
<meta name=viewport content=width=device-width,initial-scale=1.0>
<title>Wiki Configuration - Wiki</title>
</head>
<body>
%wiki.body%
</body>
</html>
" class="highlight"><code class="language-html"><span class="cp"><!DOCTYPE html></span>
<span class="p"><</span><span class="nt">html</span> <span class="na">lang</span><span class="o">=</span><span class="s">en</span><span class="p">></span>
<span class="p"><</span><span class="nt">head</span><span class="p">></span>
<span class="p"><</span><span class="nt">meta</span> <span class="na">charset</span><span class="o">=</span><span class="s">UTF-8</span><span class="p">></span>
<span class="p"><</span><span class="nt">meta</span> <span class="na">name</span><span class="o">=</span><span class="s">viewport</span> <span class="na">content</span><span class="o">=</span><span class="s">width=device-width,initial-scale=1.0</span><span class="p">></span>
<title>Wiki Configuration - Wiki</title>
<span class="p"></</span><span class="nt">head</span><span class="p">></span>
<span class="p"><</span><span class="nt">body</span><span class="p">></span>
%wiki.body%
<span class="p"></</span><span class="nt">body</span><span class="p">></span>
<span class="p"></</span><span class="nt">html</span><span class="p">></span>
</code></pre>
<h3 id="custom-css">Custom CSS</h3>
<p>The Wiki CLI does not copy or link a default stylesheet out-of-the-box. To add styling to your pages:</p>
<ol>
<li><strong>Edit the layout file</strong> — set <code>site.layout</code> in <code>wiki.yml</code> to a custom layout file. Link stylesheets in <code><head></code>, or write inline styles.</li>
<li><strong>Link wiki assets</strong> — place <code>.css</code> files under a directory listed in <code>wiki.assets</code>, then reference them from the layout, for example <code><link rel="stylesheet" href="%wiki.base_url%/assets/site.css"></code>. Built assets are served at <code>%wiki.base_url%/assets/…</code> during <code>wiki serve</code> and copied into the build output.</li>
</ol>
<h3 id="custom-logos-and-icons">Custom logos and icons</h3>
<p>To customize site logos, icons, favicons, or touch icons:</p>
<ol>
<li>Place your asset files (such as <code>logo.svg</code>, <code>logo.png</code>, <code>favicon.ico</code>) under a directory listed in <code>wiki.assets</code>.</li>
<li>Reference the assets from your custom layout file, for example:</li>
</ol>
<pre data-copy="<img src="%wiki.base_url%/assets/logo.svg" alt="" width="80" height="80">
" class="highlight"><code class="language-html"><span class="p"><</span><span class="nt">img</span> <span class="na">src</span><span class="o">=</span><span class="s">"%wiki.base_url%/assets/logo.svg"</span> <span class="na">alt</span><span class="o">=</span><span class="s">""</span> <span class="na">width</span><span class="o">=</span><span class="s">"80"</span> <span class="na">height</span><span class="o">=</span><span class="s">"80"</span><span class="p">></span>
</code></pre>
<p>You can also add <code><link rel="icon"></code>, <code><link rel="apple-touch-icon"></code>, or other <code><head></code> tags directly in your custom layout file.</p>
<p>Built assets are served at <code>%wiki.base_url%/assets/…</code> during <code>wiki serve</code> and copied into the build output.</p>
<p>See also <a href="/Wiki_Page_Layouts/">Wiki Page Layouts</a> for <code>site.layout</code>, <code>wazoo:layout</code>, and packaged layout files.</p>
<p>The metadata pane uses the same RDF serialization path as <code>wiki export</code> (compacted JSON-LD, Turtle, N3, RDF/XML, N-Triples, TriG, N-Quads). A compact <strong>Format</strong> chip row switches views without JavaScript. In <code>wiki serve</code>, set the initial chip with <code>?metadata_format=FORMAT</code> (for example <code>turtle</code> or <code>json-ld</code>). In <code>wiki build</code>, all format views are embedded in the page HTML so the picker works offline.</p>
<h3 id="built-in-css-classes-and-ids">Built-in CSS classes and IDs</h3>
<p>The wiki builder generates these selectors in the rendered page content:</p>
<table>
<thead>
<tr>
<th>Selector</th>
<th>Where</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>#article-top</code></td>
<td>Read-view <code><article></code> wrapper around rendered markdown body.</td>
</tr>
<tr>
<td><code>#firstHeading</code></td>
<td>Read-view page title <code><h1></code>; also Talk / Source / Metadata pane headings. TOC “(Top)” links here.</td>
</tr>
<tr>
<td><code>#siteSub</code></td>
<td>Subtitle under Talk / Source / Metadata pane headings.</td>
</tr>
<tr>
<td><code>article</code></td>
<td>Wrapper around the rendered markdown body (<code>#article-top</code>).</td>
</tr>
<tr>
<td><code>.layout-label</code></td>
<td>Uppercase type or custom-layout badge in read view.</td>
</tr>
<tr>
<td><code>.toc</code> / <code>#toc</code></td>
<td>Table of contents container.</td>
</tr>
<tr>
<td><code>#catlinks</code> / <code>.catlinks</code></td>
<td>Category links box.</td>
</tr>
<tr>
<td><code>.backlinks</code> / <code>#backlinks</code></td>
<td>Backlinks section.</td>
</tr>
<tr>
<td><code>.catlinks-label</code></td>
<td>Categories heading label.</td>
</tr>
<tr>
<td><code>.catlinks-list</code></td>
<td>Categories <code><ul></code>.</td>
</tr>
<tr>
<td><code>.infobox</code></td>
<td>Typed frontmatter property table.</td>
</tr>
<tr>
<td><code>.page-meta</code></td>
<td>Infobox class (used for styling).</td>
</tr>
<tr>
<td><code>.template-SLUG</code></td>
<td>Per-template class on infobox (e.g. <code>template-person</code>).</td>
</tr>
<tr>
<td><code>toclevel-N</code> / <code>lN</code></td>
<td>TOC list item classes for heading level N.</td>
</tr>
<tr>
<td><code>.wikilink</code></td>
<td>Internal wiki page links.</td>
</tr>
<tr>
<td><code>pre[data-copy]</code></td>
<td>Block code with raw source for clipboard copy.</td>
</tr>
<tr>
<td><code>.code-block</code></td>
<td>Wrapper injected around copyable pre blocks.</td>
</tr>
<tr>
<td><code>.code-copy-btn</code></td>
<td>Copy button shown on code-block hover/focus.</td>
</tr>
</tbody>
</table>
<h3 id="javascript-hooks">JavaScript hooks</h3>
<p>Custom layout files can utilize standard JavaScript hooks or customize their own. In premium layouts (such as template repositories), the following JavaScript features can be implemented:</p>
<table>
<thead>
<tr>
<th>Function</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>switchTab(viewName)</code></td>
<td>Switch between read / talk / source / metadata tabs.</td>
</tr>
<tr>
<td><code>loadTalkNotes()</code></td>
<td>Load per-page local-storage notes.</td>
</tr>
<tr>
<td><code>saveTalkNotes()</code></td>
<td>Save per-page notes to localStorage.</td>
</tr>
<tr>
<td><code>clearTalkNotes()</code></td>
<td>Clear per-page notes.</td>
</tr>
<tr>
<td><code>copySourceCode()</code></td>
<td>Copy markdown source to clipboard.</td>
</tr>
<tr>
<td><code>copyPreContent()</code></td>
<td>Copy a <code>pre[data-copy]</code> block to clipboard.</td>
</tr>
<tr>
<td><code>initCodeCopyButtons()</code></td>
<td>Wrap copyable pre blocks and inject copy buttons.</td>
</tr>
<tr>
<td><code>toggleToc()</code></td>
<td>Show/hide table of contents.</td>
</tr>
<tr>
<td><code>goToRandomArticle()</code></td>
<td>Navigate to a random page.</td>
</tr>
<tr>
<td><code>triggerSearch()</code></td>
<td>Execute search and navigate to first match.</td>
</tr>
<tr>
<td><code>onSearchInput(e)</code></td>
<td>Live search suggestions.</td>
</tr>
<tr>
<td><code>handleSearchKey(e)</code></td>
<td>Keyboard navigation for search suggestions.</td>
</tr>
<tr>
<td><code>navigateSearch(slug)</code></td>
<td>Navigate to a search result.</td>
</tr>
<tr>
<td><code>applyCategoryFilterFromUrl()</code></td>
<td>Filter index page by <code>?category=</code> URL parameter.</td>
</tr>
</tbody>
</table>
<p>If the configured page layout file does not exist, the packaged minimal <code>index.html</code> layout is used silently — no error.</p>
<h2 id="filename-conventions">Filename conventions</h2>
<p>The CLI does not hard-code kebab-case. Projects choose a convention with <strong><code>wiki.filename_pattern</code></strong>, matched against the <strong>full filename</strong> (including <code>.md</code>) on markdown files only.</p>
<p><strong>Wikipedia-style (recommended):</strong> preserved capitalization and underscores — <code>Gregory_Davidson.md</code>, <code>Pokemon_Diamond_(copy_1).md</code>, <code>LLM_Wiki_CLI.md</code>. Use a pattern such as:</p>
<pre data-copy="wiki:
  filename_pattern: "[A-Za-z0-9_()-]+\\.md"
" class="highlight"><code class="language-yaml"><span class="nt">wiki</span><span class="p">:</span>
<span class="w">  </span><span class="nt">filename_pattern</span><span class="p">:</span><span class="w"> </span><span class="s">"[A-Za-z0-9_()-]+\\.md"</span>
</code></pre>
<p><strong>Kebab-case (optional):</strong> if you prefer <code>gregory-house.md</code>, set an explicit pattern (for example <code>[a-z0-9-]+\\.md</code>) and enforce it via <code>lint.filename_pattern</code>. Wikipedia-style and kebab-case should not be mixed in one wiki.</p>
<p>Page routes keep the casing from the filename; GitHub Pages URLs are case-sensitive.</p>
<p><code>wiki link --fix-broken</code> preserves the existing link kind in each file; only <code>--apply</code> uses <code>link.style</code>.</p>
<p>When <code>link.style</code> is <code>standard</code>, <code>lint.link_style</code> (default <code>warning</code>) flags Obsidian wikilinks (<code>[[Page]]</code>) in body prose. Set <code>lint.link_style: off</code> to allow wikilinks while keeping standard links as the apply format, or set <code>link.style: wikilink</code> for an Obsidian-style wiki.</p>
<h2 id="formatting-fmt-1">Formatting (<code>fmt</code>)</h2>
<p>Top-level <strong><code>fmt</code></strong> configures <code>wiki fmt</code> (mdformat). Two shapes are allowed — not both:</p>
<table>
<thead>
<tr>
<th>Shape</th>
<th>Example</th>
<th>When to use</th>
</tr>
</thead>
<tbody>
<tr>
<td>Inline mapping</td>
<td><code>fmt: { wrap: "no" }</code></td>
<td>Default; what <code>wiki init</code> writes</td>
</tr>
<tr>
<td>Relative path</td>
<td><code>fmt: custom.toml</code></td>
<td>Share one TOML file or keep fmt out of yaml</td>
</tr>
</tbody>
</table>
<p>Omit <code>fmt</code> entirely to use fallbacks: <code>config_root/.mdformat.toml</code>, then upward search from each markdown file, then <strong>Wiki CLI fmt defaults</strong> (<code>wrap: "no"</code>, <code>end_of_line: lf</code>, extensions <code>gfm</code>, <code>frontmatter</code>, <code>wikilink</code>). See <a href="/Wiki_Subcommand_fmt/">Wiki Subcommand fmt</a> for the full resolution order.</p>
<p>Invalid inline keys or values fail when the config loads. Invalid TOML syntax fails when <code>wiki fmt</code> reads the file.</p>
<p>In library code, loaded <code>Config.fmt</code> is a <code>FmtConfig</code> with <code>options</code> (inline mapping) or <code>toml</code> (resolved path under <code>config_root</code>); yaml shapes above are unchanged.</p>
<h2 id="integrity-checks-check-1">Integrity checks (<code>check</code>)</h2>
<p>Under <code>check</code>, each rule is <code>error</code>, <code>warning</code>, or <code>off</code>:</p>
<table>
<thead>
<tr>
<th>Rule key</th>
<th>Default</th>
<th>What it audits</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>missing_layout_file</code></td>
<td><code>error</code></td>
<td><code>wazoo:layout</code> paths that do not resolve to a readable <code>.html</code> file</td>
</tr>
<tr>
<td><code>frontmatter_schema</code></td>
<td><code>error</code></td>
<td>Frontmatter that fails JSON Schema validation</td>
</tr>
<tr>
<td><code>missing_schema_ref</code></td>
<td><code>error</code></td>
<td><code>wazoo:jsonSchema</code> paths or URLs that cannot be loaded</td>
</tr>
<tr>
<td><code>remote_schema_refs</code></td>
<td><code>allow</code></td>
<td>Policy for remote <code>http(s)</code> schema refs: <code>allow</code>, <code>deny</code>, or <code>allowlist</code></td>
</tr>
<tr>
<td><code>remote_schema_hosts</code></td>
<td><code>[]</code></td>
<td>Hostnames permitted when <code>remote_schema_refs</code> is <code>allowlist</code></td>
</tr>
</tbody>
</table>
<p>Build-safety rules (unsafe URL characters, spaces in routes) and output URL collision detection always apply regardless of <code>check</code> settings.</p>
<h3 id="json-schema-frontmatter-wazoojsonschema-1">JSON Schema frontmatter (<code>wazoo:jsonSchema</code>)</h3>
<p><code>wiki check</code> validates frontmatter against JSON Schema in parallel with SHACL. Bind schemas on shape documents with <strong><code>wazoo:jsonSchema</code></strong> beside <strong><code>sh:targetClass</code></strong>; every page whose effective <code>type</code> matches that class must pass the bound schema(s). Individual pages may append extra schemas with their own <code>wazoo:jsonSchema</code> key (scalar or YAML list). Schema refs are local paths under the wiki config root (<code>.json</code> only) or remote <code>http(s)</code> URLs. Remote refs can trigger outbound network requests; set <code>check.remote_schema_refs: deny</code> in CI over untrusted wikis, or <code>allowlist</code> with <code>check.remote_schema_hosts</code> for trusted hosts only.</p>
<p>Shape binding documents are not validated as instances — only their schema refs are checked for loadability. Authoring detail: <a href="/SHACL/">SHACL</a>, <a href="/Style_Guide/">Style Guide</a>.</p>
<h2 id="convention-audits-lint-1">Convention audits (<code>lint</code>)</h2>
<p>Under <code>lint</code>, each rule is <code>error</code>, <code>warning</code>, or <code>off</code>:</p>
<table>
<thead>
<tr>
<th>Rule key</th>
<th>Default</th>
<th>What it audits</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>broken_links</code></td>
<td><code>warning</code></td>
<td>Wikilinks, internal markdown links, heading fragments, assets, <code>wiki:</code> CURIEs</td>
</tr>
<tr>
<td><code>filename_pattern</code></td>
<td><code>warning</code></td>
<td>Full filename vs <code>wiki.filename_pattern</code> regex</td>
</tr>
<tr>
<td><code>headings</code></td>
<td><code>off</code></td>
<td>ATX <code>#</code> headings only (no Setext underlines), sentence-case H2+, H1 title case conventional, numbered headings</td>
</tr>
<tr>
<td><code>thematic_breaks</code></td>
<td><code>off</code></td>
<td>Horizontal rules (<code>---</code>, <code>***</code>, <code>___</code>) in body prose</td>
</tr>
<tr>
<td><code>link_style</code></td>
<td><code>warning</code></td>
<td>Obsidian wikilinks (<code>[[Page]]</code>) in body prose when <code>link.style</code> is <code>standard</code></td>
</tr>
</tbody>
</table>
<h2 id="this-repository">This repository</h2>
<p><code>docs/wiki.yml</code> is the dogfood wiki config: the same structure, block order, and Init columns as <code>wiki init</code> (<a href="https://github.com/wazootech/wiki/blob/main/src/wiki/templates/wiki.yml"><code>wiki.yml</code></a>), plus dogfood overrides — <code>graph.context.wiki</code> for GitHub Pages and <code>graph.content_predicate: schema:articleBody</code> for SPARQL full-text.</p>
<h2 id="related">Related</h2>
<ul>
<li><a href="/Wiki_CLI/#global-options">Wiki CLI</a> — <code>-c</code> and <code>--wiki-inputs</code> global options</li>
<li><a href="/Wiki_Subcommand_init/">Wiki Subcommand init</a> — scaffold a new wiki project</li>
<li><a href="/Wiki_Subcommand_check/">Wiki Subcommand check</a> — integrity checks</li>
<li><a href="/Wiki_Subcommand_lint/">Wiki Subcommand lint</a> — convention audits</li>
<li><a href="/Wiki_Subcommand_query/">Wiki Subcommand query</a> — ad-hoc SPARQL</li>
<li><a href="/Wiki_Subcommand_render/">Wiki Subcommand render</a> — inline SPARQL tables</li>
<li><a href="/Wiki_Subcommand_serve/#sparql-endpoint">Wiki Subcommand serve</a> — <code>#serve-api</code> config block</li>
<li><a href="/Graph_Cache/">Graph Cache</a> — <code>--cache</code> and graph reuse</li>
<li><a href="/Style_Guide/">Style Guide</a> — shapes and frontmatter</li>
</ul>
` |

Example excerpt (`index.html`):

```html
<!DOCTYPE html>
<html lang=en>
<head>
<meta charset=UTF-8>
<meta name=viewport content=width=device-width,initial-scale=1.0>
<title>Wiki Configuration - Wiki</title>
</head>
<body>
<p>The CLI loads <strong>Config</strong> from <code>wiki.yml</code>, <code>wiki.yaml</code>, or <code>wiki.json</code> in the working directory (or from <code>-c path</code>).</p>
<p>The in-memory <strong>Config</strong> model uses the same nested blocks as the file (<code>wiki</code>, <code>graph</code>, <code>site</code>, <code>link</code>, <code>check</code>, <code>lint</code>, <code>fmt</code>, <code>sparql_service</code>). There is no separate flat runtime shape. <code>Config.load()</code> validates the file, injects <code>config_root</code> (the directory containing the config file), and resolves relative paths under <code>wiki</code> and <code>site</code>. Library and test code can construct configs with <code>Config(wiki={...}, config_root=path)</code> or <code>Config.for_root(path, wiki={...})</code>.</p>
<p>Config files are validated strictly through a Pydantic schema (<code>extra='forbid'</code> on every block). Unknown keys, removed aliases, wrong nested keys under <code>check</code>, <code>lint</code>, or <code>sparql_service</code>, invalid syntax, or a non-mapping top level all fail immediately instead of being ignored.</p>
<p>JSON configs may use <code>graph.context</code> or <code>graph.@context</code> for prefix maps (JSON-LD compatible).</p>
<h2 id="overview">Overview</h2>
<h3 id="terminology">Terminology</h3>
<table>
<thead>
<tr>
<th>Label</th>
<th>Meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Schema optional</strong></td>
<td>Key or block may be omitted; Pydantic applies a default. No yaml key is strictly required for <code>Config.load()</code> to succeed.</td>
</tr>
<tr>
<td><strong>Init</strong></td>
<td>Written by <code>wiki init</code> (<a href="https://github.com/wazootech/wiki/blob/main/src/wiki/templates/wiki.yml"><code>wiki.yml</code></a>); omitting an Init key is the same as the schema default.</td>
</tr>
<tr>
<td><strong>Recommended</strong></td>
<td>Not enforced by schema, but you typically set it for a real wiki (for example <code>graph.context.wiki</code>, <code>wiki.filename_pattern</code>, <code>site.layout</code>).</td>
</tr>
<tr>
<td><strong>Always on</strong></td>
<td>Behavior not gated by yaml severities (route safety, URL collisions, built-in RDF prefixes).</td>
</tr>
</tbody>
</table>
<h3 id="audit-lanes">Audit lanes</h3>
<p>Three audit lanes map to three commands:</p>
<table>
<thead>
<tr>
<th>Lane</th>
<th>Command</th>
<th>YAML block</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td>Integrity</td>
<td><code>wiki check</code></td>
<td><code>check:</code></td>
<td>SHACL, JSON Schema frontmatter, layout file existence</td>
</tr>
<tr>
<td>Convention</td>
<td><code>wiki lint</code></td>
<td><code>lint:</code></td>
<td>Links, filename pattern severity, headings, link style in prose</td>
</tr>
<tr>
<td>Formatting</td>
<td><code>wiki fmt</code></td>
<td><code>fmt:</code></td>
<td>Mechanical markdown (mdformat; inline mapping or TOML path)</td>
</tr>
</tbody>
</table>
<p><strong>Rule placement:</strong> Mechanical markdown belongs under <strong><code>fmt:</code></strong>. Wiki policy and link conventions belong under <strong><code>lint:</code></strong>. SHACL, JSON Schema, and layout keys belong under <strong><code>check:</code></strong> — never under <code>lint:</code>. See <a href="/Style_Guide/">Style Guide</a> for the full matrix.</p>
<ul>
<li>Putting a regex under <code>check.filename_pattern</code> fails at load with a hint.</li>
<li><code>check.filename_pattern</code> and <code>check.headings</code> fail at load — use <code>lint.filename_pattern</code> and <code>lint.headings</code>.</li>
</ul>
<p>Relative <strong><code>--wiki-inputs</code></strong> paths on the CLI resolve against the config file directory (same as paths in yaml), not the shell cwd.</p>
<h3 id="blocks">Blocks</h3>
<p>Top-level blocks follow a <strong>compile pipeline</strong> plus <strong>audit lanes</strong>, not arbitrary grouping. <code>wiki init</code> and <a href="https://github.com/wazootech/wiki/blob/main/docs/wiki.yml">docs/wiki.yml</a> use the same order as the packaged scaffold <a href="https://github.com/wazootech/wiki/blob/main/src/wiki/templates/wiki.yml"><code>wiki.yml</code></a>.</p>
<table>
<thead>
<tr>
<th>Block</th>
<th>Role</th>
<th>Command(s)</th>
<th>Schema</th>
<th>Init scaffold</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>wiki:</code></td>
<td>Corpus on disk — inputs, assets, filename regex</td>
<td><code>check</code>, <code>lint</code>, <code>build</code>, <code>serve</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>graph:</code></td>
<td>RDF compile — prefixes, document IRIs, body literals</td>
<td><code>check</code>, <code>query</code>, <code>render</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>site:</code></td>
<td>Publish routing — layout path, URL prefix, path style</td>
<td><code>build</code>, <code>serve</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>link:</code></td>
<td><code>wiki link</code> apply format and rename repair map</td>
<td><code>wiki link</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>check:</code></td>
<td>Integrity severities</td>
<td><code>wiki check</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>lint:</code></td>
<td>Convention severities</td>
<td><code>wiki lint</code></td>
<td>optional</td>
<td>yes</td>
</tr>
<tr>
<td><code>sparql_service:</code></td>
<td>Opt-in SPARQL HTTP on <code>wiki serve</code></td>
<td><code>wiki serve</code></td>
<td>optional</td>
<td>commented example</td>
</tr>
<tr>
<td><code>fmt:</code></td>
<td>Mechanical markdown via mdformat</td>
<td><code>wiki fmt</code></td>
<td>optional</td>
<td>inline mapping</td>
</tr>
</tbody>
</table>
<p><strong>Order in the file:</strong> source and semantics first (<code>wiki</code>, <code>graph</code>), then publish and authoring (<code>site</code>, <code>link</code>), then severity tables (<code>check</code>, <code>lint</code>), optional serve (<code>sparql_service</code>), then <code>fmt</code> last.</p>
<p><strong>Split keys</strong> — policy lives in one block, severity or tooling in another:</p>
<ul>
<li><strong><code>wiki.filename_pattern</code></strong> — the regex string. <strong><code>lint.filename_pattern</code></strong> — how strictly to flag violations (<code>error</code>, <code>warning</code>, or <code>off</code>).</li>
<li><strong><code>link.style</code></strong> — what <code>wiki link --apply</code> inserts (<code>standard</code> page links or <code>wikilink</code>). <strong><code>lint.link_style</code></strong> — whether Obsidian <code>[[wikilinks]]</code> in body prose are flagged when <code>link.style</code> is <code>standard</code>.</li>
</ul>
<p>For why <code>check</code>, <code>lint</code>, <code>fmt</code>, and <code>wiki link</code> are separate commands, see <a href="/Design_Philosophies/#check-lint-fmt-and-link">Design philosophies</a>.</p>
<h3 id="always-on">Always on</h3>
<p>These apply regardless of yaml severities:</p>
<ul>
<li><strong>Route safety</strong> — unsafe URL characters and spaces in routes (<code>wiki check</code>).</li>
<li><strong>Output URL collisions</strong> — duplicate built routes (<code>wiki check</code>).</li>
<li><strong>SHACL</strong> — when shape documents exist in the corpus (<code>wiki check</code>).</li>
<li><strong>Built-in RDF prefixes</strong> — <code>schema</code>, <code>wiki</code>, <code>foaf</code>, <code>rdf</code>, <code>rdfs</code>, <code>xsd</code>, <code>owl</code>, <code>dc</code>, <code>dcterms</code>, <code>sh</code>, <code>wazoo</code> are always merged at runtime; yaml <code>graph.context</code> entries override or add.</li>
</ul>
<h2 id="wiki-wiki">Wiki (<code>wiki:</code>)</h2>
<pre data-copy="wiki:  # optional block
  inputs: [wiki]                    # default [wiki]; init writes
  assets: [assets]                  # default [assets] if assets/ exists, else []; init writes
  exclude: []                         # default []; init omits
  filename_pattern: "[A-Za-z0-9_()-]+\\.md"  # no default; recommended; init writes
" class="highlight"><code class="language-yaml"><span class="nt">wiki</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">inputs</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[</span><span class="nv">wiki</span><span class="p p-Indicator">]</span><span class="w">                    </span><span class="c1"># default [wiki]; init writes</span>
<span class="w">  </span><span class="nt">assets</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[</span><span class="nv">assets</span><span class="p p-Indicator">]</span><span class="w">                  </span><span class="c1"># default [assets] if assets/ exists, else []; init writes</span>
<span class="w">  </span><span class="nt">exclude</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[]</span><span class="w">                         </span><span class="c1"># default []; init omits</span>
<span class="w">  </span><span class="nt">filename_pattern</span><span class="p">:</span><span class="w"> </span><span class="s">"[A-Za-z0-9_()-]+\\.md"</span><span class="w">  </span><span class="c1"># no default; recommended; init writes</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>inputs</code></td>
<td>optional</td>
<td><code>[wiki]</code></td>
<td>writes</td>
<td>indexing (<code>build</code>, <code>check</code>, <code>lint</code>, <code>fmt</code>)</td>
</tr>
<tr>
<td><code>assets</code></td>
<td>optional</td>
<td><code>[assets]</code> when <code>assets/</code> exists, else <code>[]</code></td>
<td>writes</td>
<td><code>wiki build</code> (static copy)</td>
</tr>
<tr>
<td><code>exclude</code></td>
<td>optional</td>
<td><code>[]</code></td>
<td>omits</td>
<td>indexing (skipped paths)</td>
</tr>
<tr>
<td><code>filename_pattern</code></td>
<td>optional (recommended)</td>
<td>unset — no regex check until set</td>
<td>writes</td>
<td><code>wiki lint</code> (<code>lint.filename_pattern</code>)</td>
</tr>
</tbody>
</table>
<p>Page URLs come from paths under <code>wiki.inputs</code>: <code>wiki/Alice.md</code> → <code>/wiki/Alice/</code> with default <code>site.base_url</code> and <code>site.url_style: dir</code>. <code>index.md</code> in a folder owns that folder’s route (for example <code>wiki/index.md</code> → <code>/wiki/</code>).</p>
<p>See <a href="#filename-conventions">Filename conventions</a> for regex patterns.</p>
<h2 id="graph-graph">Graph (<code>graph:</code>)</h2>
<p>RDF and document URI settings for graph build, <code>wiki query</code>, microdata, and SHACL.</p>
<pre data-copy="graph:  # optional block
  # base_iri: unset → graph.context.wiki → https://wiki.example.org/
  content_predicate: schema:articleBody   # unset by default; init writes when flagged
  include_file_extension: false           # default false; init omits (commented)
  implicit_types: []                      # default []; init omits (commented)
  implicit_types_policy: fallback         # default fallback; init omits (commented)
  context:                                # merges with built-in prefixes; init writes
    schema: https://schema.org/
    wiki: https://example.org/wiki/       # recommended
    wazoo: https://schema.wazoo.dev/
    foaf: http://xmlns.com/foaf/0.1/
    dc: http://purl.org/dc/elements/1.1/
    dcterms: http://purl.org/dc/terms/
    sh: http://www.w3.org/ns/shacl#
    xsd: http://www.w3.org/2001/XMLSchema#
" class="highlight"><code class="language-yaml"><span class="nt">graph</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="c1"># base_iri: unset → graph.context.wiki → https://wiki.example.org/</span>
<span class="w">  </span><span class="nt">content_predicate</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">schema:articleBody</span><span class="w">   </span><span class="c1"># unset by default; init writes when flagged</span>
<span class="w">  </span><span class="nt">include_file_extension</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">false</span><span class="w">           </span><span class="c1"># default false; init omits (commented)</span>
<span class="w">  </span><span class="nt">implicit_types</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[]</span><span class="w">                      </span><span class="c1"># default []; init omits (commented)</span>
<span class="w">  </span><span class="nt">implicit_types_policy</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">fallback</span><span class="w">         </span><span class="c1"># default fallback; init omits (commented)</span>
<span class="w">  </span><span class="nt">context</span><span class="p">:</span><span class="w">                                </span><span class="c1"># merges with built-in prefixes; init writes</span>
<span class="w">    </span><span class="nt">schema</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">https://schema.org/</span>
<span class="w">    </span><span class="nt">wiki</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">https://example.org/wiki/</span><span class="w">       </span><span class="c1"># recommended</span>
<span class="w">    </span><span class="nt">wazoo</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">https://schema.wazoo.dev/</span>
<span class="w">    </span><span class="nt">foaf</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">http://xmlns.com/foaf/0.1/</span>
<span class="w">    </span><span class="nt">dc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">http://purl.org/dc/elements/1.1/</span>
<span class="w">    </span><span class="nt">dcterms</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">http://purl.org/dc/terms/</span>
<span class="w">    </span><span class="nt">sh</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">http://www.w3.org/ns/shacl#</span>
<span class="w">    </span><span class="nt">xsd</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">http://www.w3.org/2001/XMLSchema#</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>base_iri</code></td>
<td>optional</td>
<td>unset → <code>graph.context.wiki</code> → <code>https://wiki.example.org/</code></td>
<td>commented example</td>
<td>document IRIs, <code>wiki query</code></td>
</tr>
<tr>
<td><code>context</code> / <code>@context</code></td>
<td>optional (recommended: <code>wiki</code>)</td>
<td>built-in prefixes only when unset</td>
<td>writes extended map</td>
<td>CURIE expansion, SHACL, microdata</td>
</tr>
<tr>
<td><code>content_predicate</code></td>
<td>optional</td>
<td>unset — no body literals in graph</td>
<td>writes when <code>--graph-content-predicate</code></td>
<td>SPARQL full-text</td>
</tr>
<tr>
<td><code>include_file_extension</code></td>
<td>optional</td>
<td><code>false</code></td>
<td>omits (commented)</td>
<td>document URI generation</td>
</tr>
<tr>
<td><code>implicit_types</code></td>
<td>optional</td>
<td><code>[]</code></td>
<td>omits (commented)</td>
<td>default <code>rdf:type</code> on untyped pages</td>
</tr>
<tr>
<td><code>implicit_types_policy</code></td>
<td>optional</td>
<td><code>fallback</code></td>
<td>omits (commented)</td>
<td><code>fallback</code> or <code>append</code> (SHACL shapes skip append)</td>
</tr>
</tbody>
</table>
<p>When <code>implicit_types_policy</code> is <code>append</code>, frontmatter types are unioned with <code>implicit_types</code> (deduped by resolved URI).</p>
<h2 id="site-site">Site (<code>site:</code>)</h2>
<p>Default page layout and routing for <code>wiki build</code> / <code>wiki serve</code>. Branding and chrome → <a href="#page-layout">Page layout</a>.</p>
<pre data-copy="site:  # optional block
  layout: index.html   # unset → built-in minimal fallback layout
  base_url: /wiki                   # default /wiki; init writes
  url_style: dir                    # default dir; init writes
" class="highlight"><code class="language-yaml"><span class="nt">site</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">layout</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">index.html</span><span class="w">   </span><span class="c1"># unset → built-in minimal fallback layout</span>
<span class="w">  </span><span class="nt">base_url</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">/wiki</span><span class="w">                   </span><span class="c1"># default /wiki; init writes</span>
<span class="w">  </span><span class="nt">url_style</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">dir</span><span class="w">                    </span><span class="c1"># default dir; init writes</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>layout</code></td>
<td>optional (recommended)</td>
<td>unset — packaged minimal <code>index.html</code></td>
<td>writes</td>
<td><code>wiki build</code>, <code>wiki serve</code>; <code>check.missing_layout_file</code> for per-page <code>wazoo:layout</code></td>
</tr>
<tr>
<td><code>base_url</code></td>
<td>optional</td>
<td><code>/wiki</code> (<code>""</code> allowed for site root)</td>
<td>writes</td>
<td>routes, layout <code>%wiki.base_url%</code></td>
</tr>
<tr>
<td><code>url_style</code></td>
<td>optional</td>
<td><code>dir</code> (<code>file</code> → <code>slug.html</code>)</td>
<td>writes</td>
<td>output paths; overridable per CLI run</td>
</tr>
</tbody>
</table>
<p><code>site:</code> does not carry site name, theme color, favicon, or sidebar logo. If you want custom styling, write a custom layout template file and place custom assets under the <code>wiki.assets</code> directory, then configure <code>site.layout</code> to point to it.</p>
<p>CLI flags on <code>wiki build</code> and <code>wiki serve</code> can override <code>site.base_url</code> and <code>site.url_style</code> for a single run.</p>
<h2 id="link-link">Link (<code>link:</code>)</h2>
<p>Settings for the <code>wiki link</code> command family (separate from <code>lint.link_style</code> severity).</p>
<pre data-copy="link:  # optional block
  style: standard       # default standard; init writes
  renames: {}           # default {}; init omits (commented example)
" class="highlight"><code class="language-yaml"><span class="nt">link</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">style</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">standard</span><span class="w">       </span><span class="c1"># default standard; init writes</span>
<span class="w">  </span><span class="nt">renames</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">{}</span><span class="w">           </span><span class="c1"># default {}; init omits (commented example)</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>style</code></td>
<td>optional</td>
<td><code>standard</code> (<code>wikilink</code> for wikilinks)</td>
<td>writes</td>
<td><code>wiki link --apply</code> only</td>
</tr>
<tr>
<td><code>renames</code></td>
<td>optional</td>
<td><code>{}</code></td>
<td>commented example</td>
<td><code>wiki link --fix-broken</code></td>
</tr>
</tbody>
</table>
<p><code>wiki link --fix-broken</code> preserves the existing link kind in each file; only <code>--apply</code> uses <code>link.style</code>.</p>
<h2 id="integrity-checks-check">Integrity checks (<code>check:</code>)</h2>
<p>Under <code>check</code>, each rule is <code>error</code>, <code>warning</code>, or <code>off</code>:</p>
<pre data-copy="check:  # optional block
  missing_layout_file: error    # default error; init writes
  frontmatter_schema: error     # default error; init writes
  missing_schema_ref: error   # default error; init writes
" class="highlight"><code class="language-yaml"><span class="nt">check</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">missing_layout_file</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">error</span><span class="w">    </span><span class="c1"># default error; init writes</span>
<span class="w">  </span><span class="nt">frontmatter_schema</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">error</span><span class="w">     </span><span class="c1"># default error; init writes</span>
<span class="w">  </span><span class="nt">missing_schema_ref</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">error</span><span class="w">   </span><span class="c1"># default error; init writes</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>missing_layout_file</code></td>
<td>optional</td>
<td><code>error</code></td>
<td>writes</td>
<td><code>wazoo:layout</code> paths missing on disk</td>
</tr>
<tr>
<td><code>frontmatter_schema</code></td>
<td>optional</td>
<td><code>error</code></td>
<td>writes</td>
<td>JSON Schema validation failures</td>
</tr>
<tr>
<td><code>missing_schema_ref</code></td>
<td>optional</td>
<td><code>error</code></td>
<td>writes</td>
<td>unloadable <code>wazoo:jsonSchema</code> refs</td>
</tr>
</tbody>
</table>
<p>Build-safety rules (unsafe URL characters, spaces in routes) and output URL collision detection always apply regardless of <code>check</code> settings.</p>
<h3 id="json-schema-frontmatter-wazoojsonschema">JSON Schema frontmatter (<code>wazoo:jsonSchema</code>)</h3>
<p><code>wiki check</code> validates frontmatter against JSON Schema in parallel with SHACL. Bind schemas on shape documents with <strong><code>wazoo:jsonSchema</code></strong> beside <strong><code>sh:targetClass</code></strong>; every page whose effective <code>type</code> matches that class must pass the bound schema(s). Individual pages may append extra schemas with their own <code>wazoo:jsonSchema</code> key (scalar or YAML list). Schema refs are local paths under the wiki config root (<code>.json</code> only) or remote <code>http(s)</code> URLs.</p>
<p>Shape binding documents are not validated as instances — only their schema refs are checked for loadability. Authoring detail: <a href="/SHACL/">SHACL</a>, <a href="/Style_Guide/">Style Guide</a>.</p>
<h2 id="convention-audits-lint">Convention audits (<code>lint:</code>)</h2>
<p>Under <code>lint</code>, each rule is <code>error</code>, <code>warning</code>, or <code>off</code>:</p>
<pre data-copy="lint:  # optional block
  broken_links: warning       # default warning; init writes
  filename_pattern: warning   # default warning; init writes
  headings: off               # default off; init omits
  heading_levels: off         # default off; init omits
  duplicate_headings: off     # default off; init omits
  thematic_breaks: off        # default off; init omits
  link_style: warning         # default warning; init writes
" class="highlight"><code class="language-yaml"><span class="nt">lint</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">broken_links</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">warning</span><span class="w">       </span><span class="c1"># default warning; init writes</span>
<span class="w">  </span><span class="nt">filename_pattern</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">warning</span><span class="w">   </span><span class="c1"># default warning; init writes</span>
<span class="w">  </span><span class="nt">headings</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">off</span><span class="w">               </span><span class="c1"># default off; init omits</span>
<span class="w">  </span><span class="nt">heading_levels</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">off</span><span class="w">         </span><span class="c1"># default off; init omits</span>
<span class="w">  </span><span class="nt">duplicate_headings</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">off</span><span class="w">     </span><span class="c1"># default off; init omits</span>
<span class="w">  </span><span class="nt">thematic_breaks</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">off</span><span class="w">        </span><span class="c1"># default off; init omits</span>
<span class="w">  </span><span class="nt">link_style</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">warning</span><span class="w">         </span><span class="c1"># default warning; init writes</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>broken_links</code></td>
<td>optional</td>
<td><code>warning</code></td>
<td>writes</td>
<td>wikilinks, markdown links, fragments, assets, <code>wiki:</code> CURIEs</td>
</tr>
<tr>
<td><code>filename_pattern</code></td>
<td>optional</td>
<td><code>warning</code></td>
<td>writes</td>
<td>full filename vs <code>wiki.filename_pattern</code></td>
</tr>
<tr>
<td><code>headings</code></td>
<td>optional</td>
<td><code>off</code></td>
<td>omits</td>
<td>ATX syntax, sentence-case H2+, numbered headings</td>
</tr>
<tr>
<td><code>heading_levels</code></td>
<td>optional</td>
<td><code>off</code></td>
<td>omits</td>
<td>heading level gaps (for example H1 then H3)</td>
</tr>
<tr>
<td><code>duplicate_headings</code></td>
<td>optional</td>
<td><code>off</code></td>
<td>omits</td>
<td>duplicate heading text on one page</td>
</tr>
<tr>
<td><code>thematic_breaks</code></td>
<td>optional</td>
<td><code>off</code></td>
<td>omits</td>
<td>horizontal rules in body prose</td>
</tr>
<tr>
<td><code>link_style</code></td>
<td>optional</td>
<td><code>warning</code></td>
<td>writes</td>
<td>Obsidian <code>[[wikilinks]]</code> when <code>link.style</code> is <code>standard</code></td>
</tr>
</tbody>
</table>
<p>ATX heading syntax is also enforced by <strong><code>wiki fmt</code></strong> (mdformat); Setext underlines are converted on format.</p>
<p>When <code>link.style</code> is <code>standard</code>, set <code>lint.link_style: off</code> to allow wikilinks in prose, or set <code>link.style: wikilink</code> for an Obsidian-style wiki.</p>
<h2 id="serve-api">Serve API</h2>
<p>Opt-in read-only SPARQL HTTP endpoint on <code>wiki serve</code>:</p>
<pre data-copy="sparql_service:  # optional block
  enabled: false        # default false; init omits (commented)
  path: /api/sparql     # default /api/sparql; init omits (commented)
" class="highlight"><code class="language-yaml"><span class="nt">sparql_service</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block</span>
<span class="w">  </span><span class="nt">enabled</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">false</span><span class="w">        </span><span class="c1"># default false; init omits (commented)</span>
<span class="w">  </span><span class="nt">path</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">/api/sparql</span><span class="w">     </span><span class="c1"># default /api/sparql; init omits (commented)</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>enabled</code></td>
<td>optional</td>
<td><code>false</code></td>
<td>commented example</td>
<td><code>wiki serve</code> SPARQL endpoint</td>
</tr>
<tr>
<td><code>path</code></td>
<td>optional</td>
<td><code>/api/sparql</code></td>
<td>commented example</td>
<td>reserved route on serve</td>
</tr>
</tbody>
</table>
<p><code>sparql_service.enabled</code> accepts YAML booleans and normalizes common string forms such as <code>true</code>, <code>false</code>, <code>on</code>, <code>off</code>, <code>yes</code>, <code>no</code>, <code>1</code>, and <code>0</code>; prefer native YAML booleans.</p>
<p>Example when enabled:</p>
<pre data-copy="sparql_service:
  enabled: true
  path: /api/sparql
" class="highlight"><code class="language-yaml"><span class="nt">sparql_service</span><span class="p">:</span>
<span class="w">  </span><span class="nt">enabled</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">true</span>
<span class="w">  </span><span class="nt">path</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">/api/sparql</span>
</code></pre>
<p>The endpoint reuses the same SPARQL engine as <code>wiki query</code>. It is read-only and intended for local or development-oriented use. HTTP request forms, supported query types, and <code>Accept</code> negotiation are documented in <a href="/Wiki_Subcommand_serve/#sparql-endpoint">Wiki Subcommand serve</a>.</p>
<p>It is <strong>opt-in by default</strong> because enabling it exposes raw graph-query access in addition to HTML preview.</p>
<p><code>sparql_service.path</code> must not collide with the effective <code>site.base_url</code> page routes or the watch endpoint. Invalid values such as <code>/</code>, <code>/wiki</code>, <code>/wiki/foo</code>, or <code>/wiki/__watch</code> are rejected when <code>wiki serve</code> starts.</p>
<h2 id="formatting-fmt">Formatting (<code>fmt</code>)</h2>
<p>Top-level <strong><code>fmt</code></strong> configures <code>wiki fmt</code> (mdformat). Two shapes are allowed — not both:</p>
<pre data-copy="fmt:  # optional block — inline mapping (init writes)
  wrap: "no"
  end_of_line: lf
  extensions: [gfm, frontmatter, wikilink]

# Pointer mode (optional alternative):
# fmt: .mdformat.toml
" class="highlight"><code class="language-yaml"><span class="nt">fmt</span><span class="p">:</span><span class="w">  </span><span class="c1"># optional block — inline mapping (init writes)</span>
<span class="w">  </span><span class="nt">wrap</span><span class="p">:</span><span class="w"> </span><span class="s">"no"</span>
<span class="w">  </span><span class="nt">end_of_line</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">lf</span>
<span class="w">  </span><span class="nt">extensions</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[</span><span class="nv">gfm</span><span class="p p-Indicator">,</span><span class="w"> </span><span class="nv">frontmatter</span><span class="p p-Indicator">,</span><span class="w"> </span><span class="nv">wikilink</span><span class="p p-Indicator">]</span>

<span class="c1"># Pointer mode (optional alternative):</span>
<span class="c1"># fmt: .mdformat.toml</span>
</code></pre>
<table>
<thead>
<tr>
<th>Key / shape</th>
<th>Required</th>
<th>Default</th>
<th>Init</th>
<th>Audited by</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>wrap</code></td>
<td>optional (inline)</td>
<td><code>"no"</code></td>
<td>writes</td>
<td><code>wiki fmt</code></td>
</tr>
<tr>
<td><code>end_of_line</code></td>
<td>optional (inline)</td>
<td><code>lf</code></td>
<td>writes</td>
<td><code>wiki fmt</code></td>
</tr>
<tr>
<td><code>extensions</code></td>
<td>optional (inline)</td>
<td><code>[gfm, frontmatter, wikilink]</code></td>
<td>writes</td>
<td><code>wiki fmt</code></td>
</tr>
<tr>
<td>TOML path</td>
<td>optional</td>
<td>unset — see fallback chain below</td>
<td>omits (commented)</td>
<td><code>wiki fmt</code></td>
</tr>
</tbody>
</table>
<p>Omit <code>fmt</code> entirely to use fallbacks: <code>config_root/.mdformat.toml</code>, then upward search from each markdown file, then <strong>Wiki CLI fmt defaults</strong> (same as inline defaults above). See <a href="/Wiki_Subcommand_fmt/">Wiki Subcommand fmt</a> for the full resolution order.</p>
<table>
<thead>
<tr>
<th>Shape</th>
<th>Example</th>
<th>When to use</th>
</tr>
</thead>
<tbody>
<tr>
<td>Inline mapping</td>
<td><code>fmt: { wrap: "no" }</code></td>
<td>Default; what <code>wiki init</code> writes</td>
</tr>
<tr>
<td>Relative path</td>
<td><code>fmt: custom.toml</code></td>
<td>Share one TOML file or keep fmt out of yaml</td>
</tr>
</tbody>
</table>
<p>Invalid inline keys or values fail when the config loads. Invalid TOML syntax fails when <code>wiki fmt</code> reads the file.</p>
<p>In library code, loaded <code>Config.fmt</code> is a <code>FmtConfig</code> with <code>options</code> (inline mapping) or <code>toml</code> (resolved path under <code>config_root</code>).</p>
<h2 id="page-layout">Page layout</h2>
<p>When <code>site.layout</code> is set, the CLI renders every page through that page layout (<code>.html</code>). Per-page overrides use <code>wazoo:layout</code> in frontmatter; see <a href="/Wiki_Page_Layouts/">Wiki Page Layouts</a>.</p>
<h3 id="layout-strategy">Layout strategy</h3>
<p>The first-class presentation contract in this repository is layout files referenced from <code>site.layout</code> (for example <code>index.html</code>).</p>
<ul>
<li>The <a href="/Wiki_CLI/">Wiki CLI</a> owns the semantic markdown-to-HTML pipeline and layout slot contract.</li>
<li>Wiki page layout files are the primary built-in extension point for presentation.</li>
<li>Advanced themes or framework-specific sites such as Next.js, Mintlify, or other external docs stacks are treated as downstream integrations or separate layout/template repositories.</li>
</ul>
<h3 id="minimal-fallback">Minimal fallback</h3>
<p>Without a configured layout file (or when the path is missing), every page is rendered with the built-in minimal fallback layout (<code>index.html</code>), which outputs plain, unstyled HTML containing only <code><h1></code> and content. It does not link any default CSS or assets and does not include a sidebar, tabs, infobox, table of contents, backlinks, or categories out-of-the-box.</p>
<h3 id="layout-slots">Layout slots</h3>
<p>Layout files use <code>%wiki.*%</code> slot substitution (not Jinja). On each page render, the CLI builds a slot map from the current page context and replaces every known slot in your layout file. Unknown <code>%wiki.*%</code> spellings are left unchanged.</p>
<p>Programmatic consumers and contract tests use <code>wiki.site.layout_tokens.build_layout_token_map</code> as the single boundary for slot production. See <a href="/Wiki_Programmatic_API/#layout-slot-contract">Wiki Programmatic API</a>.</p>
<p>Canonical slot list (3 slots):</p>
<table>
<thead>
<tr>
<th>Slot</th>
<th>Source</th>
<th>Substitution</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>%wiki.base_url%</code></td>
<td><code>site.base_url</code></td>
<td>HTML-escaped text (<code>/wiki</code>, or <code>""</code> for site root)</td>
</tr>
<tr>
<td><code><title>Wiki Configuration - Wiki</title></code></td>
<td>built per page</td>
<td><code><title>{page title} - Wiki CLI</title></code> (title HTML-escaped)</td>
</tr>
<tr>
<td><code>%wiki.body%</code></td>
<td>rendered markdown body</td>
<td>Pre-built HTML (not escaped)</td>
</tr>
</tbody>
</table>
<p><strong>Packaged layouts</strong></p>
<table>
<thead>
<tr>
<th>File</th>
<th>When used</th>
<th>Typical slots</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>index.html</code></td>
<td><code>site.layout</code> unset or missing file</td>
<td><code><title>Wiki Configuration - Wiki</title></code>, <code>%wiki.body%</code></td>
</tr>
</tbody>
</table>
<p>Example excerpt (<code>index.html</code>):</p>
<pre data-copy="<!DOCTYPE html>
<html lang=en>
<head>
<meta charset=UTF-8>
<meta name=viewport content=width=device-width,initial-scale=1.0>
<title>Wiki Configuration - Wiki</title>
</head>
<body>
%wiki.body%
</body>
</html>
" class="highlight"><code class="language-html"><span class="cp"><!DOCTYPE html></span>
<span class="p"><</span><span class="nt">html</span> <span class="na">lang</span><span class="o">=</span><span class="s">en</span><span class="p">></span>
<span class="p"><</span><span class="nt">head</span><span class="p">></span>
<span class="p"><</span><span class="nt">meta</span> <span class="na">charset</span><span class="o">=</span><span class="s">UTF-8</span><span class="p">></span>
<span class="p"><</span><span class="nt">meta</span> <span class="na">name</span><span class="o">=</span><span class="s">viewport</span> <span class="na">content</span><span class="o">=</span><span class="s">width=device-width,initial-scale=1.0</span><span class="p">></span>
<title>Wiki Configuration - Wiki</title>
<span class="p"></</span><span class="nt">head</span><span class="p">></span>
<span class="p"><</span><span class="nt">body</span><span class="p">></span>
%wiki.body%
<span class="p"></</span><span class="nt">body</span><span class="p">></span>
<span class="p"></</span><span class="nt">html</span><span class="p">></span>
</code></pre>
<h3 id="custom-css">Custom CSS</h3>
<p>The Wiki CLI does not copy or link a default stylesheet out-of-the-box. To add styling to your pages:</p>
<ol>
<li><strong>Edit the layout file</strong> — set <code>site.layout</code> in <code>wiki.yml</code> to a custom layout file. Link stylesheets in <code><head></code>, or write inline styles.</li>
<li><strong>Link wiki assets</strong> — place <code>.css</code> files under a directory listed in <code>wiki.assets</code>, then reference them from the layout, for example <code><link rel="stylesheet" href="%wiki.base_url%/assets/site.css"></code>. Built assets are served at <code>%wiki.base_url%/assets/…</code> during <code>wiki serve</code> and copied into the build output.</li>
</ol>
<h3 id="custom-logos-and-icons">Custom logos and icons</h3>
<p>To customize site logos, icons, favicons, or touch icons:</p>
<ol>
<li>Place your asset files (such as <code>logo.svg</code>, <code>logo.png</code>, <code>favicon.ico</code>) under a directory listed in <code>wiki.assets</code>.</li>
<li>Reference the assets from your custom layout file, for example:</li>
</ol>
<pre data-copy="<img src="%wiki.base_url%/assets/logo.svg" alt="" width="80" height="80">
" class="highlight"><code class="language-html"><span class="p"><</span><span class="nt">img</span> <span class="na">src</span><span class="o">=</span><span class="s">"%wiki.base_url%/assets/logo.svg"</span> <span class="na">alt</span><span class="o">=</span><span class="s">""</span> <span class="na">width</span><span class="o">=</span><span class="s">"80"</span> <span class="na">height</span><span class="o">=</span><span class="s">"80"</span><span class="p">></span>
</code></pre>
<p>You can also add <code><link rel="icon"></code>, <code><link rel="apple-touch-icon"></code>, or other <code><head></code> tags directly in your custom layout file.</p>
<p>Built assets are served at <code>%wiki.base_url%/assets/…</code> during <code>wiki serve</code> and copied into the build output.</p>
<p>See also <a href="/Wiki_Page_Layouts/">Wiki Page Layouts</a> for <code>site.layout</code>, <code>wazoo:layout</code>, and packaged layout files.</p>
<p>The metadata pane uses the same RDF serialization path as <code>wiki export</code> (compacted JSON-LD, Turtle, N3, RDF/XML, N-Triples, TriG, N-Quads). A compact <strong>Format</strong> chip row switches views without JavaScript. In <code>wiki serve</code>, set the initial chip with <code>?metadata_format=FORMAT</code> (for example <code>turtle</code> or <code>json-ld</code>). In <code>wiki build</code>, all format views are embedded in the page HTML so the picker works offline.</p>
<h3 id="built-in-css-classes-and-ids">Built-in CSS classes and IDs</h3>
<p>The wiki builder generates these selectors in the rendered page content:</p>
<table>
<thead>
<tr>
<th>Selector</th>
<th>Where</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>#article-top</code></td>
<td>Read-view <code><article></code> wrapper around rendered markdown body.</td>
</tr>
<tr>
<td><code>#firstHeading</code></td>
<td>Read-view page title <code><h1></code>; also Talk / Source / Metadata pane headings. TOC “(Top)” links here.</td>
</tr>
<tr>
<td><code>#siteSub</code></td>
<td>Subtitle under Talk / Source / Metadata pane headings.</td>
</tr>
<tr>
<td><code>article</code></td>
<td>Wrapper around the rendered markdown body (<code>#article-top</code>).</td>
</tr>
<tr>
<td><code>.layout-label</code></td>
<td>Uppercase type or custom-layout badge in read view.</td>
</tr>
<tr>
<td><code>.toc</code> / <code>#toc</code></td>
<td>Table of contents container.</td>
</tr>
<tr>
<td><code>#catlinks</code> / <code>.catlinks</code></td>
<td>Category links box.</td>
</tr>
<tr>
<td><code>.backlinks</code> / <code>#backlinks</code></td>
<td>Backlinks section.</td>
</tr>
<tr>
<td><code>.catlinks-label</code></td>
<td>Categories heading label.</td>
</tr>
<tr>
<td><code>.catlinks-list</code></td>
<td>Categories <code><ul></code>.</td>
</tr>
<tr>
<td><code>.infobox</code></td>
<td>Typed frontmatter property table.</td>
</tr>
<tr>
<td><code>.page-meta</code></td>
<td>Infobox class (used for styling).</td>
</tr>
<tr>
<td><code>.template-SLUG</code></td>
<td>Per-template class on infobox (e.g. <code>template-person</code>).</td>
</tr>
<tr>
<td><code>toclevel-N</code> / <code>lN</code></td>
<td>TOC list item classes for heading level N.</td>
</tr>
<tr>
<td><code>.wikilink</code></td>
<td>Internal wiki page links.</td>
</tr>
<tr>
<td><code>pre[data-copy]</code></td>
<td>Block code with raw source for clipboard copy.</td>
</tr>
<tr>
<td><code>.code-block</code></td>
<td>Wrapper injected around copyable pre blocks.</td>
</tr>
<tr>
<td><code>.code-copy-btn</code></td>
<td>Copy button shown on code-block hover/focus.</td>
</tr>
</tbody>
</table>
<h3 id="javascript-hooks">JavaScript hooks</h3>
<p>Custom layout files can utilize standard JavaScript hooks or customize their own. In premium layouts (such as template repositories), the following JavaScript features can be implemented:</p>
<table>
<thead>
<tr>
<th>Function</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>switchTab(viewName)</code></td>
<td>Switch between read / talk / source / metadata tabs.</td>
</tr>
<tr>
<td><code>loadTalkNotes()</code></td>
<td>Load per-page local-storage notes.</td>
</tr>
<tr>
<td><code>saveTalkNotes()</code></td>
<td>Save per-page notes to localStorage.</td>
</tr>
<tr>
<td><code>clearTalkNotes()</code></td>
<td>Clear per-page notes.</td>
</tr>
<tr>
<td><code>copySourceCode()</code></td>
<td>Copy markdown source to clipboard.</td>
</tr>
<tr>
<td><code>copyPreContent()</code></td>
<td>Copy a <code>pre[data-copy]</code> block to clipboard.</td>
</tr>
<tr>
<td><code>initCodeCopyButtons()</code></td>
<td>Wrap copyable pre blocks and inject copy buttons.</td>
</tr>
<tr>
<td><code>toggleToc()</code></td>
<td>Show/hide table of contents.</td>
</tr>
<tr>
<td><code>goToRandomArticle()</code></td>
<td>Navigate to a random page.</td>
</tr>
<tr>
<td><code>triggerSearch()</code></td>
<td>Execute search and navigate to first match.</td>
</tr>
<tr>
<td><code>onSearchInput(e)</code></td>
<td>Live search suggestions.</td>
</tr>
<tr>
<td><code>handleSearchKey(e)</code></td>
<td>Keyboard navigation for search suggestions.</td>
</tr>
<tr>
<td><code>navigateSearch(slug)</code></td>
<td>Navigate to a search result.</td>
</tr>
<tr>
<td><code>applyCategoryFilterFromUrl()</code></td>
<td>Filter index page by <code>?category=</code> URL parameter.</td>
</tr>
</tbody>
</table>
<p>If the configured page layout file does not exist, the packaged minimal <code>index.html</code> layout is used silently — no error.</p>
<h2 id="filename-conventions">Filename conventions</h2>
<p>The CLI does not hard-code kebab-case. Projects choose a convention with <strong><code>wiki.filename_pattern</code></strong>, matched against the <strong>full filename</strong> (including <code>.md</code>) on markdown files only.</p>
<p><strong>Wikipedia-style (recommended):</strong> preserved capitalization and underscores — <code>Gregory_Davidson.md</code>, <code>Pokemon_Diamond_(copy_1).md</code>, <code>LLM_Wiki_CLI.md</code>. Use a pattern such as:</p>
<pre data-copy="wiki:
  filename_pattern: "[A-Za-z0-9_()-]+\\.md"
" class="highlight"><code class="language-yaml"><span class="nt">wiki</span><span class="p">:</span>
<span class="w">  </span><span class="nt">filename_pattern</span><span class="p">:</span><span class="w"> </span><span class="s">"[A-Za-z0-9_()-]+\\.md"</span>
</code></pre>
<p><strong>Kebab-case (optional):</strong> if you prefer <code>gregory-house.md</code>, set an explicit pattern (for example <code>[a-z0-9-]+\\.md</code>) and enforce it via <code>lint.filename_pattern</code>. Wikipedia-style and kebab-case should not be mixed in one wiki.</p>
<p>Page routes keep the casing from the filename; GitHub Pages URLs are case-sensitive.</p>
<p><code>wiki link --fix-broken</code> preserves the existing link kind in each file; only <code>--apply</code> uses <code>link.style</code>.</p>
<p>When <code>link.style</code> is <code>standard</code>, <code>lint.link_style</code> (default <code>warning</code>) flags Obsidian wikilinks (<code>[[Page]]</code>) in body prose. Set <code>lint.link_style: off</code> to allow wikilinks while keeping standard links as the apply format, or set <code>link.style: wikilink</code> for an Obsidian-style wiki.</p>
<h2 id="formatting-fmt-1">Formatting (<code>fmt</code>)</h2>
<p>Top-level <strong><code>fmt</code></strong> configures <code>wiki fmt</code> (mdformat). Two shapes are allowed — not both:</p>
<table>
<thead>
<tr>
<th>Shape</th>
<th>Example</th>
<th>When to use</th>
</tr>
</thead>
<tbody>
<tr>
<td>Inline mapping</td>
<td><code>fmt: { wrap: "no" }</code></td>
<td>Default; what <code>wiki init</code> writes</td>
</tr>
<tr>
<td>Relative path</td>
<td><code>fmt: custom.toml</code></td>
<td>Share one TOML file or keep fmt out of yaml</td>
</tr>
</tbody>
</table>
<p>Omit <code>fmt</code> entirely to use fallbacks: <code>config_root/.mdformat.toml</code>, then upward search from each markdown file, then <strong>Wiki CLI fmt defaults</strong> (<code>wrap: "no"</code>, <code>end_of_line: lf</code>, extensions <code>gfm</code>, <code>frontmatter</code>, <code>wikilink</code>). See <a href="/Wiki_Subcommand_fmt/">Wiki Subcommand fmt</a> for the full resolution order.</p>
<p>Invalid inline keys or values fail when the config loads. Invalid TOML syntax fails when <code>wiki fmt</code> reads the file.</p>
<p>In library code, loaded <code>Config.fmt</code> is a <code>FmtConfig</code> with <code>options</code> (inline mapping) or <code>toml</code> (resolved path under <code>config_root</code>); yaml shapes above are unchanged.</p>
<h2 id="integrity-checks-check-1">Integrity checks (<code>check</code>)</h2>
<p>Under <code>check</code>, each rule is <code>error</code>, <code>warning</code>, or <code>off</code>:</p>
<table>
<thead>
<tr>
<th>Rule key</th>
<th>Default</th>
<th>What it audits</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>missing_layout_file</code></td>
<td><code>error</code></td>
<td><code>wazoo:layout</code> paths that do not resolve to a readable <code>.html</code> file</td>
</tr>
<tr>
<td><code>frontmatter_schema</code></td>
<td><code>error</code></td>
<td>Frontmatter that fails JSON Schema validation</td>
</tr>
<tr>
<td><code>missing_schema_ref</code></td>
<td><code>error</code></td>
<td><code>wazoo:jsonSchema</code> paths or URLs that cannot be loaded</td>
</tr>
<tr>
<td><code>remote_schema_refs</code></td>
<td><code>allow</code></td>
<td>Policy for remote <code>http(s)</code> schema refs: <code>allow</code>, <code>deny</code>, or <code>allowlist</code></td>
</tr>
<tr>
<td><code>remote_schema_hosts</code></td>
<td><code>[]</code></td>
<td>Hostnames permitted when <code>remote_schema_refs</code> is <code>allowlist</code></td>
</tr>
</tbody>
</table>
<p>Build-safety rules (unsafe URL characters, spaces in routes) and output URL collision detection always apply regardless of <code>check</code> settings.</p>
<h3 id="json-schema-frontmatter-wazoojsonschema-1">JSON Schema frontmatter (<code>wazoo:jsonSchema</code>)</h3>
<p><code>wiki check</code> validates frontmatter against JSON Schema in parallel with SHACL. Bind schemas on shape documents with <strong><code>wazoo:jsonSchema</code></strong> beside <strong><code>sh:targetClass</code></strong>; every page whose effective <code>type</code> matches that class must pass the bound schema(s). Individual pages may append extra schemas with their own <code>wazoo:jsonSchema</code> key (scalar or YAML list). Schema refs are local paths under the wiki config root (<code>.json</code> only) or remote <code>http(s)</code> URLs. Remote refs can trigger outbound network requests; set <code>check.remote_schema_refs: deny</code> in CI over untrusted wikis, or <code>allowlist</code> with <code>check.remote_schema_hosts</code> for trusted hosts only.</p>
<p>Shape binding documents are not validated as instances — only their schema refs are checked for loadability. Authoring detail: <a href="/SHACL/">SHACL</a>, <a href="/Style_Guide/">Style Guide</a>.</p>
<h2 id="convention-audits-lint-1">Convention audits (<code>lint</code>)</h2>
<p>Under <code>lint</code>, each rule is <code>error</code>, <code>warning</code>, or <code>off</code>:</p>
<table>
<thead>
<tr>
<th>Rule key</th>
<th>Default</th>
<th>What it audits</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>broken_links</code></td>
<td><code>warning</code></td>
<td>Wikilinks, internal markdown links, heading fragments, assets, <code>wiki:</code> CURIEs</td>
</tr>
<tr>
<td><code>filename_pattern</code></td>
<td><code>warning</code></td>
<td>Full filename vs <code>wiki.filename_pattern</code> regex</td>
</tr>
<tr>
<td><code>headings</code></td>
<td><code>off</code></td>
<td>ATX <code>#</code> headings only (no Setext underlines), sentence-case H2+, H1 title case conventional, numbered headings</td>
</tr>
<tr>
<td><code>thematic_breaks</code></td>
<td><code>off</code></td>
<td>Horizontal rules (<code>---</code>, <code>***</code>, <code>___</code>) in body prose</td>
</tr>
<tr>
<td><code>link_style</code></td>
<td><code>warning</code></td>
<td>Obsidian wikilinks (<code>[[Page]]</code>) in body prose when <code>link.style</code> is <code>standard</code></td>
</tr>
</tbody>
</table>
<h2 id="this-repository">This repository</h2>
<p><code>docs/wiki.yml</code> is the dogfood wiki config: the same structure, block order, and Init columns as <code>wiki init</code> (<a href="https://github.com/wazootech/wiki/blob/main/src/wiki/templates/wiki.yml"><code>wiki.yml</code></a>), plus dogfood overrides — <code>graph.context.wiki</code> for GitHub Pages and <code>graph.content_predicate: schema:articleBody</code> for SPARQL full-text.</p>
<h2 id="related">Related</h2>
<ul>
<li><a href="/Wiki_CLI/#global-options">Wiki CLI</a> — <code>-c</code> and <code>--wiki-inputs</code> global options</li>
<li><a href="/Wiki_Subcommand_init/">Wiki Subcommand init</a> — scaffold a new wiki project</li>
<li><a href="/Wiki_Subcommand_check/">Wiki Subcommand check</a> — integrity checks</li>
<li><a href="/Wiki_Subcommand_lint/">Wiki Subcommand lint</a> — convention audits</li>
<li><a href="/Wiki_Subcommand_query/">Wiki Subcommand query</a> — ad-hoc SPARQL</li>
<li><a href="/Wiki_Subcommand_render/">Wiki Subcommand render</a> — inline SPARQL tables</li>
<li><a href="/Wiki_Subcommand_serve/#sparql-endpoint">Wiki Subcommand serve</a> — <code>#serve-api</code> config block</li>
<li><a href="/Graph_Cache/">Graph Cache</a> — <code>--cache</code> and graph reuse</li>
<li><a href="/Style_Guide/">Style Guide</a> — shapes and frontmatter</li>
</ul>

</body>
</html>
```

### Custom CSS

The Wiki CLI does not copy or link a default stylesheet out-of-the-box. To add styling to your pages:

1. **Edit the layout file** — set `site.layout` in `wiki.yml` to a custom layout file. Link stylesheets in `<head>`, or write inline styles.
1. **Link wiki assets** — place `.css` files under a directory listed in `wiki.assets`, then reference them from the layout, for example `<link rel="stylesheet" href="%wiki.base_url%/assets/site.css">`. Built assets are served at `%wiki.base_url%/assets/…` during `wiki serve` and copied into the build output.

### Custom logos and icons

To customize site logos, icons, favicons, or touch icons:

1. Place your asset files (such as `logo.svg`, `logo.png`, `favicon.ico`) under a directory listed in `wiki.assets`.
1. Reference the assets from your custom layout file, for example:

```html
<img src="%wiki.base_url%/assets/logo.svg" alt="" width="80" height="80">
```

You can also add `<link rel="icon">`, `<link rel="apple-touch-icon">`, or other `<head>` tags directly in your custom layout file.

Built assets are served at `%wiki.base_url%/assets/…` during `wiki serve` and copied into the build output.

See also [Wiki Page Layouts](Wiki_Page_Layouts.md) for `site.layout`, `wazoo:layout`, and packaged layout files.

The metadata pane uses the same RDF serialization path as `wiki export` (compacted JSON-LD, Turtle, N3, RDF/XML, N-Triples, TriG, N-Quads). A compact **Format** chip row switches views without JavaScript. In `wiki serve`, set the initial chip with `?metadata_format=FORMAT` (for example `turtle` or `json-ld`). In `wiki build`, all format views are embedded in the page HTML so the picker works offline.

### Built-in CSS classes and IDs

The wiki builder generates these selectors in the rendered page content:

| Selector                    | Where                                                                                             |
| --------------------------- | ------------------------------------------------------------------------------------------------- |
| `#article-top`              | Read-view `<article>` wrapper around rendered markdown body.                                      |
| `#firstHeading`             | Read-view page title `<h1>`; also Talk / Source / Metadata pane headings. TOC “(Top)” links here. |
| `#siteSub`                  | Subtitle under Talk / Source / Metadata pane headings.                                            |
| `article`                   | Wrapper around the rendered markdown body (`#article-top`).                                       |
| `.layout-label`             | Uppercase type or custom-layout badge in read view.                                               |
| `.toc` / `#toc`             | Table of contents container.                                                                      |
| `#catlinks` / `.catlinks`   | Category links box.                                                                               |
| `.backlinks` / `#backlinks` | Backlinks section.                                                                                |
| `.catlinks-label`           | Categories heading label.                                                                         |
| `.catlinks-list`            | Categories `<ul>`.                                                                                |
| `.infobox`                  | Typed frontmatter property table.                                                                 |
| `.page-meta`                | Infobox class (used for styling).                                                                 |
| `.template-SLUG`            | Per-template class on infobox (e.g. `template-person`).                                           |
| `toclevel-N` / `lN`         | TOC list item classes for heading level N.                                                        |
| `.wikilink`                 | Internal wiki page links.                                                                         |
| `pre[data-copy]`            | Block code with raw source for clipboard copy.                                                    |
| `.code-block`               | Wrapper injected around copyable pre blocks.                                                      |
| `.code-copy-btn`            | Copy button shown on code-block hover/focus.                                                      |

### JavaScript hooks

Custom layout files can utilize standard JavaScript hooks or customize their own. In premium layouts (such as template repositories), the following JavaScript features can be implemented:

| Function                       | Purpose                                              |
| ------------------------------ | ---------------------------------------------------- |
| `switchTab(viewName)`          | Switch between read / talk / source / metadata tabs. |
| `loadTalkNotes()`              | Load per-page local-storage notes.                   |
| `saveTalkNotes()`              | Save per-page notes to localStorage.                 |
| `clearTalkNotes()`             | Clear per-page notes.                                |
| `copySourceCode()`             | Copy markdown source to clipboard.                   |
| `copyPreContent()`             | Copy a `pre[data-copy]` block to clipboard.          |
| `initCodeCopyButtons()`        | Wrap copyable pre blocks and inject copy buttons.    |
| `toggleToc()`                  | Show/hide table of contents.                         |
| `goToRandomArticle()`          | Navigate to a random page.                           |
| `triggerSearch()`              | Execute search and navigate to first match.          |
| `onSearchInput(e)`             | Live search suggestions.                             |
| `handleSearchKey(e)`           | Keyboard navigation for search suggestions.          |
| `navigateSearch(slug)`         | Navigate to a search result.                         |
| `applyCategoryFilterFromUrl()` | Filter index page by `?category=` URL parameter.     |

If the configured page layout file does not exist, the packaged minimal `index.html` layout is used silently — no error.

## Filename conventions

The CLI does not hard-code kebab-case. Projects choose a convention with **`wiki.filename_pattern`**, matched against the **full filename** (including `.md`) on markdown files only.

**Wikipedia-style (recommended):** preserved capitalization and underscores — `Gregory_Davidson.md`, `Pokemon_Diamond_(copy_1).md`, `LLM_Wiki_CLI.md`. Use a pattern such as:

```yaml
wiki:
  filename_pattern: "[A-Za-z0-9_()-]+\\.md"
```

**Kebab-case (optional):** if you prefer `gregory-house.md`, set an explicit pattern (for example `[a-z0-9-]+\\.md`) and enforce it via `lint.filename_pattern`. Wikipedia-style and kebab-case should not be mixed in one wiki.

Page routes keep the casing from the filename; GitHub Pages URLs are case-sensitive.

`wiki link --fix-broken` preserves the existing link kind in each file; only `--apply` uses `link.style`.

When `link.style` is `standard`, `lint.link_style` (default `warning`) flags Obsidian wikilinks (`[[Page]]`) in body prose. Set `lint.link_style: off` to allow wikilinks while keeping standard links as the apply format, or set `link.style: wikilink` for an Obsidian-style wiki.

## Formatting (`fmt`)

Top-level **`fmt`** configures `wiki fmt` (mdformat). Two shapes are allowed — not both:

| Shape          | Example               | When to use                                 |
| -------------- | --------------------- | ------------------------------------------- |
| Inline mapping | `fmt: { wrap: "no" }` | Default; what `wiki init` writes            |
| Relative path  | `fmt: custom.toml`    | Share one TOML file or keep fmt out of yaml |

Omit `fmt` entirely to use fallbacks: `config_root/.mdformat.toml`, then upward search from each markdown file, then **Wiki CLI fmt defaults** (`wrap: "no"`, `end_of_line: lf`, extensions `gfm`, `frontmatter`, `wikilink`). See [Wiki Subcommand fmt](Wiki_Subcommand_fmt.md) for the full resolution order.

Invalid inline keys or values fail when the config loads. Invalid TOML syntax fails when `wiki fmt` reads the file.

In library code, loaded `Config.fmt` is a `FmtConfig` with `options` (inline mapping) or `toml` (resolved path under `config_root`); yaml shapes above are unchanged.

## Integrity checks (`check`)

Under `check`, each rule is `error`, `warning`, or `off`:

| Rule key              | Default | What it audits                                                           |
| --------------------- | ------- | ------------------------------------------------------------------------ |
| `missing_layout_file` | `error` | `wazoo:layout` paths that do not resolve to a readable `.html` file      |
| `frontmatter_schema`  | `error` | Frontmatter that fails JSON Schema validation                            |
| `missing_schema_ref`  | `error` | `wazoo:jsonSchema` paths or URLs that cannot be loaded                   |
| `remote_schema_refs`  | `allow` | Policy for remote `http(s)` schema refs: `allow`, `deny`, or `allowlist` |
| `remote_schema_hosts` | `[]`    | Hostnames permitted when `remote_schema_refs` is `allowlist`             |

Build-safety rules (unsafe URL characters, spaces in routes) and output URL collision detection always apply regardless of `check` settings.

### JSON Schema frontmatter (`wazoo:jsonSchema`)

`wiki check` validates frontmatter against JSON Schema in parallel with SHACL. Bind schemas on shape documents with **`wazoo:jsonSchema`** beside **`sh:targetClass`**; every page whose effective `type` matches that class must pass the bound schema(s). Individual pages may append extra schemas with their own `wazoo:jsonSchema` key (scalar or YAML list). Schema refs are local paths under the wiki config root (`.json` only) or remote `http(s)` URLs. Remote refs can trigger outbound network requests; set `check.remote_schema_refs: deny` in CI over untrusted wikis, or `allowlist` with `check.remote_schema_hosts` for trusted hosts only.

Shape binding documents are not validated as instances — only their schema refs are checked for loadability. Authoring detail: [SHACL](SHACL.md), [Style Guide](Style_Guide.md).

## Convention audits (`lint`)

Under `lint`, each rule is `error`, `warning`, or `off`:

| Rule key           | Default   | What it audits                                                                                                 |
| ------------------ | --------- | -------------------------------------------------------------------------------------------------------------- |
| `broken_links`     | `warning` | Wikilinks, internal markdown links, heading fragments, assets, `wiki:` CURIEs                                  |
| `filename_pattern` | `warning` | Full filename vs `wiki.filename_pattern` regex                                                                 |
| `headings`         | `off`     | ATX `#` headings only (no Setext underlines), sentence-case H2+, H1 title case conventional, numbered headings |
| `thematic_breaks`  | `off`     | Horizontal rules (`---`, `***`, `___`) in body prose                                                           |
| `link_style`       | `warning` | Obsidian wikilinks (`[[Page]]`) in body prose when `link.style` is `standard`                                  |

## This repository

`docs/wiki.yml` is the dogfood wiki config: the same structure, block order, and Init columns as `wiki init` ([`wiki.yml`](https://github.com/wazootech/wiki/blob/main/src/wiki/templates/wiki.yml)), plus dogfood overrides — `graph.context.wiki` for GitHub Pages and `graph.content_predicate: schema:articleBody` for SPARQL full-text.

## Related

- [Wiki CLI](Wiki_CLI.md#global-options) — `-c` and `--wiki-inputs` global options
- [Wiki Subcommand init](Wiki_Subcommand_init.md) — scaffold a new wiki project
- [Wiki Subcommand check](Wiki_Subcommand_check.md) — integrity checks
- [Wiki Subcommand lint](Wiki_Subcommand_lint.md) — convention audits
- [Wiki Subcommand query](Wiki_Subcommand_query.md) — ad-hoc SPARQL
- [Wiki Subcommand render](Wiki_Subcommand_render.md) — inline SPARQL tables
- [Wiki Subcommand serve](Wiki_Subcommand_serve.md#sparql-endpoint) — `#serve-api` config block
- [Graph Cache](Graph_Cache.md) — `--cache` and graph reuse
- [Style Guide](Style_Guide.md) — shapes and frontmatter

Metadata: Wiki Configuration

RDF representation compiled from frontmatter

{
  "@context": {
    "schema": "https://schema.org/",
    "wiki": "https://wazootech.github.io/wiki/"
  },
  "@id": "wiki:Wiki_Configuration",
  "@type": "schema:TechArticle",
  "schema:description": "Reference for wiki.yaml, wiki.yml, and wiki.json (Config).",
  "schema:headline": "Wiki Configuration"
}

@prefix schema: <https://schema.org/> .
@prefix wiki: <https://wazootech.github.io/wiki/> .

wiki:Wiki_Configuration a schema:TechArticle ;
    schema:description "Reference for wiki.yaml, wiki.yml, and wiki.json (Config)." ;
    schema:headline "Wiki Configuration" .

@prefix schema: <https://schema.org/> .
@prefix wiki: <https://wazootech.github.io/wiki/> .

wiki:Wiki_Configuration a schema:TechArticle ;
    schema:description "Reference for wiki.yaml, wiki.yml, and wiki.json (Config)." ;
    schema:headline "Wiki Configuration" .

<?xml version="1.0" encoding="utf-8"?>
<rdf:RDF
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:schema="https://schema.org/"
>
  <rdf:Description rdf:about="https://wazootech.github.io/wiki/Wiki_Configuration">
    <rdf:type rdf:resource="https://schema.org/TechArticle"/>
    <schema:headline>Wiki Configuration</schema:headline>
    <schema:description>Reference for wiki.yaml, wiki.yml, and wiki.json (Config).</schema:description>
  </rdf:Description>
</rdf:RDF>

<https://wazootech.github.io/wiki/Wiki_Configuration> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://schema.org/TechArticle> .
<https://wazootech.github.io/wiki/Wiki_Configuration> <https://schema.org/headline> "Wiki Configuration" .
<https://wazootech.github.io/wiki/Wiki_Configuration> <https://schema.org/description> "Reference for wiki.yaml, wiki.yml, and wiki.json (Config)." .

@prefix schema: <https://schema.org/> .
@prefix wiki: <https://wazootech.github.io/wiki/> .

_:N1d3e37f5219e4daab0bfdabcf3df2702 {
    wiki:Wiki_Configuration a schema:TechArticle ;
        schema:description "Reference for wiki.yaml, wiki.yml, and wiki.json (Config)." ;
        schema:headline "Wiki Configuration" .
}

<https://wazootech.github.io/wiki/Wiki_Configuration> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <https://schema.org/TechArticle> .
<https://wazootech.github.io/wiki/Wiki_Configuration> <https://schema.org/headline> "Wiki Configuration" .
<https://wazootech.github.io/wiki/Wiki_Configuration> <https://schema.org/description> "Reference for wiki.yaml, wiki.yml, and wiki.json (Config)." .

Wiki Configuration

Infobox

Overview

Terminology

Audit lanes

Blocks

Always on

Wiki (wiki:)

Graph (graph:)

Site (site:)

Link (link:)

Integrity checks (check:)

JSON Schema frontmatter (wazoo:jsonSchema)

Convention audits (lint:)

Serve API

Formatting (fmt)

Page layout

Layout strategy

Minimal fallback

Layout slots

Custom CSS

Custom logos and icons

Built-in CSS classes and IDs

JavaScript hooks

Filename conventions

Formatting (fmt)

Integrity checks (check)

JSON Schema frontmatter (wazoo:jsonSchema)

Convention audits (lint)

This repository

Related

ContentsOn this page

Backlinks

Talk / Local Notes: Wiki Configuration

View Source: Wiki Configuration

Metadata: Wiki Configuration

Wiki (`wiki:`)

Graph (`graph:`)

Site (`site:`)

Link (`link:`)

Integrity checks (`check:`)

JSON Schema frontmatter (`wazoo:jsonSchema`)

Convention audits (`lint:`)

Formatting (`fmt`)

Formatting (`fmt`)

Integrity checks (`check`)

JSON Schema frontmatter (`wazoo:jsonSchema`)

Convention audits (`lint`)