Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: GraphCMS – A GraphQL-based Headless CMS

graphcms.com

Post reply on HN
Print view View original

61–70 of 70 posts

Re: Show HN: GraphCMS – A GraphQL-based Headless CMS

#61

Post by shrthnd »

meritt wrote: post #16
neeksHN wrote: post #5

Earlier quoted context omitted.

Directus is always at the top of self-hosted CMS lists, but one of the reasons I avoid it and other PHP self-hosted headless CMS solutions is due to the difficulties(tech debt) of automating dev environments and CI/CD pipelines across different distros and OSes. I would have possibly given Directus a spin if it didn't have hard dependencies on the following PHP system extensions: curl, gd, finfo, pdo_mysql and mbstri…

The problem you're describing is precisely why containers are so popular. You can install and deploy any app even if it doesn't provide user-level installation choices (such as php native extensions)

  curl -O https://github.com/directus/directus-docker/blob/master/docker-compose.yml
  docker-compose up

Re: Show HN: GraphCMS – A GraphQL-based Headless CMS

#62

Post by 578493025678493 »

ericfrederich wrote: post #22

>> Can I host GraphCMS on my own servers? >> Please talk to sales to discuss deployment options. This is not an answer. Talk to sales? I don't mind paying for support. I'm not a fan of paying for enterprise features. I would never want a dependency to something which is not free.

Craft CMS is designed for deployment on your own servers. It does not offer a hosted version as yet, but has just as strong a headless mode with full graphql support with craftql.

Re: Show HN: GraphCMS – A GraphQL-based Headless CMS

#63

Post by heisnotanalien »

mlukaszczyk wrote: post #29
ericfrederich wrote: post #22

>> Can I host GraphCMS on my own servers? >> Please talk to sales to discuss deployment options. This is not an answer. Talk to sales? I don't mind paying for support. I'm not a fan of paying for enterprise features. I would never want a dependency to something which is not free.

Our new architecture allows much more flexibility on the deployments, so just speak to us about your favorite setting. However, it is quite complex and we rather focus on delivering a high quality cloud infrastructure that works for everyone. I can understand your perspective but our mantra is to remain a SaaS company, which means to be able to focus on ONE code base. This allows us on delivering a higher quality pro…

So basically no?

Re: Show HN: GraphCMS – A GraphQL-based Headless CMS

#64

Post by artpar »

jonheller wrote: post #12
les wrote: post #10

The 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.

Exactly. Or drastically changes their pricing model (see: Contentful). I understand the benefits of all of these individual services, but I also miss the days of the only service I had to worry about when I handed off a client site was hosting. Now it's often the headless CMS hosting (i.e. Contentful, GraphCMS), actual hosting (Netlify), CDN, Image CDN, Search (i.e. Algolia). So many places for things to break. So ma…

Checkout daptin if you are looking for an open source self hosted solution for headless cms

https://github.com/daptin/daptin

Re: Show HN: GraphCMS – A GraphQL-based Headless CMS

#66

Post by mlukaszczyk »

heisnotanalien wrote: post #63
mlukaszczyk wrote: post #29

Earlier quoted context omitted.

Our new architecture allows much more flexibility on the deployments, so just speak to us about your favorite setting. However, it is quite complex and we rather focus on delivering a high quality cloud infrastructure that works for everyone. I can understand your perspective but our mantra is to remain a SaaS company, which means to be able to focus on ONE code base. This allows us on delivering a higher quality pro…

So basically no?

So basically, lets talk.

Re: Show HN: GraphCMS – A GraphQL-based Headless CMS

#67

Post by dustingetz »

djhartman wrote: post #38
ksec wrote: post #31

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?

> 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…

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?

Re: Show HN: GraphCMS – A GraphQL-based Headless CMS

#68

Post by armandososa »

neeksHN wrote: post #2

It'd be rather refreshing if one of the headless CMS PaaS solutions could follow an open model similar to WordPress/Gitlab

WP is extremely modifiable. I think it would be trivial* to turn WP into a headless CMS. I made a proof of concept some years ago and it was great because you could still use plugins to transform the content. Alas, feeding-my-family realities prevented me to pursuit that project.

* Of course with "trivial" I meant possible.

Re: Show HN: GraphCMS – A GraphQL-based Headless CMS

#69

Post by djhartman »

dustingetz wrote: post #67
djhartman wrote: post #38

Earlier 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…

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?"
Post reply on HN