How this site is built

The site is a static build (SSG): content is loaded once at the server entry, rendered to plain HTML/CSS, and served as files. There is no runtime database and no per-request work — every page is the deterministic output of the content under content/.

The build runs in three stages:

• Load — module, component, and page content is read from content/ and

the framework's generated metadata. - Resolve — Markdown region markers are flattened to their display form, and the docs / reference trees are assembled from each leaf's source. - Render — the component tree emits HTML/CSS with no client-side islands on the content pages, so they stay fast and indexable.

Editing content

Standalone pages like this one live in content/pages/*.md. Each carries a small YAML front-matter header (title, route) and a body that may mix generator-managed regions with hand-written overrides. An override region wins over the managed region for the same key, so regenerating the managed prose never clobbers your edits.

Development status

The Tom framework is still under intensive development. While it stabilises, the project is not accepting pull requests or change requests — the design is still moving too quickly to take outside contributions. Bug reports, on the other hand, are very welcome and genuinely useful; reach the maintainer via the contact details on the About page.