How we rebuilt the SyteWide site

The SyteWide site you’re reading was rebuilt between 2026-04-30 and 2026-05-20 using the same systems we sell to clients. The work covered design tokens, voice and positioning, governance docs, a redesigned home surface, and the case-studies system this page lives in.

The starting point was a fresh-eye design audit run in early May. The previous site had drifted: a rust accent that didn’t belong, italic display headings that fought the brand voice, per-widget typography overrides on most surfaces, and copy that read like an enterprise pitch deck. The audit retired the rust accent, killed serif display, locked Inter Variable for body, and pinned section padding to a single clamp formula.

From there the work followed a compressed pattern. The audit findings became a set of hard rules; the rules became a five-milestone sequence (M0 through M5) that closed inside four days; and the milestones became day-to-day commits, mockup-first reviews, and a governance doc trail kept current as the work shipped.

The SyteWide product line showed up in three places. SyteOps managed the engagement — task lists, design specs, commit hygiene, and the governance docs that survive after the work ships. Trustily is the path for surfacing inbound proof from this kind of rebuild, and is wired into the new home Trust Stack. Scope stayed bounded by folding adjacent work into the current PR instead of spawning new ones.

The practical takeaway for any agency or operations team running a similar rebuild: lock the tokens before you author copy, write the voice doc before you write the pages, and keep the design audit as a hard rule set you can point to when scope creeps. The systems aren’t the secret. The discipline of running them in order is.