Most portfolios don't need a CMS. They need clarity, a handful of case studies, and a contact form that works.
I used to wire every personal site to a headless CMS. Then I'd spend a weekend fighting content models for five projects and three testimonials. The content barely changed twice a year.
What changed
Folio keeps everything in TypeScript (and Markdown for this blog). You edit a file, commit, deploy. No dashboard login. No "sync failed" toast. No monthly CMS bill for a site that gets 200 visits a month.
When a CMS still wins
- A team of non-developers updating copy weekly
- Hundreds of posts with editors and drafts
- Localization workflows with translators
If that's not you, skip the CMS. Ship the portfolio instead.