Post · bonfire.cafe

@davidaugust@mastodon.online · 7 days ago

I know I'm late to the party on this, but when people say "headless CMS" do they kinda mean the database part of the "database publishing" of 20 years ago?

Like it is storing content separately from the HTML/CSS or app interface so one doesn't have to munge that stuff when making content, or munge content when making a site or app or something, right?

Or is there some new magic in "headless CMS" I'm missing?

#code #webdev #HeadlessCMS

Ben Ramsey

@ramsey@phpc.social · 6 days ago

@davidaugust @albinanigans “Headless CMS” means one of two things, from my understanding:

1. A CMS that generates a static website (so the website itself is separate from the thing that generates it).

2. The CMS essentially forms an API that is separate from the front-end UI, and your front-end UI calls that API to get content for display.

Albi, A Black Domain

@albinanigans@blackqueer.life · 6 days ago

@ramsey @davidaugust

Thanks! Today I learned; i boosted the initial query because I was curious too.

David August

@davidaugust@mastodon.online · 6 days ago

@ramsey @albinanigans that makes some sense. The first one I kind of think of as a site generator: a piece of software that generates static files for a site. Maybe these are just different ways to describe the same sorts of things.

Though the lack of apparent consensus around “headless CMS” makes me feel like it might not be as useful for specifying exactly what one means.

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances

Bonfire social · 1.0.0-rc.2.1 no JS en

Automatic federation enabled