41–50 of 50 posts
What a poor quality article, it doesn't have any explanation what a headless CMS is.
I would imagine the writer presupposes the reader already knows what a CMS is, and is trying to sell the reader on adopting it.
Cutting through the deluge of marketing-speak: A Headless CMS is a GUI that simply lets nontechnical people manage content in a database (as opposed to traditional WordPress, which included front-end templating logic). These aren't super new but they are good. They're extra good in a world where you're increasingly likely to have multiple front-ends for a single application.
> A Headless CMS is a GUI that simply lets nontechnical people manage content in a database. This is exactly what a headless CMS is not . A headless CMS is a content management system served through an API. Thus, legacy render-based CMS like Wordpress / Joomla where the database is completely tied to framework will decrease because of how heavy, poorly flexible and competitive they are from every point of view. It’s…
Cutting through the deluge of marketing-speak: A Headless CMS is a GUI that simply lets nontechnical people manage content in a database (as opposed to traditional WordPress, which included front-end templating logic). These aren't super new but they are good. They're extra good in a world where you're increasingly likely to have multiple front-ends for a single application.
Making your content work on a watch, and on nonexistent AR glasses, probably isn't a major priority yet.
SSG FTW! - Cross platform - Best performance - Ultimate security - no database or server code - Use awesome development tools for funky stuff - Easy to migrate to another thing - Easy to experiment with in development settings - Have small services for dynamic stuff that can be sepparatelly developed (comments, profiles etc.) Its good to see era of Joomla and friends is coming to an end.
What I generally need is a CMS that requires minimal maintenance over the time frame of a decade or more. Static html generation, doesn't have 50 bazillion dependencies, written in a language that isn't moving fast. Actually, what I really need is a stable, portable file format , since editors will continually bloat up and die in the natural life cycle of software projects.
Some background: I spent 6 years building customer Django sites; for the last 3.5 years I've been doing IoT. For many organizations, a headless CMS are going to be more and more of a requirement, as more content is delivered to non-web or and non-mobile contexts. Some examples: 1. Shipping content into voice or chat bots. 2. Shipping content to embedded devices like touch screens on home appliances or factory machine…
Haha. Wow. I didn't know it was already time for another anti-relational hype cycle.
"headless" I don't know what field they are operating in, but in the world of financial publishing, thats called multiplatform. Now, the thing that they gloss over, and the actual hard part of all of this, is not the headless bit, its getting your content in order. Organising your content so you can syndicate it to people that want it is really, really hard at scale. Its almost never a technical challenge, it a quest…
"Headless" is a pretty old term in IT, basically for anything that operates without a dedicated monitor or view as part of the primary access. For instance, Chrome not too long ago released the capability to run headless. Headless servers are hardware servers without a physical monitor, keyboard or mouse (i.e. you typically interact with it via ssh or RDP). Microsoft has also used the term for windows servers and emb…
However as you've highlighted, its not whats going on here.
I will accept:
o Content-as-a-service
o multi-play publishing
o API driven syndication
o multiplatform publishing
but "headless"? Its a half arsed term to supposedly differentiate them in a crowded marketplace.
Some background: I spent 6 years building customer Django sites; for the last 3.5 years I've been doing IoT. For many organizations, a headless CMS are going to be more and more of a requirement, as more content is delivered to non-web or and non-mobile contexts. Some examples: 1. Shipping content into voice or chat bots. 2. Shipping content to embedded devices like touch screens on home appliances or factory machine…
>A lot of people haven't yet felt the pain of using traditional relational data for these nontraditional channels. Haha. Wow. I didn't know it was already time for another anti-relational hype cycle.
It's similar to how data warehouses aren't going away, but a lot of companies aren't trying to shoehorn _all_ their data star schemas.
So if "relational databases aren't for everything" is hype, sign me up?
Cutting through the deluge of marketing-speak: A Headless CMS is a GUI that simply lets nontechnical people manage content in a database (as opposed to traditional WordPress, which included front-end templating logic). These aren't super new but they are good. They're extra good in a world where you're increasingly likely to have multiple front-ends for a single application.
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.