Engineering
If you peek at the repo: modules with clear boundaries, a shared UI kit, git with review, the same release every deploy, and an admin for content.
arch
Layered modules with public APIs: domain, data, UI. A new developer finds the right file without a tour.
kit
A shared UI/theme kit and reusable components. A button changes in one place, not across twenty files.
git
Branching, code review, conventional commits. The history shows who changed each line and why.
build
Lint, typecheck, production builds, asset optimization. Releases are repeatable, not “it works on my laptop”.
qa
Specs next to code, tests where mistakes are expensive. Secrets stay out of git, deploys are written down.
cwv
Target: green zone on Google PageSpeed and Core Web Vitals, plus valid markup, accessibility, and technical SEO and GEO. That ships with the build from day one.
tg
Leads and ops alerts run through the Bot API and webhooks. Tokens live in the production env at mode 600.
cms
More than markup. The admin has structured fields — heading, image, link — so the layout can’t be broken through it.
Stack by track
Two delivery tracks
Library monorepos: bootstrap / core / data / ui layers, a shared kit, unit tests, controlled builds.
A theme with a component library, ACF-as-code (JSON in git), Webpack builds, CI deploy. Nobody edits production by hand; content goes through the admin.
