Welcome to magicms

MagiCMS is a block-based CMS for Astro. It generates a normal Astro project (the scaffold) and a web editor that writes JSON into that project. There is no hidden content database: Git is the history.

You need ordinary web-dev skills (Git, JSON, a local Node toolchain). You do not need to have used MagiCMS before. The editor is how you and your team change pages; Astro is how the public site is built.

• Developers building content-driven Astro sites who don't want to hand-roll a CMS layer.
• Content editors and marketers who need a clean UI for managing pages, collections and globals.
• Designers who want to ship a custom-themed site without per-page layout work.

MagiCMS is organised around a schema (the fields in the editor) and these content types:

• Pages — URLs, built as a tree of blocks (and optional sections).
• Blocks — reusable page sections (hero, text, cards, …).
• Sections — optional wrappers around a group of blocks (for example a theme band).
• Collections — repeating entries such as team members or articles.
• Globals — one-off site data (name, theme, cookie banner, icons).
• Page types — extra fields for children of a navigation item (this docs section is one).

You do model data: you install blocks and, when needed, you edit schemas for collections, globals and page types. MagiCMS then generates the forms. Full picture: Content model.

The Astro scaffold is the site on disk: layouts, routes, blocks, src/content/. You own custom components and styling. MagiCMS owns a small set of generated registries (see Auto-generated files).

The MagiCMS web editor opens that same project from a local folder, GitHub, or a hosted MagiCMS project. Day-to-day use is on Using MagiCMS.

On GitHub, saves go to draft. Cloudflare Pages builds that branch for editor preview. Publish merges into main, where production (Bunny) usually runs.