Decap i18n with Hugo?

[majdal]

I'm trying to use Decap with my multilingual site built using Hugo (using hugo-blox). I followed the directions here, but they don't include specific directions for translating content.

The i18n section of the Decap docs seems to be missing something. Mainly, I'm having trouble reconciling the directory structure that Decap expects with the one that Hugo(-blox) expects. There are 3 options available for translating content using Decap,

  # Required and can be one of multiple_folders, multiple_files or single_file
  # multiple_folders - persists files in `<folder>/<locale>/<slug>.<extension>`
  # multiple_files - persists files in `<folder>/<slug>.<locale>.<extension>`
  # single_file - persists a single file in `<folder>/<slug>.<extension>`

All of these seem to be inconsistent with what Hugo expects, which is <content>/<locale>/<content type>. I have tried so many different approaches, but I can't get the translation/multilingual interface to appear.

The extensions part of my params.yaml file looks like this (almost identical to the one suggested by Decap docs):

extensions:
  decap_cms:
    local_backend: true
    publish_mode: editorial_workflow
    branch: main
    i18n:
      structure: multiple_folders
      locales: [en, ar]
      default_locale: ar

    collections:
      - name: projects
        label: Projects
        folder: content/en/project
        create: true
        i18n: true
        fields:
          - label: Title
            name: title
            widget: string
            i18n: true
          - label: Date
            name: date
            widget: datetime
            i18n: duplicate
          - label: Body
            name: body
            widget: markdown

Any thoughts on what I should do here? Many thanks!

[martinjagodic]

In my experience, it's best to use the <folder>/<slug>.<locale>.<extension>, which is supported both by Hugo and Decap.

If you want to use <content>/<locale>/<content type>, that would be the multiple_folders option.

[majdal]

I tried that, but I can't tell how the Decap interface should look like for the multiple_files option. There's nowhere no the UI that indicates language as a metadata option.

Let's say I want to make all the content under the content/project available in both ar and en locales. How should my configuration look like?

[janealsh]

I'm dealing with something similar, and my params.yaml file looks almost identical as well

[martinjagodic]

@majdal here is an example configuration

# other root config here (backend, media_library etc.)

i18n:
  structure: multiple_files
  locales: [en, ar]

collections:
  - name: projects
    label: Projects
    label_singular: project
    folder: content/projects
    i18n: true
    create: true
    fields: [
      {name: title, widget: string, i18n: true},
      {name: image, widget: image, i18n: duplicate},
    ]

And this is how the UI should look like:

[majdal]

That's it! Ok, thank you so much.

[privatemaker]

Really nice to see this new granular per-field level i18n parameter 👍🏻

I tried adding i18n: duplicate to a few fields, but now my config errors out with:

I'm using decap-cms 3.4.0 🤔

[martinjagodic]

@privatemaker welcome back :D This seems like a bug report, can you open an issue with a config and instructions to replicate the situation?

[privatemaker]

Done #7332