Cascadia is a mostly-unopinionated starter kit, with just enough CSS and JS to get you going with the essentials.

Components
Cascadia comes with a bunch of Page Builder components with some sensible presets that you can customize to your liking. These include:
- Accordion
- Blog Teaser
- Logo Cloud
- CTA Bumper
- 50/50 Group
- Stats
- Testimonals / Ratings
- Large Media
- Google Map
- Hero
- Image Carousel
- Intro
- Tabs Explorer
- Job Listings
Google Maps
To use the Google Maps component, be sure to add your API key as GOOGLE_MAP_API_KEY in your .env file.
Sets
In addition, it has a few Sets built in that you can insert into any Bard field:
- Blockquote
- Image Carousel
- Tabbed Content
Cascadia leverages Alpine.js and TailwindCSS, such that you can configure the views to your liking. For the carousel, it includes Splide
AI-Assisted Development
Every component follows a strict, checkable convention — a name chain of matching fieldset, builder registration, view partial, and catalog entry — so that both developers and AI coding agents can work with the component system predictably. See export/docs/COMPONENT-SYSTEM.md for the full explanation (installed at docs/COMPONENT-SYSTEM.md in a site built from this kit).
- The component catalog (
content/collections/components, tagged via thecomponent_tagstaxonomy) documents what each component is for, when to use it over a sibling, and what content it needs — editable in the control panel, and readable by an AI assistant deciding which components fit a content brief. php artisan components:auditchecks the whole system against the conventions (name chain, builder purity, theme consistency) and exits non-zero on failure, so it can run in CI.php artisan components:sync [--prune]stubs missing catalog entries and reports (or prunes) orphaned ones.php artisan components:make <handle> --group=<group> --icon=<icon>scaffolds a new component's fieldset, builder registration, partial, and catalog entry in one step.- All three are also reachable from System → Components in the control panel, and from the command palette (⌘K → "Cascadia").
- Optionally, adding Laravel Boost + statamic-boost (
composer require chrisvasey/statamic-boost— not installed by default; check its compatibility with your Statamic version first) gives AI coding agents (Claude Code, Cursor, etc.) MCP tools for querying the component catalog and running the conventions audit, plus guidelines that teach them the conventions automatically.config/boost.phpand.ai/guidelines/statamic.blade.phpare already set up for when you do.
Adding Scout
This kit has no dependency on Scout (Cascadia's editor-facing content assistant) and doesn't require or configure it — they're built to compose, not to need each other. If you do add it, point it at this kit's own conventions by publishing its config (php artisan vendor:publish --tag=scout-config) and setting:
'page_builder_field' => 'page_blocks','catalog_collection' => 'components',
Scout's own System → Scout page shows whether these are set, so it's easy to check without digging through config files.
Navigation
Cascadia comes with 2 separate Navs out of the box, with the secondary nav being placed either in a smaller menu above the main nav, or in an off-canvas drawer, which can be configured in the Globals -> Site Config.
Theming
Each page-builder component has a Theme Selector field, starting with the default (light), Accent, Muted, and Dark themes, for easy theming of components. Add more themes to the field, and set up the CSS in the theme.css file.
The theme system uses CSS variables to set up Tailwind classes like bg-surface which will change values, depending on the theme selected. Override these values to your liking in the CSS.
Classes for theming include:
- bg-surface
- text-body
- button (and variants)
- eyebrow
Explore the theme.css to see all the available theme classes, and add your own.
Update your .env file to see the theme images:
STATAMIC_CUSTOM_CMS_NAME="Cascadia Starter Kit"STATAMIC_CUSTOM_LOGO_URL='/cascadia-kit.png'STATAMIC_CUSTOM_DARK_LOGO_URL='/cascadia-logo.png'
SEO
Basic SEO fields are incorporated into the Page, Team, and Blog collections, with fallbacks configured in the Globals: Site Config section.
Analytics
Optionally choose between Fathom or GA with a toggle, and add your tracking ID to your .env file. The button component, used for CTA buttons throughout, will fire an event that can be used for sending data to your analytics platform of choice. Enable events by setting
enableEventTracking: true,
in the js/apline/app.js file.
To modify the available data, look at the button component, and explore the app.js file for the handleAnalyticsEvent method, and follow the code from there.
Accessibility
This starter kit has baked-in accessibility features, including full keyboard operation for the accordion and Tab Explorer components, focus trap for the off-canvas menu.
Colour-contrast ratios for text over backrounds meet WCAG 2.1 AA standards. Keep this in mind when making updates to suit your own designs!