Keystatic content, edited as forms in Xodia
Xodia reads your keystatic.config and opens each collection and singleton in the Content tab, with the fields you defined. Change an entry, upload a photo into its folder, and the 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 with Keystatic: the Menu, Posts and Settings collections from keystatic.config.ts, and the Menu entries with their price, category and whether each is available, Morning buns marked unsaved.
What you can do
The fields you defined, as a form
Each field in your Keystatic schema becomes the input that suits it, so writers fill in a form instead of editing YAML.
- Collections and singletons, each entry in the layout Keystatic writes: YAML or JSON data, with a .mdoc or .mdx body file where the schema has one
- Text, numbers, dates and times, links, selects and multiselects, checkboxes, relationships to other entries, objects and arrays
- Image and file fields with Upload, into the directory each field names, or pick one already there
- The body in Markdown with a formatting bar and a preview
- Your AI follows Xodia's git-based CMS skills for Keystatic. See Agent skills
A Keystatic menu entry open in the Content tab: name, price, a category select, allergens as chips, the photo with Upload and Choose from public/images/menu, and Available, with Save.
How to set it up
Nothing to connect
Keystatic keeps its content in your repo, so Xodia reads it from there. No token, no account.
- Import your site from GitHub, or open its folder on your computer.
- Xodia finds keystatic.config and reads it as text. Your config code never runs.
- Open the Content tab, pick a collection or a singleton 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 entries and uploading in the Content tab come with Starter, Pro and Agency; on Free you can read every entry there. Your AI's skills for Keystatic come with Starter, Pro and Agency.
Free
CMS editing: read repo content
Starter
CMS editing: included
Pro
CMS editing: included
Agency
CMS editing: included
Limits
Good to know
- An image field without a directory keeps the image next to its entry; uploads can't go there yet, so type the path or ask your AI
- Blocks fields open as JSON data, not as a form per block
- Markdoc tags show as text in the Markdown editor
- Keystatic's own admin stays as it is; Xodia edits the files it writes
Questions
Keystatic questions
Do I need to change my Keystatic config?
No. Xodia reads the config you have, collections and singletons, paths, formats and fields, and writes entries in the same layout Keystatic does.
Can writers keep using Keystatic's admin?
Yes. Both edit the same files in your repo. Changes made in Xodia wait as a draft until you save, then they are a commit like any other.
Where do uploaded images go?
Into the directory the image field names in your config, with a short unique ending on the file name so nothing is overwritten. Images and documents up to 5 MB.
Which frameworks does this work with?
Any site whose keystatic.config is in the repo. On Astro, Next.js and the other click to edit frameworks you can also edit the pages themselves on the canvas.
Keep exploring
Related pages
- Git-based CMSMarkdown and MDX files, Keystatic, Decap, TinaCMS and Nuxt Content
- CMSContent files, collections and Sanity
- Decap CMSFolder and file collections from config.yml, as forms
- TinaCMSCollections from tina/config, with uploads to Tina's media folder
- AstroVisual editing for Astro sites
- Git and publishingDrafts, restore points, branches and publish
- IntegrationsEvery tool Xodia works with
- PricingPlans, limits and the free trial