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.
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.
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.