An Astro website with Rigel CMS configured for pages, blog posts, news and footer menus. Your content stays in the repository.
Use Node.js 24 and pnpm 11:
pnpm install
pnpm devOpen the local URL printed in your terminal. Visit /rigel/ to edit content. Local mode writes files when you press Save; it does not create Git commits.
astro.config.mjs: Rigel configuration and preview mappings.src/content/schema.ts: editable page and shared-content fields.src/content/: sample content to replace with your own.
Run pnpm build to build the website. GitHub editing requires a separate authentication setup.
Documentation · Rigel CMS source
The default starter uses one content language. Enable the separate English and French example before starting or building:
RIGEL_CONTENT_MULTILANG=true pnpm dev
RIGEL_CONTENT_MULTILANG=true pnpm buildVisit /en/studio/ and /fr/studio/, or /en/articles/publishing/ and /fr/articles/publishing/. The example lives in src/content/multilang/; it leaves the original pages and articles in place. Each language has its own page type, section layout and article collection. Authors, logos and media are shared. Draft pages and articles stay out of production website routes.
In the editor, Content language filters annotated page types and collections. Unannotated content remains available in both languages. Settings > Interface changes the editor interface language; it does not translate content or choose its language. Settings > Content controls whether global search covers all content languages or only the current one. The website example reuses the existing navigation and footer rather than translating that shared chrome.
Run RIGEL_CONTENT_MULTILANG=true pnpm test for production route and content checks. With the opt-in development server already running, run RIGEL_CONTENT_MULTILANG=true RIGEL_URL=http://localhost:4321/rigel/ pnpm test:browser multilang for the browser regression. Run the same browser command without RIGEL_CONTENT_MULTILANG against a default server to check that the selector and example stay disabled. Browser checks use an isolated Chrome profile and restore edited fixture bytes; run them sequentially.
Core pages remain uncategorized. Legal is a native DocumentDef.category template, not an editable category field. Visit /legal/example/; its copy is a layout specimen, not a ready-to-use legal policy.
Appearance is a per-page property, not a category or route prefix. The native Dark theme switch in page properties changes the layout's color tokens; pages without it remain light. /perspective/ is an ordinary Core page with this property enabled.
With multilingual content enabled, Legal examples are available under /en/legal/example/ and /fr/legal/example/. Each template declares its own allowed sections and creation defaults. Newly saved Legal pages use the legal route prefix; Core pages keep ordinary routes regardless of theme. Editor and website mappings are in astro.config.mjs. Restart the local development server after schema changes so its manifest and write routes use the new definitions.
The starter uses Rigel CMS 1.6.1. Pages starts with All pages; select Core or Legal to narrow the list. New pages can preview before Save using their assigned template. Inline editing starts with Properties closed; opening it shows the Page tab. Switch to Content for fields.
Editing and recovery covers keyboard shortcuts, browser draft backups and GitHub revision history. Media covers batch uploads, image processing and saved-content usage checks.
Rigel's SEO tab includes No index (noindex), off by default. Saving noindex: true makes the shared page/article layout emit <meta name="robots" content="noindex">, including localized routes. Missing or false values leave indexing unchanged. This is separate from Draft: published pages remain accessible by URL and links remain followable. Rebuild and deploy saved changes to update production metadata. Search engines need to crawl the page to read the directive; do not block it in robots.txt. This starter does not generate a sitemap; exclude flagged URLs if you add one.
Run node tests/seo-output.mjs for the production regression across page types, blog/news and localized articles. It builds temporary content fixtures and removes them in finally; run it separately from browser suites. With a local development server running, use RIGEL_URL=http://localhost:4321/rigel/ pnpm test:browser seo to check the switch, explicit Save, public metadata and reload roundtrip.
Apache-2.0. Copyright 2026 Alex Zappa (FreshJuice).