Why I Built My Portfolio with a Full Backend (Not Just Static HTML)

The Conventional Wisdom

Every portfolio guide says the same thing: 'Use a static site generator. Keep it simple. Content in markdown files.'

I disagree.

Why a Backend?

1. Dynamic Content Management

I can add projects, publish blog posts, and update content without redeploying. The admin API lets me manage everything from a REST client.

2. AI-Integrated Blog

I built an AI blog draft generator that uses Anthropic's Claude API. I feed it my notes and project context, and it generates a structured first draft that I then edit and publish.

3. Analytics Without Third Parties

I track blog post views in my own database. No Google Analytics, no cookies, no privacy concerns. Just a simple view counter that tells me what content resonates.

4. Search and Filtering

Full-text search across projects and posts. Category filtering. Tag-based discovery. Try doing that with a static site.

5. It Showcases My Skills

A static portfolio shows I can write HTML. A full-stack portfolio shows I can build, deploy, and maintain a production system — which is exactly what I want employers to see.

The Technical Stack

The Trade-offs

But these trade-offs are exactly the kind of production concerns I want to demonstrate I can handle.

Key Takeaway

Your portfolio IS a project. Make it demonstrate the same skills you want to be hired for.