---
name: orbitable
description: Set a website up for Orbit MD ("make my site Orbitable", "configure my site for Orbit") — write orbit.config.yaml (and a content map for Gatsby, Next.js, Nuxt and other non-Astro sites) and move editable words out of code into content files, without changing the design.
---

# Make a site Orbitable

Fetch and follow the full guide: https://orbitmarkdown.com/ai/orbitable.md

In short:

1. Find the site folder and its generator (`astro`, `gatsby`, `next`, `nuxt` in
   `package.json`; `hugo.toml`; `_config.yml`).
2. List pages/posts (Markdown/MDX folders and what renders them), data files
   (JSON/YAML), and words written in code.
3. Astro: Orbit reads `content.config.ts` — keep schemas in that file; add
   `orbit.config.yaml` only for rules. Anything else: add a `sections:` content map —
   `files` (a glob), `template` (the file that renders them — required for editors to
   add pages), optional `newPage` and `fields`.
4. List editable JSON/YAML under `data:`; move data written as code into JSON.
5. Move obvious words out of code (home heading/intro, site details) into content
   files the pages read — same components, same markup.
6. Validate against https://orbitmarkdown.com/schema/orbit.config.json, keep the
   build passing, and summarise what editors can change and what stays in code.

Never change the design, never delete content, and ask before large changes.