Key takeaways
This example post shows what an article looks like on a Launchpad site. Edit it in the Keystatic admin at /keystatic while developing, or publish new ones from your content platform through the webhook.
- Posts are plain files in the repository, so every publish is a commit and a deploy.
- The admin UI at /keystatic edits them locally; the webhook creates them in production.
- Headings become a table of contents, questions become FAQ structured data.
Why files instead of a CMS
Every post on this site is a folder under content/posts with one index.mdoc file: YAML frontmatter for the metadata and a Markdoc body for the text. There is nothing to host, nothing to pay for and nothing that can go down.
Writing locally
Run the dev server and open /keystatic. The admin UI edits the files in your working tree, so a new post is just a commit.
Images
Images dropped into the editor are saved under public/images/posts/<slug>/ and referenced by their public path, so they ship with the site.
Publishing from your content platform
Connect the site's webhook endpoint in your content platform. Each publish is signed, verified, turned into the same files and committed to the repository, which triggers a new deployment.
Everything a visitor sees on this page came from one file. That is the whole system.
Related questions
- How do I publish a new article?
- Can I edit an article after it is published?
