feat: create-astro-fleet CLI + Keystatic CMS example in Meridian - #8
Merged
Conversation
Scaffolds a new fleet from a giget template (default github:indivar/astro-fleet) and adds new sites to an existing fleet. Replaces the bash new-site.sh flow for cross-platform use. Uses @clack/prompts for interactive UX; supports non- interactive mode via flags (--domain, --preset, --template, --keep-demos).
Demonstrates the CMS pattern for the Astro Fleet template: - @keystatic/astro integration gated to dev (output stays 'static') - insights content collection using @astrojs/markdoc - three seed entries rendered at /insights and /insights/[slug] - nav updated to point Insights at the real page Admin UI available at http://localhost:4321/keystatic in dev. Production editing requires switching to server output + adapter; see docs/adding-a-cms.md.
Two workflows (build.yml and ci.yml) were firing on every push and PR. build.yml did not set up Node and fell back to the runner's default (Node 20), which Astro 6 rejects (requires >=22.12). ci.yml already sets up Node 22 correctly, so every commit produced one green + one red run. Deleting build.yml leaves ci.yml as the single canonical pipeline.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
^6.1.7across all sites (was^6). Lockfile already resolved to latest; this tightens intent.create-astro-fleetCLI — new package withinit(scaffold a new fleet from the template) andadd(add a site to an existing fleet) subcommands. Interactive prompts via@clack/prompts, giget-based template fetch, non-interactive flags (--domain,--preset,--template,--keep-demos).insightscollection with Markdoc content, three seed entries, list + detail pages at/insights. Admin at/keystaticin dev; production build stays fully static (integration gated to dev).docs/adding-a-cms.md— explains the Meridian pattern, how to replicate it on another site, the monorepo access-control caveat, and when to reach for Sanity/Directus/Decap/etc instead.Why
new-site.shstays for bash users).astro-seoskill.Test plan
bun install --frozen-lockfileworks from cleanbun run build— all 4 sites build cleanly from scratch--helpand--versionrender correctlyadd <domain> <preset>scaffolds a working site (verified by building the scaffolded output)/insightslist and detail pages render in prod build/keystaticadmin loads inastro dev(HTTP 200, Keystatic React island present)bunx create-astro-fleetend-to-end against the merged branch (post-merge smoke)Follow-ups (not in this PR)
astro-seoskill (content collection Zod schema for SEO constraints, sitemap improvements, JSON-LD,llms.txt, etc.)create-astro-fleetto npm once the repo URL in the PR is merged