4 ms·
but it specifically has a GUI. It touts the features of its GUI. Like... i feel like i'm not understanding something obvious. I get the idea of an API only ser
by masukomi 3y ago
but it specifically has a GUI. It touts the features of its GUI.
Like... i feel like i'm not understanding something obvious. I get the idea of an API only server. I've written many. BUT by shipping a GUI (as part of it or separately) and then touting the features of that gui for managing the CMS they're no longer talking about a "headless" thing. They're talking about a GUI that may talk to a "headless" cms but the entire point of the GUI is to get around the "headless" part.
- jaywalk 3y ago"Headless CMS" doesn't mean it has no management GUI. It means that the output is an API instead of actual HTML pages. The "head" is HTML pages, like what you get with WordPress. "Headless" says nothing about how the CMS is managed, just what it outputs.
- j45 3y agoA bare bones api will sell faster with an example gui and management interface almost always. It’s a starting point to both see what’s possible, and also a way to maybe have some boiler plate to experiment with right away to help users start using the api by example of usage not just by a call but in a front end. I appreciate what you’re saying, got me it’s like finding an app and then wondering if it has an api. Both are useful