A CMS for Astro sites. You edit the text, Git keeps the history.
Edit page copy, structured content and articles at /rigel/. Your content stays in your repository, and your Astro site controls how it looks.
- Visual editing on prepared page templates, with unsaved changes shown in the preview.
- A block editor for articles and a media library with local uploads.
- Explicit Save, with warnings before leaving unsaved changes.
- Local file editing or GitHub drafts with pull-request publishing.
Rigel edits content, not .astro components. Developers define the editable fields and add preview bindings to their templates. Saving content and publishing the website are separate steps.
Use the Astro starter, or follow the installation guide to add Rigel to an existing site. Requires Node.js 24 and Astro 7.3 or later within Astro 7.
Documentation · Content model · Previews · GitHub setup
The guides live in this repository and ship with the npm package. They describe the current source; features on main may not yet be in npm's latest release. The documentation website is also available.
Declare language-specific page types and article collections, then use an optional content-language selector in the editor. See Content languages for configuration. Website routing stays in your Astro templates.
Register your own slash commands, toolbar buttons and saved article blocks with Svelte components. The extension guide covers registration, editable blocks and published rendering.
Browsers with the experimental native WebMCP API can offer agents access to existing pages, blog/news articles, menus and shared content. Tools read and edit supported drafts, including structured fields and article bodies. Changes stay unsaved until you review them and press Save. See setup and limits.
When the editor opens, it checks the public npm latest metadata for @rigel-cms/rigel over HTTPS. npm receives the browser's IP address; the request omits credentials and the referrer and sends no user content. Sites with a Content Security Policy must allow https://registry.npmjs.org in connect-src for this check to work.
Rigel compares the stable release against the installed package version embedded when the site was built. A newer version appears as a dismissible notice on the welcome screen, with a link to the project's GitHub release notes. The check runs once per editor mount, times out after five seconds and fails quietly without blocking editing or sign-in. Successful results and failed attempts are cached in this browser for 24 hours, separately for each installed version. If browser storage is unavailable, each editor mount may check again. Dismissing a notice hides that version, not future versions; clearing Rigel's browser data clears the cache and dismissal.
Updates are manual. Ask your developer to update @rigel-cms/rigel, review the release notes, and rebuild and redeploy the site. The editor never installs packages or updates the site itself.
Apache-2.0. Copyright 2026 Alex Zappa (FreshJuice).