Start a Site
-
Copy a template out of the repository and make it its own git project:
Terminal window cp -r templates/restaurant my-sitecd my-sitegit initpnpm installpnpm dev -
Read the template’s
README.md. It covers what to change first: the business details, prices or listings, opening hours, forms, legal pages and the photos it expects. -
Set your identity in
src/config/site.config.ts(name, URL, contact details) and the template’s own config file insrc/config/, such asrestaurant.config.ts. -
Pick a theme.
src/styles/theme.cssimports one preset fromsrc/styles/themes/; change the import to switch. To make your own, copy a preset and change its brand hue. Fonts are an entry inastro.config.mjsand a token in the theme file. The colour and font switcher on the hosted demos only shows these presets; your site doesn’t include it. -
Add your photos with the file names the README lists. Until a photo exists, its slot shows a labelled placeholder.
-
Connect the forms before launch. Forms submit to Astro Actions and send nothing until you configure where they go. See Forms & Actions.
-
Check and deploy.
pnpm validateruns lint, type checks, tests, a build and the agent-ready check. Then deploy like any Velocity site: see Deployment.
What’s yours to change
Section titled “What’s yours to change”A template is a normal Velocity project, so the same file ownership applies: Velocity upgrades
replace Velocity’s own files and leave yours alone. The template’s pages, views, content, config, theme and its
own components are yours. The Premium Kit in src/components/premium/ is updated by pnpm kit:update, which
leaves any kit file you edit alone, so restyle the kit with tokens and skin classes rather than editing it. See
The Premium Kit.