TinaCMS content, edited as forms in Xodia

Each field in your Tina schema becomes the input that suits it, and dates keep the exact format they were written in.

• Collections in Markdown, MDX, JSON or YAML, with the title field you marked as each entry's name
• Strings, text areas, colors, options, numbers, booleans, dates and times, lists and objects
• Image fields with Upload into the media folder your config sets, or pick one already there
• References to other entries, saved as the file path Tina expects
• Collection templates, with the template each entry uses, and the body in Markdown with a formatting bar
• Your AI follows Xodia's git-based CMS skills for Tina. See Agent skills

Tina keeps its content in your repo, so Xodia reads it from there. No token, no account.

1. Import your site from GitHub, or open its folder on your computer.
2. Xodia finds tina/config and reads it as text. Your config code never runs.
3. Open the Content tab, pick a collection and edit an entry.
4. Save: the change becomes a commit on your branch and goes live when you publish.