What to do with `config.toml` when making a multilingual site?

support
1

Here Multilingual mode | Hugo it says

If you had more domains and languages, you would just create more config files. The standard config.toml is what Hugo will run as a default, but since we’re creating language-specific ones, you’ll need to specify each config file when running hugo server or just hugo before deploying.

So, for english and japanese versions I would have config_en.toml and config_ja.toml.

But what to do with config.toml? Remove?

I think, the docs should give an advice on this.

2

Yes, remove. The docs could be more clear about this, but the important piece of information here is that there is ONE config file per site.

1 Like
3

@askar You can rename config.toml to one of those versions that has the locale as prefix. You don’t need to have a file called config.toml, because the command --config="" allows you to specify a custom name for the config file.

1 Like
4

See: Multi-Language (each with it’s own content) in single tree,