Re:Headless CMS Is Killing the Buy vs. Build Decision
by anotheryou on Saturday July 20, 2019 @06:46AM
(#20485069)
No?
Headless = DB/content is separated by an API from the display/front-end/output and possibly a data entry-UI
The benefit: you can swap front-end and data entry UI to your liking and have no lock-in.
Added bonus: separating by an API forces cleaner code and more documentation
Comparing it to wordpress (ignoring how it can possibly be used headless nowadays too): If wordpress doesn't do the trick for you anymore you have to migrate all your data, rebuild the front-end, teach staff a new UI for data entry and all that possibly just for something like a bit more performance.
Headless = DB/content is separated by an API from the display/front-end/output and possibly a data entry-UI
The benefit: you can swap front-end and data entry UI to your liking and have no lock-in.
Added bonus: separating by an API forces cleaner code and more documentation
Comparing it to wordpress (ignoring how it can possibly be used headless nowadays too): If wordpress doesn't do the trick for you anymore you have to migrate all your data, rebuild the front-end, teach staff a new UI for data entry and all that possibly just for something like a bit more performance.