S/05

Site build

Fast, accessible front-end templates your marketing lead can edit without filing a ticket with engineering.

TemplatesContent modelAccess

Getting edits out of the backlog

The most common problem with a marketing site is not how it looks. It is that changing a sentence requires an engineer. Six months of that and the site stops saying anything current, because nobody wants to spend a pull request on a headline.

The fix is a content model: a small set of blocks the marketing team assembles pages from, with the content itself in files anyone can edit.

Performance is a design decision

Fast sites are mostly the result of choices made early — how many fonts, how many scripts, whether images are sized before they ship. Those get decided at the start rather than fixed in a sprint afterwards.

What you get

Designed and built templates, a documented content model, the components in your repository, and a walkthrough with whoever will be publishing.

What is included

A content model built from the blocks your team actually publishes
Static output that scores well without a performance sprint afterwards
Content in Markdown — reviewable, editable and portable
Accessibility tested with a keyboard before it ships

Two project slots open from September

Have you got something that deserves doing properly?

Tell me what is broken, who it is breaking for, and what happens if it stays that way. That is enough for me to come back with a scope and a number.