Hugo has two approaches to manage translated content with files:
- including the language code in the filename, or
- including the language code in the content directory/folder.
Note that Hugo does not support using both approaches at the same time.
Because CloudCannon collections are based around folders, the approach you choose will change the editing experience. This guide outlines the best practices for each approach.
This guide focuses on integrating with CloudCannon, it does not cover:
- Setting up a multilingual Hugo site; we recommend Hugo Multilingual Part 1: Content translation by Régis Philibert.
- The Hugo
i18nshortcode, which could be added as a Snippet.
- Multihost introduces editing problems as a site on CloudCannon uses one domain. Using multiple sites in a staging-production workflow can work around this.