Product · 2026
iamevs
This site. A personal digital studio rather than a portfolio template with my name on it.
- Role
- Design and engineering
- Status
- building
- Year
- 2026
- Stack
- Next.js, Firebase, MDX, GSAP
iamevs
The public site and the journal are separate products that share a language. One is what I build. The other is how I think.
Problem
A personal site that only lists projects starts to feel like a brochure. I needed a place that could grow with the work.
Why
I wanted the identity, the writing, and the admin tools to live in one ecosystem without becoming a CMS company.
What was difficult
Keeping two applications related without making them identical. Sharing only what is actually shared.
Decisions
Portfolio content in Firebase. Blog posts in Git. A private studio for editing, not a dashboard of charts.
Architecture
A pnpm monorepo. Two Next.js apps. Shared tokens and primitives. Firebase for the portfolio. MDX for the journal.
What exists
A working ecosystem: iamevs.com for the work, journal.iamevs.com for the thinking.
Lessons
The architecture is the design. If the writing lives in Git, the blog stays a publication. If the portfolio lives in Firebase, it can change without a deploy.
Related
- vs-pod
A personal development environment I could actually live in — not another dashboard of widgets.