[Instructions]

User Instructions
& Guidelines

Instructions

A short guide to the parts of the theme you are most likely to change first.

Running it

Node 22.12 or newer. `npm install`, then `npm run dev` for a local server and `npm run build` for the static site in `dist/`. Nothing else is required — a fresh clone renders the whole demo.

Content

Everything the pages render lives in `src/content`: services, news, press releases, team, testimonials, principles and the outlet belt. Add a Markdown file and it appears — `order` in the frontmatter decides where.

Colors and type

Every color, radius and spacing step is a custom property in `src/styles/theme.css`. Change one there and it changes everywhere, including the style guide page. The type scale lives in the base layer of `src/styles/global.css`.

Corrections and additions

`src/styles/components.css` is generated from the original design and is overwritten if the converter is run again. Put your own CSS in `src/styles/additions.css`, which is never regenerated and outranks both layers.

Motion

The scroll and reveal work is declared in the markup as `data-anim` attributes and implemented once in `src/scripts/motion.ts`. To retime the whole site, or switch an effect off, edit the EFFECTS table there. Everything respects prefers-reduced-motion.

Connecting a CMS

Set CONTENT_SOURCE to contentful, sanity, strapi, wordpress or shopify plus that source’s credentials, and any collection it provides loads from there instead of the Markdown. Field names are mapped in `src/loaders/mapping.ts`.

docs/content-sources.md : /instructions/

Deploying

The build is static. `wrangler.jsonc` at the repository root tells Cloudflare so; without it the platform sets up on-demand rendering and every optimized image 404s. Delete it if you deploy elsewhere.