The portfolio problem
A lot of portfolios become stale because every update requires editing the UI directly. That slows down publishing and makes it harder to keep writing.
A better model
Use markdown files as the source of truth. When content is the data model, the website can generate routes, metadata, and feeds automatically.
What this unlocks
- Faster publishing
- Cleaner separation between design and content
- Better SEO output
- Less risk of breaking layouts when writing
My workflow
I like building a reusable route system that reads files from a content folder and turns them into polished pages with almost no manual overhead.
Takeaway
For student portfolios, content-first wins because it gives you momentum. You can keep shipping articles and projects without rebuilding the whole site.
