Evidence
System surface
No public screenshot on file—generative preview stands in for the visual layer.
Story arc
How this shipped
Where I learned to build at scale and lead teamsThree beats: what pressed against the work, how the stack answered, and what changed once it was live.
I · Constraint
The brief
Maintain and extend a 10-site Craft CMS portfolio for paying clients while keeping local Herd environments, Composer plugin upgrades, and project-config syncs reliable across handoffs.
II · Build
The craft
Standardized Twig template architecture and content-modeling patterns. Adopted Craft project-config CLI workflow over hand-edited YAML. Used Herd for parity with shared local dev. Tracked QA via the in-house rocket-vitals scanning tool.
III · Proof
What moved after launch
Client sites remain live and maintainable. Project-config workflow makes content-model changes traceable in version control. Standard patterns reduce per-site ramp-up.
Signals
Signals & scale
Inventory