An agency portfolio needs custom design and easy team publishing — a template-based CMS gives both.
A community site needs strong content plus member interaction — where content-plus-comments fits versus a forum.
A marketplace is a transaction engine plus a content layer — keep content in a CMS, not the engine.
A classifieds site is a structured-content system, not a blog — the CMS has to model listings.
A brand site needs full design control and marketing autonomy — a template-based, self-hosted CMS gives you both.
HTMX bets on server-rendered HTML, and a server-rendered CMS matches that bet better than a headless one.
A PWA needs content over a clean, cacheable API — exactly what a REST headless CMS provides.
A web app needs a CMS for everything around the product — marketing, blog, docs — not the product itself.
An intranet needs organization, access control, search, and data ownership from its CMS.
A release-notes page needs dated entries, publish autonomy, and an API.
An internal wiki needs organization, search, and access control — and self-hosting to keep knowledge yours.
Technical writers need clean content handling, publish autonomy, and an API from their CMS.
