Excuse my ignorance, and I don't mean to troll.
Why would I want a "Headless" CMS?
Why would I want a CMS based on GraphQL?
What is wrong, with plain old HTML?
Show HN: GraphCMS – A GraphQL-based Headless CMS
31–40 of 70 posts
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#32Graphql is not a product pitch. I don't care. Even your product page just shows an editor that looks like a WordPress article. Why do I need graphql to pull an article from a remote api to my local cache? Your front page is just reasons why graphql is good. Maybe so, but I'm sizing you up for a cms api for my business, not a library. Technology itself is not a product
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#33Excuse my ignorance, and I don't mean to troll. Why would I want a "Headless" CMS? Why would I want a CMS based on GraphQL? What is wrong, with plain old HTML?
Nothing is wrong with plain old HTML. Going headless gives you frontend freedom. It means integrating your content on any platform you like: web, mobile, smartwatch, fridges and toasters (if they are smart enough). It's interesting that we mostly see people using a headless CMS just for web.
Why?
Because they can pick the frontend stack they like! React, react-static, Gatsby, vue, nextJS etc.
You can pick the stack you like most. It is much easier to find a react developer than someone who knows how to write good drupal templates.
Why GraphQL? Because it's awesome! I can highly encourage you to just try out a GraphQL API and see yourself. It is designed for fetching related data efficiently and it will give you a huge boost in development productivity, which means lower development costs and faster time to market.
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#34Graphql is not a product pitch. I don't care. Even your product page just shows an editor that looks like a WordPress article. Why do I need graphql to pull an article from a remote api to my local cache? Your front page is just reasons why graphql is good. Maybe so, but I'm sizing you up for a cms api for my business, not a library. Technology itself is not a product
GraphQL is fun on the frontend. On the backend, there is a gazillion things that need to be considered. You can build a powerful GraphQL backend via the GraphCMS UI.
So we leave you with the fun part.
This has proven very valuable to our users that don't want to implement the backend part of things, while getting a content management interface for editors.
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#35The scary thing to me is if a service like this stops, I have an angry client and a lot of work. Headless CMS's are a delight to work with though.
If there was a commitment to open source if the service was being shut down, I would sign up.
Content is a much larger problem than many realize u til they are dragged into projects that run late, grow too big, and need too many signoffs to be ready.
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#36It'd be rather refreshing if one of the headless CMS PaaS solutions could follow an open model similar to WordPress/Gitlab
Hey! I'm one of the co-founders of GraphCMS. We will soon start open sourcing our content management interface, so users have the opportunity to customize the CMS UI to their needs. Most of our customers just want us to take care of the hosting.
+1 Very interested in self hosting. Especially to meet data residency and locality requirements for a few projects that I have.
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#37Excuse my ignorance, and I don't mean to troll. Why would I want a "Headless" CMS? Why would I want a CMS based on GraphQL? What is wrong, with plain old HTML?
Nothing is wrong with plain old HTML. Going headless gives you frontend freedom. It means integrating your content on any platform you like: web, mobile, smartwatch, fridges and toasters (if they are smart enough). It's interesting that we mostly see people using a headless CMS just for web. Why? Because they can pick the frontend stack they like! React, react-static, Gatsby, vue, nextJS etc. You can pick the stack y…
Thx for all the answers and answer in other threads. Will surely take another look from your angle.
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#38Excuse my ignorance, and I don't mean to troll. Why would I want a "Headless" CMS? Why would I want a CMS based on GraphQL? What is wrong, with plain old HTML?
> Why would I want a "Headless" CMS?
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.
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#39Excuse my ignorance, and I don't mean to troll. Why would I want a "Headless" CMS? Why would I want a CMS based on GraphQL? What is wrong, with plain old HTML?
> What is wrong, with plain old HTML?
Not specific to GraphQL, but plain old HTML doesn't work when other non-technical people are managing the content of the site. They need a GUI, and hence the need for CMS's in general.
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#40It'd be rather refreshing if one of the headless CMS PaaS solutions could follow an open model similar to WordPress/Gitlab
There are lots out there, but the terminology is not consistent so it's hard to identify them.
Perhaps one of these would serve your needs: