Initial public release
Rigel CMS 1.0.0 is the initial public release, available on npm. It adds a content editor at /rigel/ while your Astro site keeps its own templates, content files and deployment pipeline.
Included
- Visual editing on prepared HTML, with explicit field bindings and in-memory draft previews. Editor templates are separate from draft and live website links; cross-origin previews use sanitized HTML snapshots.
- Developer-declared content models for JSON pages, reusable shared records, references, section objects and keyed arrays. Existing
defineCopycontent remains supported. - JSON article collections with Lexical block bodies, Inline preview by default, an optional Sidebar experience and a read-only Markdown view.
- A media library with configurable upload limits, UUID filenames, editable metadata, image and video previews, PDF and text previews, and confirmed local file deletion.
- GitHub sign-in and publishing with repository access checks, saves to a shared drafts branch and reviewed batch publishing through a pull request and squash merge. Use the provided GitHub connection or host your own compatible service.
- Local filesystem editing through Astro’s development server, explicit Save and unsaved-change warnings.
- Content and SEO fields, configurable content navigation and JSON menu editing.
Get started
Create a site from the Astro starter:
pnpm create astro@latest my-site --template rigel-cms/rigel-starter
cd my-site
pnpm install
pnpm dev
Or add Rigel to an existing site:
pnpm add @rigel-cms/rigel@1.0.0 svelte@^5.57.0
pnpm add -D vite@^8.0.0
Requirements and limits
Use Node.js 24, Astro ^7.3.0, Svelte ^5.57.0 and Vite ^8.0.0. Local filesystem writes require the Astro development server; deployed static sites use the GitHub backend. GitHub media writes are not implemented. The default maximum upload size is 2 MB, configurable in bytes.
Previews need host-built HTML and explicit field bindings; they do not execute website scripts or rerun Astro. Collection canvases work before the first Save; new schema page documents require their first Save. Your site must provide its own routes, draft filtering and SEO output.
Save writes content, while Publish reviews and merges the shared branch’s pending changes as a batch. Your hosting pipeline still builds and deploys the website.
Package source: 7416acb.