mlukaszczyk

Windows Vista. Is that you?

A curated list of competitive intelligence tools, resources, frameworks, and best practices for tracking and analyzing competitors.

Thanks! That would work easily with GraphCMS!

GraphCMS | (Senior) Golang Developer | Remote/Berlin/Giessen | Full-time | https://graphcms.com

We are looking for a Senior Backend Golang Engineer, who will help us improve the most advanced content management system worldwide. As a Backend Engineer at GraphCMS, you will take care of extending and solidifying our backend architecture.

Please find the job description here: https://jobs.graphcms.com/o/senior-golang-backend-engineer-m...

Gatsby did a great job incorporating Mikhail Novikov's work on the Gatsby Source GraphQL plugin. Kudos!

If you want to see another example of Gatsby powered by a GraphQL native CMS, check out the following tutorial: https://docs.graphcms.com/tutorials/developers/gatsby_and_gr...

So basically, lets talk.

TLDR; It allows you to bring content to any platform.

It allows you to build content databases in an easy and visual manner. Once you have your content in GraphCMS, you are able to fetch it in an elegant way by using GraphQL. The target platforms that consume the content can be anything: web, mobile, alexa skills or just business partners you want to share digital content with so that they can put it on the target platform of their choice.

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.

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.

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.

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 product in the long run so all users can benefit from it.

Can you please elaborate? How would that replace an API based CMS?

PS: A CLI will also follow.

You could use the management API for this. It's basically the same API the content management interface also speaks to. You can open up the API explorer and switch to the management API in the top bar and play around with it!

(fyi: the documentation is not released, yet)

I definitely can understand this point of view! But this is actually the case for all SaaS's out there. I would even say that this is also the case for open source projects if there aren't maintained anymore and the costs for trying this yourself are too high.

One benefit of the nature of a headless CMS though, is that there can't really be a vendor lock-in on your content.

100% Agree.

GraphCMS is the only CMS that exclusively offers GraphQL. Other CMSs have since entered the space to offer GraphQL technology, but they still try to maintain both REST and GraphQL APIs which will lead to some maintenance issues in the future. An example of this is that the other CMSs aren’t able to offer a “mutation” API for their CMS through GraphQL. With our CMS you can query the data and change it through the same powerful interface. This opens the door to a wide range of tooling and custom workflow enhancements. Additionally, because we only offer GraphQL, we are able to be more agile with changes to the technology.

In the future, our focus will shift even more to content based BaaS as we will support end user authentication. We are also preparing a new suite of workflow tools that will make managing large datasets a breeze.

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.

Guys! This looks extremely promising like all the things you create.

What databases does it support?

Also love the name and logo. I see you at the dark side of my resolvers :v