Category
117 posts
A public knowledge base wants SEO and search; an internal wiki wants co-editing and history. Different tools. Which fits your case.
Generate the API reference from your spec; write the guides in a CMS. Why splitting the two beats one tool doing both.
A changelog is just dated, tagged entries. Here's when to buy a changelog SaaS versus run one on a CMS you already have.
Flutter talks to any content API with http or dio. Here's the honest CMS shortlist for mobile apps and how to wire it.
SolidStart consumes any content API through query and createAsync. Here's the honest CMS shortlist and how to wire it.
How a CMS handles the knowledge-base half of a help desk and what it does not — pair it with ticketing. SEO and ownership wins explained.
What a support center needs from a CMS, and why a self-hosted one beats a help-desk KB for SEO and ownership. Honest tradeoffs.
Move off the Kentico .NET DXP to a self-hosted CMS — export, map page types, rebuild the front end, and protect SEO through URL aliases.
Move off Agility CMS to a self-hosted CMS — export via Content API, flatten page modules, and protect rankings with redirects.
Move off Kontent.ai to a self-hosted CMS — export via Delivery API, flatten structured rich-text, rewrite to REST, and protect SEO.
Move off ButterCMS to a self-hosted CMS — export via REST, map, carry over SEO fields, and protect rankings. A light, REST-to-REST move.
Move off Craft CMS to a self-hosted CMS — export, map sections, carry over SEO, and protect rankings with redirects. Both PHP.