-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
multilingual: Add option to keep the main language on top level #2312
Comments
You mean you'd like to render the English homepage at the complete root ? I use a quick redirection based on browser settings with a hard coded GolangMontreal.org/index.html Le ven. 29 juil. 2016 02:15, Bjørn Erik Pedersen notifications@github.com
|
Yes.
Yes, and that is the good an natural solution for the "full multilanguage" sites. But that does not fit some of my use cases, for SEO reasons etc. (I don't want to move 90% of my URLs one level down), I don't want my "main page" be a redirect etc. |
OK this shouldn't be very difficult.. as the addition of prefixes happens Le ven. 29 juil. 2016 10:12, Bjørn Erik Pedersen notifications@github.com
|
Things to keep in mind when implementing:
|
This commit also unexports some Site methods, making it clear what the external build API really is. See #2312
What I did (if I didn't document it, I should), is I wrote a static
|
This commit also unexports some Site methods, making it clear what the external build API really is. See #2312
This commit also unexports some Site methods, making it clear what the external build API really is. See #2312
This commit also unexports some Site methods, making it clear what the external build API really is. See #2312
This commit also unexports some Site methods, making it clear what the external build API really is. See #2312
This commit also unexports some Site methods, making it clear what the external build API really is. See #2312
This commit also unexports some Site methods, making it clear what the external build API really is. See #2312
This commit also unexports some Site methods, making it clear what the external build API really is. See gohugoio#2312
@bep Hi there, I got a problem when I test Hugo Multilingual Mode for my unfinished Hugo theme, and I Google here... Briefly, Hugo generated a useless folder My defaultContentLanguage = "zh"
defaultContentLanguageInSubdir = false
[languages]
[languages.zh]
languageName = "中文"
contentDir = "content/zh"
weight = 0
languageCode = "zh-CN"
hasCJKLanguage= true
[languages.en]
languageName = "English"
contentDir = "content/en"
weight = 1
languageCode = "en-US" What’s more, this folder still could not be removed after I’v tried some tricks, such as:
Although this folder has no side effects and I can delete it by myself or bash script, it would be great if Hugo won’t generate it at all or give an option to config it. Thx. |
Oh I see… It’s not useless… The |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
See #2309
I'll add this here for discussion
I'll take two of my Hugo sites as an example:
http://bepsays.com/ => Norwegian
http://bep.is/ => English
bepsays.com
has some English content, so I would love to have ahttp://bepsays.com/en/
, but I would still like my old URLs (the main content) to live as before.bep.is
has a short presentational text in English. It would be cool to point to translations in French, Japanese etc., but I would still like the main language to stay where it is.on
/cc
@abourget
@spf13
@RickCogley
@the1900 I
The text was updated successfully, but these errors were encountered: