All features Visual editor

A proper editor for writers, not developers.

Rich text, Markdown shortcuts, structured fields and your own Astro components — in an editor that writes clean files to your repo and never gets in your way.

Try the live demo Connect your repo

/ src / content / guides / writing-with-skills.mdx

Writing with skills

Audit now

Content Fields History

Visual Code

A skill is a short Markdown file the agent reads before it writes. Brand voice, SEO rules, image style — write it once and every draft follows it.

Skills live in your repo under skills/, so they're versioned, reviewed and shared with the whole team like any other file.

› Callout <Callout />

Start with one skill for voice. Add rules only when the agent gets something wrong twice.

What goes in a skill

Three things, roughly:

Edit content without touching code.

Writers get a document. Developers get clean Markdown, MDX and frontmatter in the repo — exactly where they'd have put it themselves.

Any block in two keystrokes.

Type / anywhere. Headings, lists, tables, code, images — and every .astro component in your project, read straight from the repo.

Forms, straight from your schema.

Zero reads the Zod schema of every collection and builds the fields from it. Enums become dropdowns, dates get pickers, limits are enforced as you type. Nobody has to edit raw YAML.

Your components, as forms.

Props become inputs. Nested children stay editable. The import statement is written for you — the writer never sees it, the developer never has to fix it.

AI inside the editor, not beside it.

Select a passage, hit Ctrl/⌘ + Shift + K or use the toolbar. Rewrite, expand, translate, or fix the tone — with your skills applied. Pick a model you prefer per task.

src / content / guides / first-week.mdx

Welcome aboard. This week is about making one small, doable habit stick.

› Callout <Callout />

Pick just one habit for week one. We know it's tempting to overhaul your whole life — resist it.

Saved · 2 unpublished changes Agent

Images land in your repo.

Paste or drag an image into the body or an image field. Zero stores the file next to your content and writes the relative path. No bucket to configure.

Markdown shortcuts work.

## for a heading, **bold**, - for a list. People who know Markdown never have to reach for the toolbar.

Switch to code anytime.

One toggle between the visual editor and the raw file. Both edit the same file — nothing is translated or lost in between.

Validation before publish.

Required fields, length limits and enum values are checked inline while you write. Schema changed in the repo? The form updates on its own.

File types

One editor. Whatever the file.

A blog post, a settings file, the site navigation — Zero opens each as the right kind of editor and writes back exactly the format the repo expects.

writing-with-skills.mdx about.md general.yaml nav.json

Each tab opens the same file in two panes: a visual editor on the left, and the raw file Zero writes to the repository on the right.

src / content / guides / writing-with-skills.mdx

What Zero writes writing-with-skills.mdx

---
title: Writing with skills
status: draft
tags: [agent, skills, guide]
---
import Callout from '@/components/mdx/Callout.astro'

A skill is a short Markdown file the agent
reads before it writes. Brand voice, SEO
rules, image style — write it once and every
draft follows it.

<Callout>
  Start with one skill for voice. Add rules
  only when the agent gets something
  wrong twice.
</Callout>

Three things, roughly:

src / content / pages / about.md

What Zero writes about.md

---
title: About us
description: A small team in Helsinki.
---

# About us

We're a small team in Helsinki building the
CMS we always wanted: one that lives in the
repo and gets out of the way.

## What we believe

- Content is code. Treat it with the same care.
- Writers deserve a document, not a form.
- The agent works for the team, not

src / content / settings / general.yaml

What Zero writes general.yaml

brand: Zero
contact_email: hello@zerocms.io
copyright: © 2026 ZeroCMS
nav:
  - label: Home
    href: /
  - label: Guides
    href: /guides

src / content / data / nav.json

What Zero writes nav.json

{
  "items": [
    {
      "label": "Features",
      "href": "/features"
    },
    {
      "label": "Pricing",
      "href": "/pricing"
    },
    {
      "label": "Resources",
      "href": "/resources"
    }
  ],
  "ctaLabel": "Get started",
  "showLogin": true
}

Questions about the editor.

Something else on your mind? Email us — a human replies.

Which schema field types does the visual editor support?

ZeroCMS has built-in editors for text, numbers, toggles, dates, date-times, lists, objects, dropdowns, tags, image fields, and relation fields. Complex schemas and deeply nested custom objects are supported.

Are nested or child components supported?

Yes. The visual editor supports nesting components inside other components, and every level stays fully editable through the same visual interface.

What if my schemas change?

ZeroCMS automatically detects schema changes for both frontmatter and components, and updates the UI accordingly.

Which file types does the visual editor support?

Markdown, MDX, JSON, and YAML.

Is it possible to edit the raw files?

Yes. Users can switch between the visual editor and a code editor at any time.

Give your whole team a proper editor.

Connect Zero to your Astro repo and writers can start editing in minutes — no code changes, no new tooling to learn.

Connect your repo for free Talk to us