It can be hard to visualize so people may ask what could this look like?
From there a headless cms can use the api to render the data as a site. It can be static, or dynamic.
It can be hard to visualize so people may ask what could this look like?
From there a headless cms can use the api to render the data as a site. It can be static, or dynamic.
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.
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