Publishing Per Locale

Scale content globally with a core feature of Hygraph. Define how many locales are needed within the project and manage each translation easily within one content model.

  • 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

Optimize Workflows

Locale Based publishing helps teams optimize their workflows and keep teams efficient. If additional locales are outsourced to external companies, they are able to see the published default locale and base their content on the default locale. Teams have the flexibility to create workflows that work for them. If they want to slowly build out pages and continually add locales, that is possible with Hygraph. If teams prefer to create a full project in one locale and then create page by page a localized version of that page, that is also possible.

Teams are able to plan ahead with Locale Based Publishing. It allows them to determine which locales will be target locales in the future, enable them in the schema, and leave them in an unused draft state until they have the capacity to create content for the additional locale.