[Cyberdog]

I'm looking at the awful web site[0] for Directus, and it sure has a lot of screenshots of what appears to be a fairly traditional web-based CMS UI.

I get that what we're seeing may just be a front-end "app" connecting to the core headless CMS via its own API, but at what point has your "headless CMS with a nice UI" just become another traditional CMS?

[0]: https://getdirectus.com

[detaro]

All I see on their homepage is backend UI. A headless CMS has no client/visitor facing UI.

[lsaferite]

Headless CMS in this context means it's just the CMS backend (the tail) and not a frontend (the head). The raw content is rendered to a FE view by something else.

[thisacctforreal]

Back-end and front-end often mean server-side and client(browserside respectively, eg Front-end developer.

So to be clear, headless CMSs have an admin-facing front-end and back-end to manage content, but only an API for a process to render the content into HTML/CSS/JS for visitors.

That said, headless CMSs can be used for more than just websites.

[lsaferite]

Hence the "in this context" part