Static sites
#The site projection turns a directory of Markdown files into a linked HTML
publication. Source paths become .html routes, local assets are copied or
embedded, and Markdown links are checked against the discovered page set.
Build a directory
margo site ./content --output-dir ./dist --assets local
Use --assets inline when a page should carry its generated dependencies in
the document. The output directory must be new; the site is staged and only
published after the build succeeds.
What the builder verifies
| Input concern | Site result |
|---|---|
| Markdown page path | A deterministic .html route |
| Relative Markdown link | A rewritten route or an actionable error |
| Local image | A copied asset or an inline data URL |
| Page metadata | Canonical, description, and social tags |
| Build output | margo-manifest.json with artifact digests |
A site has a composition boundary
Margo supplies the article and route data. The host selects the visual frame or
shell, maps navigation, and chooses its identity assets. This showcase uses
the public Goshtoso componentdocshell for the header, sidebar, responsive
drawer, dark-mode control, and on-page table of contents.
The content remains plain Markdown. The shell is a presentation choice applied after the document has been rendered.