A portfolio can be more than a static page. I wanted mine to behave like a small product: content stored separately, projects managed from data, and a structure that can evolve without rebuilding everything from scratch. The goal is simple: keep the public experience minimal while making the system behind it flexible. Supabase stores the content, Next.js renders the interface, and the portfolio can grow one project or note at a time.
Building a Portfolio That Can Become a Product
Why this portfolio is moving from static export to a database-backed product surface.
