Platform · Internal packages
In-house component & admin package ecosystem
The internal platform behind ~10 client sites: versioned React/Next packages for accounts, carts, checkout and forms, a config-driven admin system, and Laravel cores to match.
- Role
- Top contributor & maintainer
- Years
- 2024 — 2026
- Platforms
- npm packages · Admin panel
- My share
- ~50% of commits
The challenge
Every new client site was rebuilding the same accounts, carts, checkouts and admin CRUD screens. That cost time and multiplied bugs.
How I solved it
- 01
Repeated code extracted into versioned npm packages with example apps that mirror real client sites.
- 02
A config-driven admin: describe a resource once, get list, filters, forms and media management.
- 03
A design inspector that lets designers tune CSS variables and translations live and save them back to source.
- 04
A design-token migration plan to remove thousands of lines of per-project overrides.
What it does
- Account, cart, checkout and order page templates
- Admin UI kit with ~20 components, media manager, rich-text, slug and tree fields
- Form package with phone, select, date and upload fields
- Core API client, i18n and spacing tokens
- Laravel admin-core with OTP login, roles and a generic resource controller
Results
- Published packages
- 10
- Client sites using them
- ~10
- Of my commits
- 1,066
- Example apps
- 10
- 10 published packages reused across about ten client sites
- ~1,066 of my commits — the top contributor
Stack
- React
- TypeScript
- styled-components
- Zustand
- react-hook-form
- Laravel 13
Integrations
- CKEditor 5
- npm
Details, names and visuals are generalised to respect client confidentiality. Happy to walk through the architecture in a call.
Have a product in mind?Let's build it.
Tell me about your idea, your product or your team. I usually reply within one working day.