The repository stays canonical
Content, configuration, history, and review remain in the place your work already lives.
A publishing framework for Git-native authorship
Your work deserves more than a README.
Turn the repository where the work happens into a coherent public home for documentation, essays, projects, research, and product knowledge.
$
npx tidypress init --preset docs-writing tidypress / publishing model 01
One source tree.
A complete public body of work.
Author in Markdown · MDX · notebooks
Shape with collections · themes · routes
Publish as static site · searchable content · Markdown
Structure carries meaning
Docs, essays, projects, references, and custom collections keep their own public shape.
The result remains yours
Build portable static files and complete published Markdown without a proprietary runtime.
The work and its explanation belong together
Keep the evidence close.
Publish the meaning clearly.
A repository often contains the code, experiments, decisions, and drafts behind a body of work. TidyPress gives that material an information architecture and a public surface without splitting authorship across another system.
- People
- Read a clear, deliberate interface.
- Teams
- Review the source through familiar Git workflows.
- Agents
- Receive complete, structured published context.
One repository, distinct public forms
Give each kind of work the space it needs.
Start narrow. Add new surfaces when the work asks for them.
Documentation
Guides, concepts, procedures, and exact reference arranged for learning and lookup.
Writing
Essays, research notes, field reports, and releases with dates, authors, and topics.
Projects
Outcomes, status, links, evidence, and the context that a repository card cannot carry.
Your collections
Research, methods, works, changelogs, or the vocabulary particular to your practice.
Framework, not takeover
A useful default with an honest exit.
Begin with a complete publishing system. Replace the theme, a component, a route view, or an entire collection when the baseline stops fitting. The generated site is still a folder of files you can inspect, host, archive, and move.
Read the architecture →project/the repository you own
├─ src/content/canonical writing
├─ tidypress.config.tspublic structure
├─ src/styles/your visual language
└─ build/portable publication
Enter at the layer you need
Start with the job in front of you.
From the workshop
Writing
The build folder is your exit plan A practical test for whether a publishing system gives you ownership or merely lets you store Markdown inside it.
A README cannot carry a body of work Why developers, research labs, and independent builders need more than one giant page to make their work understandable.
A notebook is evidence. It is not yet a publication. A concrete workflow for turning computational work into something a collaborator, reviewer, or future self can actually read.