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.

Speed up Content Creation

Locale-based publishing also speeds up content creation across the board. Once the first iteration of a locale is complete, the team can publish and move on to other content without having to waste time waiting for other locales to be complete.

Locale-based publishing opens up possibilities from integrating with 3rd party translation services into workflows because external editors are able to work with the existing locale as a guide for translation and structure of the next locale. After the default locale is in place, teams are able to work efficiently to build additional locales and can take advantage of 3rd localization services.

Refine and Test Content

In some cases, it may be helpful for teams to test marketing content for each locale rather than have each locale be a direct translation of the default locale. We have all seen examples where direct translations lose their meaning when they do not reach the correct audience.

With locale-based publishing, teams are able to build content that will bring the most value to the intended audience. As teams iterate the content, they are able to run tests based on the localized content and continue to refine one locale’s content without impacting additional locales.

Build Modern Products & Modern Teams

Modern digital products are created by a global team for a global audience. Locale-based publishing enables teams to work efficiently, reach new audiences as their product grows, be flexible to changes in taste or capacity. If a digital product gains traction in a market that was not initially anticipated, it is easy to create localized content for the new locale once the initial localized structure is in place.

Teams that plan ahead and want to avoid costly redesigns will account for localization from the beginning of the project. With locale-based publishing, teams are able to have the localized structure from the beginning of the project and wait until the team has the capacity to add additional locales. Because the content of the locales exists independently of each other, teams remain flexible and workflows accommodate the modern style of a global team.