Reflections, ideas and explorations

We had 175 brand assets scattered across 4 repositories. A branding change required 4 deploys. We solved it with a dedicated repo, S3 + CloudFront, and a single environment variable.

The PRD documented 9 breaking-change patterns. The reality was 26+. This is what I learned coordinating a major version bump across 4 repositories and 3 simultaneous packages.

We executed the full token migration of a design system with 8 categories of breaking changes, 43 consuming files, and a deliberate decision not to do the architecturally correct thing — yet.

We audited 105 Storybook stories with axe-core and found that 67.6% failed WCAG AA. The root cause wasn't the components — it was two token values.

Before writing a single line of code for our design system rebrand, we spent weeks investigating. This is how six parallel audits radically changed what we were going to build.

How I moved blog and project content from local MDX files to Strapi 5, keeping bilingual support and adding auto-rebuild on publish.

A comprehensive case study on building a dynamic theme management system that goes beyond static npm packages to support real-time theme creation and white-label applications

A detailed case study on building a robust NestJS API for theme management, covering everything from database design to security and scalability considerations

A proof-of-concept for generating framework-specific themes from unified design tokens, supporting DaisyUI, Material-UI, and Shadcn/UI

A scalable, type-safe design tokens system built with Style Dictionary and modern OKLCH color space

A reflection on how modular architecture and developer experience (DX) can elevate frontend development to a strategic level.

The architectural journey of transforming a single-brand design token system into a scalable, multi-brand platform supporting dynamic brand switching and advanced token management