My current portfolio, built with Next.js, source-controlled project content, bilingual case studies, structured metadata, and a constrained AI assistant.
My old portfolio could show projects, but it did not tell enough of the story behind them. The content also needed one reviewable, source-controlled model instead of being scattered across components.
How I fixed it
I rebuilt it in Next.js with MDX project files, typed experience data, project detail pages, bilingual copy, SEO metadata, structured data, and a Groq-powered assistant grounded in the same portfolio sources.
What it can do
Source-controlled MDX project data
Bilingual portfolio copy
Project case-study pages
Structured data and generated social images
Dynamic CV download
Groq portfolio assistant
The stack that shipped it
Next.js fits the SEO and dynamic route needs, MDX keeps project claims reviewable in Git, and the AI assistant uses the same constrained sources so answers stay within portfolio context.
What changed
The portfolio now works more like a small content product: projects can grow into case studies and recruiters can ask the assistant about my work.
What I learned
I learned that a portfolio is not only visual polish. Data quality, story structure, and update workflow decide whether it keeps working after launch.