Decap CMS content, edited as forms in Xodia
Xodia reads your Decap config.yml and opens its folder and file collections in the Content tab, with the widgets you set up as fields. Edit a post or a page, upload into your media folder, and save it as a commit.
Free plan. 14-day Pro trial. No charge unless you choose a plan.
The Content tab on a site with Decap CMS: the Blog folder collection and the Home and Visit us pages from public/admin/config.yml, and the blog's posts with their date and category, one a draft and one unsaved.
What you can do
Your widgets, as fields
Each widget in your config becomes the input that suits it, and new entries get their file name from your slug setting.
- Folder collections with one file per entry, in Markdown with frontmatter, YAML or JSON
- File collections, each file opened as a single entry
- String, text, number, boolean, date and datetime, select, relation, list, object and color widgets
- Image and file widgets with Upload into your media folder, and image galleries
- A draft switch on collections with a draft field, and the Markdown body with a formatting bar
- Your AI follows Xodia's git-based CMS skills for Decap. See Agent skills
A Decap blog post open in the Content tab: title, date, a category select and the featured image with Upload and Choose from public/images/uploads, with Make draft and Save.
How to set it up
Nothing to connect
Decap 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 config.yml in admin, public/admin or static/admin and reads its collections.
- 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 a Next.js site with Tailwind 4, npm and Netlify, with its content in Decap CMS.
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 Decap 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
- Collections in TOML, or JSON frontmatter, aren't listed yet; your AI edits those files
- A media folder set relative to the entry keeps images next to it; uploads can't go there yet
- List widgets with several types open as JSON data
- Decap's own admin and its editorial workflow stay as they are; Xodia edits the files in your repo
Questions
Decap CMS questions
Do I need to change my config.yml?
No. Xodia reads the config you have: collections, folders, file names from your slug setting and the media folder.
Can editors keep using Decap's admin?
Yes. Decap and Xodia edit the same files. Changes made in Xodia wait as a draft until you save, then they are a commit on your branch.
Where do uploaded images go?
Into the media folder from your config, with a short unique ending on the file name so nothing is overwritten, and the field gets the public path. Images and documents up to 5 MB.
Does it work if my site isn't on Netlify?
Yes. The Content tab reads the files in your repo, wherever you host. Connect your host to see deploys next to your edits; see Integrations.
Keep exploring
Related pages
- Git-based CMSMarkdown and MDX files, Keystatic, Decap, TinaCMS and Nuxt Content
- CMSContent files, collections and Sanity
- KeystaticCollections and singletons from keystatic.config, as forms
- TinaCMSCollections from tina/config, with uploads to Tina's media folder
- NetlifyLive address, domains, deploys and build errors
- Git and publishingDrafts, restore points, branches and publish
- IntegrationsEvery tool Xodia works with
- PricingPlans, limits and the free trial