Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
A starter template with 40+ Astro components built for visual editing in CloudCannon, using a three-file pattern so developers code and editors manage content.
Astro Component Starter is a boilerplate template for building Astro websites with 40+ prebuilt components designed for visual editing in CloudCannon. It takes a Git repository as input and produces a fully editable Astro site where content lives in Markdown/MDX files under src/content, and every component ships as your own source code to modify or delete. The starter is distributed as an npm initializer and is licensed under MIT.
Astro Component Starter is a boilerplate template for building Astro websites with 40+ prebuilt components designed for visual editing in CloudCannon. It takes a Git repository as input and produces a fully editable Astro site where content lives in Markdown/MDX files under src/content, and every component ships as your own source code to modify or delete. The starter is distributed as an npm initializer and is licensed under MIT.
.astro file, a cloudcannon.inputs.yml file defining what editors can change, and a cloudcannon.structure-value.yml file with defaults and picker metadata.src/styles/variables/ control colors, fonts, spacing, and widths; light and dark themes live in src/styles/themes/. Changing the variables restyles the entire site.src/components/ organizes 40+ components into building-blocks (buttons, headings, forms, layout wrappers), page-sections (heroes, features, CTAs), and navigation (header, footer, mobile nav)./component-docs/ includes examples and a visual builder for every component; it is excluded from production builds by default via npm run build and can be included with npm run build:with-library.npm run deps:sync regenerates package-lock.json with cross-platform resolutions (Linux, Windows, macOS) so npm ci succeeds on GitHub Actions; npm run deps:check verifies the lockfile is CI-ready.npx create-astro-component-starter my-site-name clones the starter, adds the original repo as a git upstream so you can pull future improvements, and installs dependencies automatically.src/content/pages/index.md to change the hero heading and watch it update live in the browser..astro, inputs, and structure-value files to create a reusable, editor-friendly component system for your team.Run npx create-astro-component-starter my-site-name, then cd my-site-name and npm run dev to start the dev server at http://localhost:4321. The scaffold creates a working demo site, sets the starter repository as upstream, and installs dependencies. From there, edit content in src/content/ and components in src/components/; optionally include the component docs in production by using npm run build:with-library.
Yes. The template is open source under the MIT license, so you can use, modify, and distribute it freely, including in commercial projects.
Node.js version 24.0.0 or later is required. The project also provides deps:sync and deps:check scripts to keep the lockfile compatible across macOS, Linux, and Windows for CI.
The component docs are served by the dev server at http://localhost:4321/component-docs/ and are excluded from production builds by default. To include them in a production build, run npm run build:with-library.
Yes. CloudCannon is the visual editor that reads the YAML input files, but the components themselves are plain Astro, HTML, and CSS. You can use the starter as a standalone Astro site without connecting CloudCannon, though you'd lose the visual-editing workflow.
