Method
Structuring a knowledge hub
Why a hub needs a spine of durable pages before it needs a feed, and how to tell the two apart.
Editorial hub
A theme for writing meant to be read twice
Atlas is built for research notes, technical essays and reference pages — the kind of writing people arrive at from a search result years after publication.
Recent writing
Standards
Writing for citation
What a long-form technical page owes a reader who arrives from a search result three years later.
Practice
Editorial standards
Corrections policy, sourcing, and the difference between an update and a rewrite.
What makes it a reading theme
The body column is set in a serif at a 72-character measure with looser leading than the other themes in this suite. Navigation, buttons and table headers stay on the interface face, so only the prose carries the serif — a distinction that matters once a page runs past a screenful.
Corners are nearly square, shadows are faint, and there is no accent gradient anywhere. The design gets out of the way.
Structure over feed
A knowledge hub needs durable pages more than it needs a stream. Atlas gives you an articles index, a papers index and an about page carrying editorial standards, all built from Markdown you control.
RSS, Atom and JSON Feed are generated by the generator from the same content and linked in the document head, so readers who do want a stream get one without you maintaining a second thing.
What it is not
Atlas ships no comment system, no newsletter capture, no share buttons and no reading-progress bar. Each of those is a third-party request, a consent obligation, or both. Add them deliberately if you need them.