All work
Shared publishing system
Website Content Platform
The publishing system behind about ten production client websites. Each client gets isolated content, custom fields and one shared administration experience.
- Role
- Lead engineer, 100+ commits
- When
- 2026 to now
- ~10
- sites served
- 100+
- commits
The problem
Every client website had its own one-off admin panel. Fixing a bug or adding a feature meant repeating the same work across every site.
What I built
- A NestJS 11 API that resolves the correct client workspace and keeps each website's content isolated.
- A Next.js admin for pages, posts, media, menus and SEO fields, shared by all clients.
- Moved production websites onto the shared publishing platform one client at a time.
Shared platform, isolated content
Clients often need custom content types. Isolated schemas allow that while keeping backup, restore and client-specific changes clean inside one shared platform.