Architecture Map Layout
April 17, 2026 · View on GitHub
Layout: Layered system diagram with a dominant core tier, supporting service bands, and a narrow operations strip Best for: Platform overviews, service boundaries, technical blueprints, API ecosystems, stack explanations
Template
Markdown Rendering Platform
Each tier should answer a different question: where content enters, how it is transformed, and which delivery surfaces finally expose it to users.
Input Layer
Markdown Sources
Files, clipboard payloads, generated prompts, synced docs.
Embedded Media
Mermaid, Vega, HTML snippets, canvas assets, images.
Skill Packs
Task-specific instructions that bias transformation and output structure.
Core Processing
Parser Pipeline
AST normalization, plugin hooks, markdown feature expansion.
Renderer Layer
HTML generation, theme application, export-specific transforms.
Messaging Bridge
Host communication across browser, mobile, and editor surfaces.
Observability
Error capture, cache diagnostics, performance traces.
Exporters
Word output, image capture, share bundles.
Clients
VS Code, browsers, mobile shells, Obsidian.