Customization
How-toTailoring the starter to your needs.
Branding
Section titled “Branding”Update the site-wide identity in src/config/site.config.ts (name, description,
url, author, social links, OG image). This is the single source of truth for
canonical/OG/sitemap and llms.txt.
Adding Pages
Section titled “Adding Pages”- Create a Markdown file in
src/content/pages/:
---title: My Pageslug: my-pagelocale: endescription: A new page.---## Content here- Create the route
src/pages/my-page.astro— copysrc/pages/privacy.astro(it loads the entry byslug+localeand renders it), or compose sections fromsrc/components/sectionsfor a marketing page. - Add it to the navigation in
src/config/nav.config.tsand add the label key tosrc/i18n/en.json. - Register the page in
src/registry.json(pnpm validate:registrychecks it). - With more than one locale, also add
src/pages/[locale]/my-page.astro.
Updating the Hero
Section titled “Updating the Hero”The homepage uses the Hero section (src/components/sections/Hero.astro).
Its copy comes from the hero.* keys in src/i18n/en.json; variants and sizes
are defined in src/components/sections/hero.variants.ts.
Design tokens
Section titled “Design tokens”Colors, spacing and typography are CSS custom properties in
src/styles/tokens/. Change the brand there (or via branding in
site.config.ts) — components only use semantic tokens such as
var(--primary) or bg-primary, and pnpm check:kpis rejects hardcoded colors.
Interactivity
Section titled “Interactivity”There is no UI-framework runtime. Add behavior with a <script> in the component
(Astro bundles and hashes it for the CSP) or a small custom element — see
src/components/landing/FeatureTabs.astro for an accessible example.
Third-party scripts and embeds
Section titled “Third-party scripts and embeds”The Content Security Policy only allows origins listed in
src/config/csp.config.ts. Add a new analytics provider, font CDN or iframe
source there; pnpm test:e2e fails if a page triggers a CSP violation.
Was this helpful?