How we ship new features

Ship early

Favor the smallest mergeable change that improves the story: a section, a page, or a fix users can feel on preview.

Ship often

Short PRs beat long branches; urgency and clear scope beat waiting for perfect design.

Ship together

Hand off ownership explicitly when content, design, and engineering split work—document the cut line in the PR or RFC.

Preview deployments

Use host preview URLs (for example Vercel) so reviewers and stakeholders click the real HTML/CSS before merge.

Controlled rollout

On a static site, “flags” are often simple: hide a block, ship a branch-only page, or stage copy behind a draft PR. Dynamic product services use their own feature toggles in their repositories.

Ship checklist

Before calling it done: links and nav paths work, handbook/docs mentions updated when user-facing, Support looped in on behavior changes, and accessibility/regression spot-check on key templates.