Rigel edits content stored in an Astro site's repository. Developers define the fields and templates; editors change content at /rigel/ and press Save. The site owns routing, HTML, styles and deployment.
These guides follow the SDK source in this repository. Check your installed version before using features that have not reached npm's latest release.
- Getting started: use the starter or add an editable page to an existing Astro site.
- Content model: native documents, fields, sections and shared references.
- Preview bindings: prepare real page templates for unsaved visual editing.
- Keyboard shortcuts: search, save and editor panel shortcuts.
- Content navigation: sidebar entries, categories and page tables.
- Content languages: localized types, template selection and search scope.
- Menus: JSON menu data and your site's navigation renderer.
- Media: uploads, metadata, providers and image pickers.
- Authors and references: reusable author records and article selectors.
- Content and SEO: editable metadata and the HTML your templates must render.
- Extensions: custom article controls and saved blocks.
- Browser-assisted drafts: optional native WebMCP tools for content navigation and unsaved page, article, menu and shared-content edits.
- GitHub connection and publishing: authentication, draft saves and reviewed publishing.
- Collection metadata ledgers: indexed article lists, on-demand bodies and maintenance reindexing.
- Live and draft previews: preview mappings and deployment hosts.
Content Save and website deployment are separate operations. Local Save writes files without committing them. GitHub Save writes the configured editing branch; publishing follows the configured branch workflow and hosting pipeline.