Frontmatter Core · MIT
Extract a stable data contract from Astro.
Core scans Astro, Markdown and YAML and writes a typed JSON intermediate representation. Solo and Studio consume that IR. Core is not a CMS.
Build-time only. No runtime. No lock-in.
Input
- .astro pages and components
- .md content files
- .yaml datasets
Core scanner
- Reads the project tree
- Extracts routes, props, fields
- Writes a typed JSON IR
Output
- JSON IR
- Pages, datasets, routes
- Stable contract for later tools
What the IR contains
The IR is structure, not rendered HTML and not an admin UI. Component props, pages, datasets and routes are represented as data:
{
"pages": [
{
"route": "/",
"layout": "Base",
"fields": ["title", "subtitle"]
}
],
"components": [
{
"name": "Hero",
"props": ["headline", "sub"]
}
],
"datasets": ["works", "posts"]
}What Core does not do
- it is not a CMS or visual editor
- it does not generate Twig, PHP or Grav files
- it does not create editable content models in a backoffice
- it does not fetch, store or publish content
- it adds no runtime to your site
Solo consumes the IR.
Frontmatter Solo reads the same intermediate representation and prints Twig or plain PHP templates plus INTEGRATION.md. Core stops at the contract. Solo starts at generation.
Studio builds on the pipeline.
Studio is coming soon. It is planned to sit on Core and Solo to produce a Grav theme, blueprints and an editable data layer. Studio is not released and is not a generic headless CMS.
Open by design.
Frontmatter Core is MIT licensed. You can read it, fork it, and build other tools on the same IR. Paid products stay outside the core.