| Age | Commit message (Collapse) | Author |
|---|
|
[ci skip]
|
|
[ci skip]
|
|
No practical difference.
|
|
We need to revisit the commands package re globals and tests, but this should fix the init order of flags and languages.
Fixes #4589
|
|
[ci skip]
|
|
[ci skip]
|
|
Fixes #4563
|
|
[ci skip]
|
|
A sample config:
```toml
defaultContentLanguage = "en"
defaultContentLanguageInSubdir = true
[Languages]
[Languages.en]
weight = 10
title = "In English"
languageName = "English"
contentDir = "content/english"
[Languages.nn]
weight = 20
title = "På Norsk"
languageName = "Norsk"
contentDir = "content/norwegian"
```
The value of `contentDir` can be any valid path, even absolute path references. The only restriction is that the content dirs cannot overlap.
The content files will be assigned a language by
1. The placement: `content/norwegian/post/my-post.md` will be read as Norwegian content.
2. The filename: `content/english/post/my-post.nn.md` will be read as Norwegian even if it lives in the English content folder.
The content directories will be merged into a big virtual filesystem with one simple rule: The most specific language file will win.
This means that if both `content/norwegian/post/my-post.md` and `content/english/post/my-post.nn.md` exists, they will be considered duplicates and the version inside `content/norwegian` will win.
Note that translations will be automatically assigned by Hugo by the content file's relative placement, so `content/norwegian/post/my-post.md` will be a translation of `content/english/post/my-post.md`.
If this does not work for you, you can connect the translations together by setting a `translationKey` in the content files' front matter.
Fixes #4523
Fixes #4552
Fixes #4553
|
|
This allows a `config.toml` (or `yaml`, ´yml`, or `json`) in the theme to set:
1) `params` (but cannot override params in project. Will also get its own "namespace", i.e. `{{ .Site.Params.mytheme.my_param }}` will be the same as `{{ .Site.Params.my_param }}` providing that the main project does not define a param with that key.
2) `menu` -- but cannot redefine/add menus in the project. Must create its own menus with its own identifiers.
3) `languages` -- only `params` and `menu`. Same rules as above.
4) **new** `outputFormats`
5) **new** `mediaTypes`
This should help with the "theme portability" issue and people having to copy and paste lots of setting into their projects.
Fixes #4490
|
|
To prepare for config in themes
See #4490
|
|
|
|
Issue introduced some days ago.
Fixes #4516
|
|
[ci skip]
|
|
[ci skip]
|
|
Fixes #4456
|
|
[ci skip]
|
|
That logic fails in multi-host mode when no baseURL is set on top level.
Fixes #4397
|
|
See #4434
|
|
[ci skip]
|
|
[ci skip]
|
|
Updates #4339
|
|
According to @bep, it is easier to undraft content by
editing manually the frontmatter of said content by
setting the draft flag to `false`, or removing it completely,
than to rely on the undraft command which is a source of
many bugs.
Fixes #4353
|
|
See #4347
|
|
preserveTaxonomyNames, uglyURLs
You can of course still set them in site config.
Fixes #4347
|
|
The current behaviour addes a `url` attribute to the frontmatter of all posts imported from Jeklly and assumes the desired permalink structure is /:year/:month/:day/:title/. This may be the case for most peeps, but poses a problem for those that don't use this permalink structure as the `url` attribute takes precedence over the `permalink` attribute in the site-wide configuration meaning it can't be overruled.
This changes the behaviour to only set the `url` attribute if the `permalink` attribute is set in the Jekyll frontmatter.
The duplication of the confirmation message is also removed.
Tests have been updated to reflect this change in behaviour.
Fixes #1887
|
|
This was introduced in 6413559f7575e2653d76227a8037a7edbaae82aa a couple of days ago, and demonstrates that we really need better tests for the server/commands package.
Fixes #4333
|
|
This commit adds a new config setting:
```toml
disableLanguages = ["fr"]
```
If this is a multilingual site:
* No site for the French language will be created
* French content pages will be ignored/not read
* The French language configuration (menus etc.) will also be ignored
This makes it possible to start translating new languages and turn it on when you're happy etc.
Fixes #4297
Fixed #4329
|
|
* Page without front matter now treated same as a page with empty front matter.
* Test cases added to cover this and repro issue #4320.
* Type safety of front matter code improved.
Fixes #4320
|
|
|
|
[ci skip]
|
|
[ci skip]
|
|
See #4275
|
|
This was broken in Hugo 0.30.
Fixes #4275
|
|
Fixes #4272
|
|
[ci skip]
|
|
[ci skip]
|
|
Fixes #4246
Fixes #4248
|
|
This reverts commit 768ec5df9fa8f91610ee80a9e6194f94a7dbe117.
|
|
This is no longer supported. Since Hugo 0.32 we do static sync and build in parallel.
Closes #4246
|
|
[ci skip]
|
|
[ci skip]
|
|
Fixes #4232
See #4224
|
|
Fixes #4218
|
|
[ci skip]
|
|
[ci skip]
|
|
[ci skip]
|
|
[ci skip]
|
|
The `--renderToMemory` flag stopped working on `hugo` in 0.32.
Note that this is only useful for benchmark testing, as there is no easy way to actually view the result.
Fixes #4212
|
|
[ci skip]
|
