Vision

I. Make publishing predictable

The system should make it easy to turn content into a live page without bespoke engineering for every site.

II. Keep the source of truth simple

Markdown, frontmatter, and config should carry most of the site’s meaning so forks are easy to understand and extend.

III. Make the framework easy to fork

When someone forks the repo, they should replace the config, swap the sample content, and have a working site quickly.

IV. Support optional integrations

Workers, APIs, search, analytics, and webhooks should be optional instead of mandatory.

V. Keep the sample content useful

The repository should demonstrate real layouts, real content models, and real publishing flows without locking the project to one customer.

VI. Support content operations

Publishing, review, deployment, and later analytics should all fit the same mental model.

VII. Stay maintainable over time

The code should remain understandable enough that the next fork can keep evolving without a rewrite.