A form, not a file
Orbit reads your content schema and builds a typed form — dropdowns, dates, image pickers, reorderable lists. Editors fill in fields; you keep your Markdown.
Point Orbit at your site and it reads the shape of your content — an Astro collection’s schema, the fields listed in a content map, or, failing both, the fields your pages already use. Enums become dropdowns, dates get a date field, images get a thumbnail and a picker, and lists can be reordered by drag. Editors never see raw YAML or worry about breaking the file — and your Markdown, frontmatter, and formatting come out exactly as you’d expect, with the smallest possible diff.