Building Without a CMS
For a portfolio, a content management system is often a liability pretending to be a feature.
Every portfolio project eventually hits the same fork in the road: do we put this on a CMS? For most creatives, the honest answer is no — and saying no buys you speed, security and longevity you did not know you were trading away.
What a CMS actually costs
A content management system promises convenience and delivers a standing liability: a database to back up, a server to keep patched, plugins that break on update, and a monthly bill for content that changes twice a year.
For a portfolio — a dozen case studies, a handful of articles — that is a lot of machinery to maintain a small amount of text.
The local-content alternative
Astro’s content collections let you keep everything in version-controlled Markdown and typed data files. The benefits compound:
- Speed. Pages are built to static HTML. There is no database query between the visitor and the content.
- Safety. No server-side admin means no admin to attack.
- Longevity. Plain text outlives every platform. Your case studies will open in ten years.
- Confidence. A typed schema catches a missing field at build time, not in production.
”But I’m not a developer”
This is the real objection, and it is fair. The answer is that editing a Markdown file with clearly labeled fields is closer to filling in a form than writing code. Arrowline ships with example case studies you copy, rename and edit. Going live is three files, not a tutorial.
A CMS is the right tool when many non-technical people edit content daily. A portfolio is almost never that. Match the tool to the problem and the simpler path usually wins.