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!

Recently, we got interviewed on Siftery! We also wanted to share this interview on our blog. Enjoy reading! Kevin William David interviewed Michael Lukaszczyk, Co-Founder at Hygraph to know more.

At Hygraph, we constantly want to improve user experience and invest into new features. We also want to deliver the highest performance possible, no matter where you are located. While we are still working on content localization (it's ready very soon, I promise ? ) and more features to come in the next months, we are happy to introduce our newest feature today:

Since launching GraphCMS nearly 3 months ago, we have processed millions of API requests and are continuously welcoming an ever growing community.

Hygraph is now a Headless CMS with Localization out of the box! Get up and running with i18n at project setup, and deploy to all or specific locales.

This tale tells of a time before now, when Gatsby.js (a static site generator that combines React and GraphQL) was only using GraphQL internally. Gatsby could fetch data from static files, contentful APIs, Wordpress databases, and mongoDB, but it never fetched the seed data with GraphQL. Angel, the original plugin author and project leader, looked into static site generators for his personal website remake. He thought to himself, “Well, that doesn’t make much sense, does it?” And the idea was born.