Nuxt Content collections, edited as forms in Xodia
Xodia reads your content.config and opens each page and data collection in the Content tab, with fields from your schema. Writers fill in a form instead of editing Markdown or YAML, and every change is saved as a commit.
Free plan. 14-day Pro trial. No charge unless you choose a plan.
The Content tab on a Nuxt site with Nuxt Content: the Blog, Menu and Team collections from content.config.ts, and the menu items with their price, category and whether each is vegan, Morning buns marked unsaved.
What you can do
Your schema, as a form
The fields come from each collection's z.object schema, so a choice is a select, a number is a number and yes or no is a checkbox.
- Page collections in Markdown, with a title and description on every entry and the body in a Markdown editor
- Data collections in YAML or JSON, one file per entry
- Text, numbers, dates, booleans, enums, lists and objects from your schema
- Image paths with a thumbnail and Upload into your site's public folder
- Collections that read files from content/ or from the folder you set with cwd
A Nuxt Content menu item open in the Content tab: name, price, a category select, the photo with Upload and Choose from Assets, and Vegan, with Save.
How to set it up
Nothing to connect
Nuxt Content keeps its content in your repo, so Xodia reads it from there. No token, no account.
- Import your Nuxt site from GitHub, or open its folder on your computer.
- Xodia finds content.config and reads it as text. Your config code never runs.
- 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 Nuxt 4 site with Tailwind 4, pnpm and Netlify, with its content in files in the repo, and marks it Preview and agent.
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.
Free
CMS editing: read repo content
Starter
CMS editing: included
Pro
CMS editing: included
Agency
CMS editing: included
Limits
Good to know
- Click to edit isn't available on .vue pages yet: edit the content here, and the pages through your AI or the Code tab
- Collections that read from a remote repository, and CSV collections, aren't listed
- Nuxt Content v3's content.config is read; on sites without one, the Markdown folders in content/ are listed
- Markdown components (MDC) show as text in the Markdown editor
Questions
Nuxt Content questions
Do I need to change my content.config?
No. Xodia reads the collections you have, their type, source folder and schema, and writes each entry back as Markdown, YAML or JSON in the same place.
Can I click to edit my Nuxt pages?
Not yet. Nuxt sites get the live preview, the Code tab and your AI, and the Content tab for your collections. See Nuxt and Vue.
Where do uploaded images go?
Into your site's public folder, with a short unique ending on the file name so nothing is overwritten. Images up to 5 MB.
Does my AI know Nuxt?
Yes. Your AI follows Xodia's Nuxt and Vue skills for page meta, the app folder and public files. See Agent skills.
Keep exploring
Related pages
- CMSContent files, collections and Sanity
- Git-based CMSMarkdown and MDX files, Keystatic, Decap, TinaCMS and Nuxt Content
- KeystaticCollections and singletons from keystatic.config, as forms
- Bring your AIClaude, Cursor and any MCP app, with Xodia's tools and skills
- Git and publishingDrafts, restore points, branches and publish
- IntegrationsEvery tool Xodia works with
- PricingPlans, limits and the free trial