Notes from shipping code
Deep-dives on the problems I've debugged, the patterns I've extracted, and the decisions I'd make differently next time.

Aligning Five Form Components Around aria-describedby
Five form components, five approaches to displaying errors. One aria-describedby pattern turns inconsistency into a shared accessibility contract.

Standardizing a Component Size Scale
A design system with five avatar sizes, no badge size, and three spinner sizes is a design system arguing with itself.
A Favicon Pipeline from One SVG
A 64-line bash script turns one SVG into 11 SEO-ready images: favicon.ico, apple-touch-icon, android-chrome, and mstile via rsvg-convert.

Mobile Nav Accessibility: The Bottom Sheet Dialog Pattern
A nav redesign passes code review but fails E2E tests on mobile. Here's what axe caught and how aria-hidden, inert, and proper dialog semantics fixed it.

Fixing Hydration Mismatches Without Suppressing Them
A three-line useSyncExternalStore hook helps server and client renders agree, no more suppressHydrationWarning.

Graceful Degradation for Third-Party Embeds
Adding a timeout-based fallback when a Calendly iframe gets blocked by ad blockers or network issues.

Z-Index Choreography for a Mobile Bottom Nav
The z-index choreography behind adding a fixed bottom bar without breaking scroll-to-top, table-of-contents, and bottom sheet overlays.

Why import type Isn't Optional: A Circular Dependency Crash
How a subtle difference between import and import type causes a circular dependency crash in a Turbopack-bundled Next.js app.

Making Data Tables Keyboard-Navigable
Adding scope, caption, clickable row keyboard support, and focus-visible to a Table component. The accessibility basics HTML tables need but rarely get.

Pause-on-Hover: Making Toast Notifications Respect the User
Adding aria-live regions and pause-on-hover to a Toast system. Screen readers and sighted users have conflicting timing needs.

Building an Accessible Dropdown Without a Library
Full ARIA menu semantics and keyboard navigation in ~150 lines of React, no Radix, no Headless UI, just the spec.

Documenting Design Tokens for Developer Experience
Documenting 100+ theme tokens for a Tailwind CSS 4 component library so developers pick semantic names instead of guessing gray values.