Blog
Explore our latest articles, tutorials, and insights.
A web app needs a CMS for everything around the product — marketing, blog, docs — not the product itself.
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 SaaS marketing site needs marketing autonomy, a content API, and SEO — without dragging in app code.
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.
A release-notes page needs dated entries, publish autonomy, and an API.
Pick a team CMS by its permission model and publish path, not its feature checklist.
A content hub needs taxonomy, search, scheduling, and multi-channel delivery from its CMS.
A B2B website is a long content operation that needs the right CMS infrastructure.
A developer blog needs a CMS that respects code, offers an API, and lets you own your domain.