Content in your repo, edited as forms
If your content lives as files in your repo, Xodia's Content tab already edits it: Markdown, MDX and YAML entries, Astro content collections and Keystatic folders. Writers fill in forms, and every change is saved as a commit with the rest of your edits.
Free plan. 14-day Pro trial. No charge unless you choose a plan.
The Content tab on an Astro site: a draft post open as a form with its title, date, tags, cover image and Markdown body, with Set live and Save.
What you can do
Every entry, with its state
The Content tab lists each collection and its entries, with whether each one is live, changed or a draft.
- One file per entry in Markdown, MDX, Markdoc or YAML, or a JSON file that lists every entry
- Forms from your Astro collection schema, or from the fields your entries already have
- The body in Markdown with a formatting bar, and frontmatter that keeps its comments and order
- Keystatic's .mdoc entries and YAML data collections in the same tab
- Your AI follows Xodia's skills for Keystatic, Decap and TinaCMS: their config, media folders and dev commands
The Content tab: a bakery site's menu collection, with each entry's status as Live, Changes or Draft.
How to set it up
Nothing to connect
The content is already in your repo, so Xodia reads it from there.
- Import your site from GitHub, or open its folder on your computer.
- Keep entries in a content or src/content folder, or in Astro content collections. Your AI can move a collection there or set one up.
- Open the Content tab, pick a collection and edit an entry.
- Save: the change becomes a commit on your branch and goes live when you publish.
Settings, General: Xodia detected an Astro 6 site with Tailwind 4, npm and Netlify, with its content in Keystatic.
Plans
Which plan you need
Editing in the Content tab comes with Starter, Pro and Agency; on Free you can read entries there. Your AI's skills for git-based CMSs come with Starter, Pro and Agency.
Free
CMS editing: not included
Starter
CMS editing: included
Pro
CMS editing: included
Agency
CMS editing: included
Limits
Good to know
- Markdown folders outside content and src/content aren't listed unless an Astro collection loads them; your AI edits those files
- Decap's and TinaCMS's own editors stay as they are; Xodia edits the files they write
- On a TinaCMS site the preview runs your framework's dev server without tinacms dev, so Tina's local content API isn't running there
- Markdoc tags show as text in the Markdown editor
Questions
Git-based CMS questions
Do I need a CMS at all?
No. A folder of Markdown files is enough. Xodia finds it and lists its entries, and your AI can set up a collection if you don't have one.
Where do content changes go?
Into your draft, like every other edit. Saving makes them a commit on your branch, and publishing puts them on your live site.
Can I keep using Decap or TinaCMS?
Yes. Xodia doesn't change their config. Both edit the same files, so writers can use whichever they like.
Does it work with Sanity too?
Yes, Sanity is the headless CMS the Content tab edits. See Sanity.
Keep exploring
Related pages
- CMSContent files, collections and Sanity
- SanityDocuments as forms, drafts to live, publish and discard
- AstroVisual editing for Astro sites
- GitHubImport repos, save as commits, branches and pull requests
- Git and publishingDrafts, restore points, branches and publish
- For freelancersClients edit safely, you review
- IntegrationsEvery tool Xodia works with
- PricingPlans, limits and the free trial