Portfolio Platform
This portfolio started turning into a product the moment I wanted to edit and publish it without turning the database into a bucket of arbitrary HTML and JavaScript.
A multi-tenant portfolio publishing platform in development, with a Next.js Studio and an authoritative ASP.NET Core backend.
The product idea
A portfolio should be editable without rebuilding the site, but ‘editable’ should not mean storing random HTML, CSS and JavaScript in a database. I’m building a structured publishing model instead.
The architecture
The public site and Studio live in Next.js. Business rules, authorization and publishing authority live in ASP.NET Core .NET 10. PostgreSQL is the system of record, and Cloudflare R2 is the media direction. The architecture is a pragmatic modular monolith, not a microservice diagram for its own sake.
Draft, preview, publish
The Studio is designed around structured content and branding: pages, sections, projects, themes, navigation, SEO and opening configuration. Changes move through draft → preview → publish instead of mutating the live site directly.
Tenant security matters early
Workspace/site isolation and RBAC are backend responsibilities. The system does not assume database policies magically protect ordinary API traffic. Cross-tenant behavior is something to test, not something to hope for.
Current state
The platform is still in development. The public portfolio design is being used as a real first tenant while the .NET, Studio, publishing and integration slices continue underneath it. I would rather label that honestly than present a roadmap as a shipped SaaS.
Back to all work
Work index ↗