Project
Portfolio CMS
A lightweight modular monolith for an SRE/DevOps portfolio, with SSR public pages, a static Svelte admin, PostgreSQL, and a separate Nginx edge.
Problem
The former portfolio had overlapping controls, expensive client rendering, and more operational surface than a single-owner site needed.
Role
Architecture, backend, responsive UI, database normalization, delivery, and production-safe migration planning.
Outcomes
A smaller three-container runtime, true SSR and 404 behavior, responsive grayscale UI, and reproducible CI/CD.