This post — and every page under /blog and /docs — is written in Markdown and lives in the content/ directory of the app. There is no database and no CMS server to run: the files are read straight from the repository at request time, so shipping a new article is just committing a new file.
Why file-based content
Keeping marketing and documentation content in Git has a few nice properties:
- Versioned like code. Every edit is a commit, reviewable in a pull request.
- No extra infrastructure. Nothing to host, back up, or keep online.
- Portable. The same Markdown renders in your editor, on GitHub, and on the site.
What's next
Have a look around:
- The documentation walks through getting the project running.
- The rest of the blog shows how a multi-post index and pagination behave.
When you're ready to make it yours, replace the files in content/posts and content/documentation with your own — the routes, navigation, and styling all pick them up automatically.