Content Localization

Hygraph comes with a flexible localization API that teams can use to publish content for all or specific locales in a project.

Explore the Documentation
Content Localization
  • It's best for multi-language e-commerce platforms that have high tariffs.

    Hygraph User
  • My team needed a scalable headless CMS for our homepage, company blog, and all of our periodic content. Why we chose Hygraph: rich-text visual editor, easy-to-use localization feature (our content is in 11 languages), scalability (several hundred thousand visitors per month) and the ability to write content into the CMS programmatically (awesome for importing content from other systems).

    Tatyana M.CEO
  • Localization API is amazing.

    Hygraph User
  • ...we’ve found the platform to be quite flexible. Being able to not only specify relationships between content, but also the way it relates to other parts of the schema (one-to-one, one-to-many, etc.), makes for great control over the schema. We’ve internally started using it for prototypes that go beyond the scope of a simple CMS because of this flexibility.

    Roland P.
  • Hygraph is a way for us to allow non-engineers at our company to create content for our marketing website. Once the engineers define the data model within GraphCMS, other employees at our company can easily add the content through their UI, and once published, our build system automatically rebuilds the website with the new content.

    Hygraph User
  • The interface - It's slick. Intuitive and best of all, rapid fast. You can get exactly what you need done in a fraction of the time for other headless CMS about.

    Doug S. Product Consultant

Mutating Localized Content

The Mutations API is gives developers ultimate control and flexibility when setting up a Hygraph project. As it regards to localization, developers can mutate localized content to create, update, upsert, and delete. Create custom mutations or pull from one of Hygraph auto-generated mutations for modifying the locals for each entry.  

Explore the Documentation

i18n

i18n is the abbreviation for Internationalization, specific to the process by which developers prepare a software or project to be adapted for use in other countries. Beyond managing the creation of content in different languages, this ability to create and distribute content globally also accounts for the various adaptions of the projects to accept different forms of data and settings to match local customs and processes correctly. 

Localization Mutation Permissions

This allows users to specify fine-grained permissions for locales on mutations. For example, a German translator can only update the German-language content but has the ability to read the Spanish, English or content in other languages. The default language of the Hygraph project will always require full access, as it is considered the base content. 

Explore the Documentation