Content engineering

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.

Add custom fields to your uploaded files, like a description or an alt text. This crucial feature allows you to implement functionality based on your asset's meta information.

Following in the footsteps of these pioneering 20th-century industrialists, early 21st century enterprises are breaking down software monoliths into modular, highly-specialized microservices.

This article introduces Agile Content Management, its key benefits, and how Headless CMS systems, like Hygraph, can allow your business to soar.

A lot of professionals get stuck in a configuration where they combine a React(-like) library with WordPress as a headless CMS.

It's relatively simple to ensure you're not sacrificing any SEO best practices when using a Headless CMS.

How can teams ensure that content that is being produced is timely, brings value, and that new team members can quickly join the team and start producing content?

Picking up from our earlier post on Agile Content Marketing, here is how we approach content at Hygraph.

We recently had a conversation with Kaya Ismail, discussing everything around Headless CMS for scaling business needs.