Category
122 posts
A service business site is a lead engine — service pages, trust content, lead capture, and SEO.
A link-in-bio page is one simple page — the only question is whether you rent it or own it.
A status page must stay up when your app is down, which means separate infrastructure.
An intranet needs organization, access control, search, and data ownership from its CMS.
HTMX bets on server-rendered HTML, and a server-rendered CMS matches that bet better than a headless one.
A brand site needs full design control and marketing autonomy — a template-based, self-hosted CMS gives you both.
A help center needs taxonomy, search, and support-team publishing from its CMS.
Technical writers need clean content handling, publish autonomy, and an API from their CMS.
An internal wiki needs organization, search, and access control — and self-hosting to keep knowledge yours.
Pick a team CMS by its permission model and publish path, not its feature checklist.
A personal website should be simple to run and impossible to lose.
A photography CMS lives or dies on its image pipeline and your control over presentation.