Editing content
Sections, pages & folders
Orbit shows a site’s content as sections in the sidebar — posts, team, pages — each a folder of Markdown (or MDX) pages. One file is one page: its frontmatter is a form, and its body is a Markdown editor.
Where the sections come from depends on how the site is built:
- Astro — each content collection is a section, with the fields its schema describes. There’s nothing to set up.
- Any other generator (Gatsby, Next.js, …) — the
content map in
orbit.config.yamllists the sections: where their pages are, which template renders them and, if you like, their fields.
Either way, the developer decides what editors can do in each section:
- Edit only, or add pages too. A section that holds one fixed page (a home page) can’t take more. On a content-map site, adding pages also needs the section’s template.
- Folders — where new pages may go, and whether editors may start new ones. See the pages below.
- Read-only and no body — set per section in Collection rules.
Data that isn’t a page — navigation, footers, team lists — is edited as a data file instead.