A Shared Component Architecture for a WordPress Booking Plugin - 4 Case Studies
A solo, year-long build of a 44-component Vue library shared between two independently built apps inside a WordPress booking plugin - four linked case studies covering API boundaries, state, resilient input handling, and codebase structure.
Structuring a Large Frontend Codebase for Maintainability at Scale
Two independently-built Vue apps and a webpack-built Gutenberg block shared one component library through a consistent alias system and a per-app Tailwind purge - except in the one place plain CSS won.
Centralizing State Management Across a Multi-App Architecture
Migrating 21 Pinia stores across two independently-built Vue apps to the Composition API, and routing their data-shaping logic through one shared model layer instead of duplicating it in each store.
Designing Component APIs That Scale Across Two Applications
PreBook ships two independently-built Vue apps against one shared component library with no package boundary, so every reusable component forces the same question - what generalizes, and what stays local to the app that needs it.
WordPress Plugin Frontend Refactoring - 5 Case Studies
A self-proposed, solo-executed refactor of a WordPress Gutenberg plugin used by 60,000+ sites - five linked case studies covering the technical execution, the decision, the trade-offs, and the risk.
JavaScript Linting & Formatting Setup for a WordPress Gutenberg Plugin
Adding ESLint and a formatter to a Gutenberg block plugin codebase - the groundwork that made the CSS refactor safer, and the paired initiative behind it.
Bundle Size After a CSS Split: Measuring What Actually Changed
I expected splitting one stylesheet into 19 files to cost bundle size. The first measurement said it grew - until I isolated unrelated image assets and re-measured: a 20-30% reduction.
How I refactored 13+ dependent files with no automated tests - what I verified manually, what the risks were, and what I would do differently next time.