Personal brand platform with blog and project content
Portfolio & Publishing System
A Next.js portfolio/blog system that combines public pages, Supabase-backed content, rich text editing, and Cloudflare deployment.
- Next.js
- React
- TypeScript
- Supabase
- TipTap
- Cloudflare Pages
Problem
A serious portfolio needs more than static pages; it needs a maintainable publishing workflow and a stronger proof system.
Goal
Turn the site into a product-like platform for case studies, technical notes, and professional positioning.
My role
Full-stack owner across frontend, content model, editor workflow, Supabase integration, and deployment.
What this proves
Full-stack product ownership, publishing workflows, Supabase integration, and Cloudflare deployment.
Architecture
- Next.js App Router public site
- Supabase content and images
- TipTap editor for dashboard content
- Edge-aware deployment with next-on-pages
Features
- Blog and article routes
- Rich text editing workflow
- Project listing and case-study direction
- Cloudflare Pages deployment path
Technical decisions
Challenge
Balancing static brand content with dynamic content fetching
Decision
Separated curated portfolio data from dynamic publishing data
Challenge
Keeping Edge compatibility in mind
Decision
Kept public brand pages server-rendered where possible
Challenge
Avoiding a homepage that becomes only a blog feed
Decision
Used reusable sections so the site can evolve without page rewrites
Results and learning
Shows ownership of a real Next.js/App Router system with content workflows, Edge deployment constraints, and public-brand UX.
A portfolio works better when it is treated like a product system, not a decoration layer around links.