Customizing your site

Content — markdown files, no code

Everything editorial lives in src/content/:

• pages/ — each file becomes a page at its own URL (travel.md → /travel). Frontmatter nav: header or nav: footer adds it to the navigation.
• faq/ — one question per file; the body is the answer.
• news/ — dated posts, listed newest first at /news.
• features/ — the three-up cards on the home page.
• highlights/ — the alternating image/text splits, each with an optional CTA button.

Event data — edited on Cloomba, not in the repo

Agenda, speakers and their photos, sponsors and their logos, ticket tiers, coupons, the cover image, and the organizing team all come from your Cloomba event. Edit them in the event admin, rebuild, done — the site picks up everything, including speaker portraits replacing the initial-letter placeholders automatically.

Look — tokens in the config

Colors, fonts, and corner radius are config values, with separate light and dark palettes. Components only ever use semantic tokens, so a palette change restyles the whole site consistently — there is no per-component color to chase.

Images inside markdown pages

Drop the image next to the markdown file and reference it relatively —![The venue](./venue.jpg). The build optimizes it automatically: converted to WebP, content-hashed for caching, and emitted with its real dimensions so the page never shifts while loading. Images from public/ (![Map](/images/map.png)) and remote URLs also work, served exactly as-is — use the relative form when you can.

Images shipped with the site

• public/logo.svg — the header/footer mark; public/favicon.svg — the browser tab.
• public/placeholders/ — the hero scene and the split illustrations; replace them with your own photos or art (any format, same paths — or new paths referenced from the highlight files).

Going further

It's your repository — every section is a small component undersrc/components/sections/, and the home page is a list mapping config names to them. Add a section type by writing a component and one map entry. The repo's AGENTS.mdcarries the few layout rules that keep everything aligned (one page width, semantic tokens only) — they apply to humans and AI assistants alike.

Next: configuration · deployment