Skip to content
Glossary

#Glossary

Atom feed
An XML feed (feed.xml) that allows RSS readers to subscribe to documentation updates. Pages can opt out with feed = false in frontmatter. Source
Build pipeline
The seven-stage process that transforms Markdown templates into a static HTML site: scan, resolve, tokenize, render, post-process, generate HTML, auxiliary output. Source
Callout
A content directive that renders a styled admonition box. Types include callout-note, callout-warning, callout-tip, callout-danger, and callout-important. Source
Canonical URL
The definitive URL for a page, set via the base_url config field. Used in <link rel="canonical"> tags and sitemaps to avoid duplicate content in search engines. Source
Code block
A fenced block of source code (triple backticks) that gets syntax-highlighted in the rendered output. Consecutive code blocks with different languages become tabbed. Source
Content directive
A directive that transforms body content into styled HTML without needing source code access. Includes callouts and list-glossary. Source
Coverage
The proportion of public symbols in your source code that are documented through directives. Reported by selfdoc check and held to the coverage_threshold fraction in selfdoc.json. Source
Custom directive
A project-specific directive defined in selfdoc.json that points to a script resolving it. A .py script defines resolve(attrs, config, body) and is called by an embedded Python driver; any other script is executed directly. Takes priority over the code-extraction directives, not over content directives. Source
Directive
A marker in Markdown templates that selfdoc resolves into content at build time. Comes in one-liner (:-:) and block (:<: ... :>:) forms. Source
Extractor
A language-specific component that reads source code and extracts API information for directives. Selfdoc ships with extractors for Go, Python, TypeScript, Svelte, Zig, Dart, Kotlin, Swift and SQL. Source
Frontmatter
The TOML metadata block at the top of a Markdown file, between +++ fences. Its keys are a declared registry: title, description, nav group and the rest of a page's settings. Source
JSON-LD
Structured data embedded in each HTML page as a <script type="application/ld+json"> block. Provides search engines with machine-readable metadata about the page. Source
Lint rule
An SEO or content quality check run by selfdoc check. Each rule has a code (e.g., SEO001) and produces warnings or errors with file locations. Source
Nav group
A frontmatter field (nav_group) that controls which section of the sidebar navigation a page appears in. Pages with the same nav group are grouped together. Source
OG card
An OpenGraph image generated for each page, used as the preview image when a link is shared on social media or messaging platforms. Source
Post-processor
A transform that runs on the rendered HTML after block rendering, to detect cross-block patterns like consecutive code blocks (code tabs) or ordered lists after tutorial headings (step guides). Source
Resolver
The dispatch layer that routes a parsed directive to the correct handler -- content directives, custom directives, or language extractors, in that order. Source
Search index
The Pagefind index under pagefind/, built from the finished HTML pages, powering the client-side full-text search in the rendered site. Source
Sitemap
An XML file (sitemap.xml) listing all page URLs and their last-modified dates, used by search engines for indexing. Source
Slug
The URL-friendly identifier derived from a page's filename. For example, getting-started.md becomes the slug getting-started, served at /getting-started/. Source
Staleness
When a page's content has changed since the last build but its frontmatter description has not been updated. Detected by comparing content and description hashes. Source
Theme
A set of CSS custom properties controlling colors, typography, layout, and component styling. Every theme's stylesheet is compiled into the binary, and the set of embedded stylesheets is the registry of theme names. Source
Tokenizer
A standalone module that splits Markdown into typed block tokens (headings, code blocks, tables, paragraphs, etc.) used by both the renderer and the lint system. Source

More tools from this site

  • claudestream Drive Claude Code from Python: run it as a subprocess and read its output as typed events, with async and sync sessions, sandbox policies, and tools you define in Python
  • claudewheel A TUI Claude Code Launcher that lets you have more than one profile, manage sessions lifecycle, pick the exact CC version, model to use (even older unlisted ones), pick which GitHub account to use, etc.
  • dirstat Fast, single-binary directory statistics CLI: every file under a tree grouped by format, with counts, sizes, and lines of code, as a colored terminal table or as JSON
  • fastware A batteries-included ASGI framework: msgspec JSON, a managed Granian server, dependency injection, SSE, WebSockets, auth, and a test client
  • go-toml-edit Zero-dep TOML editing library for Go with comment preservation
  • howmuchleft The fastest Claude Code statusline: context window, 5-hour, and weekly limit usage as three customizable gradient bars, rendering in about 6 ms
  • orxtra
  • pgdesign
  • predraw Declarative rendering pipeline: describe a scene in JSON and get SVG, PNG and WebP out, with light and dark style tokens, reusable components and text converted to path outlines
  • reposummary Turn a git repository's history into a Markdown journal: pick a time window or revision range and get a readable digest of what changed, optionally narrated by an LLM
  • rlsbl Release orchestration and project scaffolding CLI that bumps versions, validates a structured JSONL changelog, tags only the commit CI verified, and publishes to npm, PyPI, Go and more
  • safegit git wrapper CLI that gives each commit its own temporary index and retries ref updates on conflict, so concurrent agents share one repository
  • saferm Command-line replacement for rm that archives every deletion with a mandatory reason and the context it ran in, so deleted files can be listed, inspected and restored
  • strictcli
  • stricttest An always-on test-isolation floor: a pytest plugin and a Go env-hygiene module that make a test suite structurally unable to reach real credentials, the real HOME, the network, or the development repository.
  • wesktop A Python framework that turns an ASGI web app into a desktop application, serving it from a local Granian server and displaying it in a native OS window via pywebview
Search