Orbit Studio Local MDX Content System

Moving Notes from component data into a maintainable local MDX content layer, with room for Projects and Garden to use the same expansion path later.

Why start with local MDX

Orbit Studio's content is still in a personal-maintenance and fast-iteration stage. Notes, Projects, and Garden all need continuous additions, but there is not yet a need for multi-user collaboration, review workflows, an editing backend, or scheduled publishing.

Local MDX fits this stage better. Content stays in Git history alongside the code, Codex can directly help reorganize article structure, and pages can keep reusing the visual language already established for Orbit Studio.

First-phase boundaries

  • Notes use content/notes/*.mdx for article bodies.
  • List pages show only published content by default.
  • Projects and Garden reserve the directory shape first, without rushing to migrate everything.
  • Custom components stay minimal for now: Callout, Figure, and Gallery.

This step does not introduce a CMS and does not change the rhythm or visual story of the homepage.

Migration order

  1. Move existing AI Development notes into MDX one by one.
  2. Add a project-retrospective template for Projects.
  3. Add a shorter knowledge-entry format for Garden.
  4. Consider RSS, tag pages, featured content, and Open Graph images later.
Orbit Studio MDX content system map
The first phase only establishes a local content skeleton so Notes can begin using MDX as the writing format.

Last updated on

AI Framework Licenses and Commercial Boundaries

A quick reference for the open-source licenses and commercial boundaries of CopilotKit, assistant-ui, and Mastra.

On this page

Why start with local MDXFirst-phase boundariesMigration order
Orbit Studio Local MDX Content System | Orbit Studio