Re:Headless CMS Is Killing the Buy vs. Build Decision
by _bxg1 on Friday July 19, 2019 @01:37PM
(#20480771)
> a content management system served through an API
That phrase doesn't make any sense.
> legacy render-based CMS like Wordpress / Joomla where the database is completely tied to framework will decrease
That's exactly what I said.
> It’s also important to note that your CMS isn’t bound to any render-full GUI like WordPress but instead can be managed from anywhere as long as you have the APIs for it.
I think you may be getting the front-end GUI and back-end GUI mixed up. A headless CMS omits the front-end GUI, but includes a back-end (content management) GUI. It admittedly also includes a light CRUD API over the database, so it's slightly more than I initially said, but not much.
That phrase doesn't make any sense.
> legacy render-based CMS like Wordpress / Joomla where the database is completely tied to framework will decrease
That's exactly what I said.
> It’s also important to note that your CMS isn’t bound to any render-full GUI like WordPress but instead can be managed from anywhere as long as you have the APIs for it.
I think you may be getting the front-end GUI and back-end GUI mixed up. A headless CMS omits the front-end GUI, but includes a back-end (content management) GUI. It admittedly also includes a light CRUD API over the database, so it's slightly more than I initially said, but not much.
Here's a more in-depth explanation. Maybe this will clear things up for you: https://css-tricks.com/what-is-a-headless-cms/