Perhaps your CMS serves multiple front ends: a website, or a mobile app.
> Why would I want a CMS based on GraphQL?
The way I see it, the CMS is not based on GraphQL, it's just a CMS that you can query with GraphQL. I haven't used GraphQL at all, but it seems like it could be useful for working within a system where you need to bring data from many different REST endpoints together. Usually I would have to hand code something like this myself on the backend, but with GraphQL it seems like once you have it all set up, you can get data from multiple APIs, while specifying the schema of your response on the client instead of on the backend.
> What is wrong, with plain old HTML?
Nothing, if you can build what you want to build with "plain HTML" then do it.
It's describing the CMS, not the API. It's not so familiar to software engineer types, but is pretty well understood in publishing / Drupal / WordPress space.
So you're supposed to put test/markdown and images in it and basic structure like title/date/author? What about data oriented systems instead of content oriented?
I'm not sure I understand your questions. I haven't used GraphCMS so I don't know if they let you store HTML, but some CMS do, and yes that makes it harder to reuse your content in a context other than the web. I don't know, but I assume that you could probably make GraphCMS store HTML if you wanted to. The question of "can the CMS store HTML" seems orthogonal to the question of "Is it headless?" or "Does it have a GraphQL or REST API?"
Perhaps your CMS serves multiple front ends: a website, or a mobile app.
> Why would I want a CMS based on GraphQL?
The way I see it, the CMS is not based on GraphQL, it's just a CMS that you can query with GraphQL. I haven't used GraphQL at all, but it seems like it could be useful for working within a system where you need to bring data from many different REST endpoints together. Usually I would have to hand code something like this myself on the backend, but with GraphQL it seems like once you have it all set up, you can get data from multiple APIs, while specifying the schema of your response on the client instead of on the backend.
> What is wrong, with plain old HTML?
Nothing, if you can build what you want to build with "plain HTML" then do it.