Do people really care about the library used to build their CMS? Surely this will only appeal to those that already use GraphQL...
Show HN: GraphCMS – A GraphQL-based Headless CMS
41–50 of 70 posts
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#42Do people really care about the library used to build their CMS? Surely this will only appeal to those that already use GraphQL...
It's about the language front-to-back. The language that builds the CMS is also the language that you build your sites with! So you keep the overhead low on various technologies being used. Yes, GraphQL users are the primary people drawn to the app, but that's sort of true for any platform?
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#43Can't wait to use the new version! I've been looking forward to a lot of the new features.
Great! Excited to see what your thoughts are on it!
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#44mlukaszczyk,
Is GraphCMS a Graphcool service? I see their style of sorting and filtering in your API. If so, what's your experience with Graphcool, and what value does GraphCMS add?
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#45It'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.
> We will soon start open sourcing our content management interface, so users have the opportunity to customize the CMS UI to their needs.
"We're going to open source the interface" is a disingenuous answer to the question. Documenting an interface isn't open source. If your plan is "proprietary SaaS", just own it.
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#46Excuse 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 togethe…
"Headless" is a weird term for an HTTP API.
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#47I reviewed the site. I still have no idea what GraphCMS does.
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#48mlukaszczyk, Is GraphCMS a Graphcool service? I see their style of sorting and filtering in your API. If so, what's your experience with Graphcool, and what value does GraphCMS add?
Hey Hirundo,
the former GraphCMS was built on top of Graphcool, with the new system, we also move to Graphcool's new product, Prisma, which is a setting we enjoy a lot. Prisma runs at the core for CRUD and then we add an additional API layer to it to add the features we think make sense in a CMS context.
The value add depends on perspective. If you are looking for a tool to build a content database, then GraphCMS brings definitely a lot to the table. While you get the content management interface and tools, we add just enough opinion to the APIs that makes sense in a context of building a content database.
Graphcool is also not actively maintained anymore as the team is now focusing on Prisma.
The Demo-API on the landing page is from the former stack. We will soon add a new example to showcase all the new API utils.
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#49Excuse 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?
What do you mean by this?
Re: Show HN: GraphCMS – A GraphQL-based Headless CMS
#50Earlier quoted context omitted.
> 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 togethe…
"Headless" is a weird term for an HTTP API.
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.