Single language configuration

[thackmaster]

I'm new to Hugo, and wanting to utilize Hinode for a site of mine that will only be written in one language. I updated the hugo.toml file as documented to remove the /en/ slug but things aren't going as expected.

languageCode = 'en-us'
defaultContentLanguage = "en"
defaultContentLanguageInSubdir = false

Items from /content/en/blog still load with the /en/ slug even after rebuilding the site. So I moved the content out of /content/en/blog to /content/blog. That causes it to not load on the front page though it still exists via its content path.

I'm clearly missing something here and would just like a little guidance on what I'm doing wrong. Thanks!

[markdumay]

You may have to adjust contentDir in your language configuration too, see config/_default/languages.toml. The following configuation tells Hugo to use the content dir (without the en subfolder):

[en]
    languageName = "English"
    contentDir = "content"
    weight = 1

The Hinode repository contains two site examples. You might want to take a look at each configuration.

• npm run start - starts a plain, single-language site without any content. The configuration is defined in /config/.
• npm run start:example - starts a multi-language site with multiple translated pages. The configuration is defined in /exampleSite/config/.

[thackmaster]

I think I was misunderstanding the instructions. I was thinking that since I was overriding config/_default that I didn't need to have the directory with the appropriate files I was overriding (copied those from the exampleSite directory). Additionally, when I read "remove the language slug /en from your site entirely", I was under the impression that it also removed it from the URL, not the breadcrumbs at the top of pages.

Thanks for your help!