TinaCMS

Tina keeps content in the repository and puts an editing interface on top of it. Markdown, MDX, JSON and YAML files stay exactly where they are, versioned alongside the code, while the people writing work in a UI instead of a text editor.

A GraphQL API sits over those files, so reaching a post's author is a query rather than a parsing exercise, and documents can reference each other. Statically generated and server-rendered pages are both supported, which leaves your rendering strategy to you.

Two audiences are being served at once, and the split is visible in the design.

• Developers: content stays in Git, reviewable in a pull request, with no separate database to reconcile.
• Editors: an optional live preview makes editing Markdown intuitive for people who will never open a code editor.
• Formats: Markdown and MDX alongside JSON and YAML, so structured data and prose share one system.
• References: documents point at other documents and the API resolves the link for you.
• Starters: a single create command scaffolds a working site locally.

You can try it by running a starter on your own machine or spinning up a demo site on TinaCloud, the hosted backend. The declared aim is to be the leading CMS with Git support that developers actually enjoy, and the repository names its maintainers and publishes a roadmap of what comes next.