A focused CMS for Astro teams

Give editors forms. Keep everything in Git.

Mica turns your content model into a clean editing interface. Editors draft in peace, review what changed, and publish one commit of readable JSON, Markdoc, and media. Your Astro build stays static and independent.

Start in five minutes View on GitHub

npm install @micacms/astro @micacms/core

Mica 0.2.0 is available

src/mica.tsTypeScript

// One model. The editor and the build both read it.
export const site = defineSite({
  collections: {
    projects: collection({
      label: "Projects",
      fields: {
        title: text({ required: true }),
        slug: slug({ from: "title" }),
        story: richText(),
        gallery: media({ multiple: true }),
      },
    }),
  },
});

FormsValidationTypesFilesCollections

0content records in MicaFiles stay in Git

1commit per publishAtomic by design

16field typesOne typed model

8composable packagesUse only what you need

Your repository is the source of truth

A CMS should not become part of your website's runtime.

Mica gives non-technical editors a good interface without putting content behind an API. The public website reads local files at build time. It stays fast, portable, and available even when Mica is offline.

01 · EDITORSomeone writes in Mica
generated forms
02 · SOURCEYour repository
content/
03 · BUILDAstro reads local files
getCollection()
04 · OUTPUTStatic files on any host
HTML + CSS + assets

The published website never contacts Mica.

From model to production

One model. One clear path from edit to website.

The content model connects the editor and the build. Git connects everything else.

Step 1

Describe

Define collections, fields, validation, labels, and editor help in one TypeScript module.

src/mica.ts

Step 2

Edit

Mica reads the model and gives your team generated forms, media tools, and safe validation.

JSON + Markdoc + media

Step 3

Ship

Drafts stay with the editor until Publish turns them into one commit. Your existing CI runs Astro and sends static files to any host.

publish → astro build

For the people who write

A real editor, not a repository in nicer colours.

Model-generated forms give editors the controls they need. Validation happens before an entry reaches the repository.

Pages /

Getting started

Savedmain · content/docs/getting-started/

Title

Section

Start

Read time

8 min

Summary

Add Mica to an Astro 5 project and open the local editor.

Guide

BIH2

What you need

Mica adds an editing interface to an Astro project. The website still reads local files.

Focused field controlsMarkdoc rich textMedia and relationsConflict protection

Small surface. Strong guarantees.

The content workflow that Git already wanted.

Mica removes the glue between a content editor and an Astro project. It does not add a second platform to operate.

Source of truth

Git-native content

Content is readable files in your repository. Every publish is one commit, ready for review, rollback, and your normal CI.

No schema drift

One typed model

One TypeScript module defines the editor, validation, file layout, Astro collections, and page data types.

Calm authoring

Editor-first forms

Give editors purpose-built fields, focused rich text, media selection, relations, and useful validation messages.

Safe collaboration

History without a revision table

Git keeps the history. Per-entry revision checks stop stale edits without blocking people who work on different content.

No media server

Media that ships with the site

Images are repository files. Astro optimizes them at build time, so the public site does not fetch assets from Mica.

Operate less

A small, secure runtime

Deploy one container. OpenID Connect gives identity, and one setting gives permission. SQLite holds sessions, but never website content.

Built with a point of view

Less infrastructure. More ownership.

Own the source

Content stays in formats that people, Git, and Astro can read without Mica. There is no export step.

Use the web you have

Keep your repository, CI, static host, and identity provider. Mica fits the path instead of replacing it.

Say no on purpose

No page builder, GraphQL layer, media server, or custom workflow. The smaller product is the more reliable product.

Ready when your repository is

Your Astro site is already close.

Add two packages, write one content model, and open the editor. Your templates remain ordinary Astro.

Read the quick start

Experimental · v0.2.0 · MIT