Topics
The slow half of the job: naming things well, writing markup that survives the next redesign, choosing the boring solution on purpose. Notes on how a page is actually built, not on how it gets demoed.
2 posts
A schema that fails the build is worth more than a CMS that lets anyone publish a broken page. What we validate in Astro, what we deliberately leave alone, and the three rules that keep a Zod schema from slowly turning into a second CMS.
We rebuilt a site we first shipped in 2016, and the markup that survived was never the clever markup. What holds up: elements chosen for meaning, state left where the browser can see it, and a hard limit on what a class name is allowed to know.