All blog posts

You can now directly fetch content from remote systems using one single Hygraph API, without the need to link remote content to content hosted in Hygraph.

One content API, unifying your entire stack. Content Federation allows you to source external data directly from your Hygraph content API.

One year after GraphQL was open sourced, the community and ecosystem around this technology is growing rapidly. The GraphQL project left the stage of technical preview and the GraphQL website was relaunched with a shiny new design. In mid-September, GitHub announced their new GraphQL-API, which is huge news for the growing GraphQL community.

This is a guest post by Jeff Escalante. One of the great advantages of headless CMS' is that they are able to be consumed by a wide variety of different applications and build tools, rather than being tied specifically to a web frontend. And today we'll be talking about using Hygraph to create a static site - an architecture that suits many use cases much better than using a dynamic site or single page app.

The awesome folks over at Snipcart just released a great blog post on how to integrate their powerful shopping cart with a Hygraph powered website.

Hey everyone, it's been a while! We have been pretty quiet in the last weeks. The reason for this is, because we have been working very focused on the redesign of our new systems API. The systems API is basically the API our web app is talking to. It is responsible for creating projects, models, fields, adding members to your team etc. We are happy to announce that we just ported the CMS to the new API and all migrations are complete.

Using Wordpress for your production site can be quite a challenge. The more plugins you integrate, the less maintainable your code gets. The content editing is kind of clunky and feels just unnatural. Hacky code becomes your daily business.

Headless Content Management Systems have grown big time in the recent years and are enjoying immense popularity. The really big difference to a conventional CMS is the missing front-end, which certainly opens up a great set of possibilities. For developers, the headless CMS provides an API for the stored content. For editors, the CMS provides great tooling to manage all their content. Your front-end applications then fetch data from this API and displays it.

We just released a new version of our documentation featuring improvements to the assets section and a new guide on nested mutations!