Decisions, releases, finished sites
Only about what is already in the repository. The product forbids invented figures on the pages it builds. A blog that broke that rule would cost more than it returns.
Sites built
with this skill
Not single blocks but complete sites: both themes, both languages, inner pages, social cards. Each with a write-up of which sections it is made of and why those.

Biocoda: a site for a contract laboratory

Greenhouse: a site for a venture fund

Ledgera: a site for payment infrastructure

Neurocast: a site for a medtech startup

Polba: a site for a D2C grain brand

Svet: a site for a branding studio
What is new
in every version
What a release changed, and what has to be carried into sites already built. Grouped by what the reader can now do, not by which files were touched.
What decides
if a site is found
Rendering, search, accessibility, markup for machines. The general things that decide whether a site is found — and how the template settles them so nobody has to settle them again.

Accessibility: what it actually checks

robots.txt, sitemaps and markup: how a site talks to machines

SEO for a marketing site: what works and what is myth

SSR and SPA: why a marketing site renders on the server

The section catalogue came off this site




