Skip to content
Sign inJoin waitlist

Kalme documentation — Astro

Everything you need to go from the downloaded folder to a published site. Read in this order, or jump to what you need.

Guide What it covers
Install and run Requirements, install, the commands, what is in each folder
Editing the content Editing text, images, videos, services and prices, projects, posts and legal texts — no CMS needed
Making it look like your brand Colours, fonts, spacing, components, the style guide, motion
Pages and sections Adding, removing and reordering pages and sections, with a map of every page
Forms Making the Contact form deliver to you — static or server mode
Using a headless CMS Connecting Sanity, Payload, Strapi, Directus or any other headless CMS
Going live Pre-launch checklist, deploying to any static host, domains, what to do after launch
Troubleshooting and questions Errors, questions and answers

In a hurry: the first 15 minutes

Section titled “In a hurry: the first 15 minutes”
Terminal window
npm install
npm run dev
  1. Open http://localhost:4321.
  2. Put your name, description and domain in src/content/site.json, and your contact details in the same file.
  3. Replace the images in src/assets/images/ (keep the file names and you are done) and the three videos (Editing the content).
  4. Replace the browser icons in public/ (icon.svg, apple-icon.png) and the share image (public/opengraph-image.png).
  5. Edit the page copy in src/content/pages/ and your services, projects, posts, team and legal texts in src/content/collections/.
  6. Point the Contact form at your inbox — Forms.
  7. Deploy — Going live.

Nothing else is required: the site has no database, no account to create and no paid service to run.

How this template is put together

Section titled “How this template is put together”
  • Content is data. All text and every collection item live in src/content/ as JSON. Collections are defined in src/content.config.ts and checked against src/content/schemas.ts; pages read them through src/lib/content.ts. This is why swapping in a CMS later touches one file, not the whole site.
  • Design is tokens. Colours and breakpoints are in src/design-system/theme.css; text styles in src/design-system/tokens/. Change a token and every page follows.
  • Components are shared. Every button, card, form field and section is in src/design-system/ and shown at /style-guide on your own site.
  • No framework in the browser. Pages are plain HTML; the few interactive parts (menu, accordion, pricing switch, videos, form, hovers) are small scripts that load with them.

Getting help

Section titled “Getting help”