My old portfolio could show projects, but it did not tell enough of the story behind them. I also wanted a way to update content without editing code every time.
How I fixed it
I rebuilt it in Next.js with Firestore content, project detail pages, a dashboard, bilingual copy, SEO metadata, structured data, Cloudinary uploads, and a Groq-powered assistant.
What it can do
✓Firestore-backed project data
✓Bilingual portfolio copy
✓Project case-study pages
✓Admin CRUD dashboard
✓Cloudinary image uploads
✓Groq portfolio assistant
The stack that shipped it
Next.js fits the SEO and dynamic route needs, Firestore keeps content editable, and the AI assistant uses a constrained knowledge base so answers stay on 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.