Expand description
Renderers over the Roteiro graph. All outputs — docs site, Obsidian vault,
and the optional MCP server (feature mcp) — are build products of the
same store, so humans and agents always see the same data.
Structs§
- Index
Entry - An entry in the ADR/docs index page.
- Rendered
Adr - A rendered ADR: its title (for the index) and the full themed HTML page.
- Vault
Note - A rendered vault note: its filename (with
.md) and markdown content.
Enums§
- Target
- A render target for the graph.
Functions§
- markdown_
to_ html - Convert
CommonMarkmdto an HTML fragment (GitHub tables + strikethrough, and Roteiro[[wiki-links]]resolved). Resolves ADR links relative to the ADR directory; userender_docfor root-level pages. - note_
name - Map a node key to a filesystem- and wikilink-safe note stem. Characters that
are awkward in filenames or Obsidian links (
:/#whitespace) collapse to-; alphanumerics,.,_and-are kept. - render_
adr - Render one ADR markdown document to a themed HTML page. Leading YAML
frontmatter is stripped; the title is the first
#heading, orfallbackif there is none. ADR[[…]]links resolve to sibling ADR pages. - render_
adr_ index - Render the docs index: any
lifetimedocs (Build Plan, …) then the ADRs. - render_
doc - Render a root-level “lifetime doc” (e.g. the Build Plan) to a themed page.
Its
[[docs/adr/…]]links resolve into theadr/subdirectory. - render_
note - Render a node’s
Explanationinto an Obsidian note: YAML frontmatter, a heading, and its outgoing/incoming edges as provenance-labelled wikilinks.