Skip to content

Writing

Frontend

8 pieces tagged Frontend. Everything else is one click away in the rail beside it.

31 documents · press / to search

  1. 4 min read

    A dead animation looks exactly like one that has not started

    CSS scroll-driven animations fail silently in four different ways, and every one of them renders a page that looks fine. Here is how we made them fail loudly instead.

    CSSTestingFrontend

  2. 4 min read

    Four CSS traps, and the one property family behind all of them

    A mask that cancelled a 3D transform, a perspective on the wrong element, a header that ate its own menu, and a timeline measured against the wrong box. All four looked right in the state anyone would check first.

    CSSFrontendDebugging

  3. 9 min read

    Architecting large-scale Next.js applications: Server Components, caching and state

    How to structure a Next.js App Router codebase that stays fast as it grows — where the client boundary belongs, what Server Components actually cost, which caching layer answers which question, and the state patterns that survive a hundred routes.

    Next.jsReactArchitectureFrontend

  4. 7 min read

    The cost of JavaScript: what a 100/100 Lighthouse score actually requires

    A framework floor you cannot budget below, four techniques that move the number, and the measurement discipline that keeps it there. Written from a site that scores 100/100/100/100 with zero route-level JavaScript.

    PerformanceCore Web VitalsFrontendNext.js

  5. 6 min read

    Bridging Figma and code: a design system built on tokens and Tailwind

    Three token layers, one configuration knob for a whole colour ramp, and contrast ratios computed by a test rather than typed into a comment — how to build a design system where the code and the design file cannot drift apart.

    Design systemsTailwindFrontendAccessibility

  6. 7 min read

    Web accessibility as a competitive advantage: an engineering checklist

    The accessibility defects an automated suite finds, the ones it structurally cannot, and eleven real failures from one build — what caused each, and the check that now prevents it.

    AccessibilityWCAGFrontendTesting

Start here

Tell us what you are building

Or what is breaking, or what has to go faster. You will get a straight answer from an engineer who would do the work.

Start a project