Age | Commit message (Collapse) | Author |
|
Named segments can be defined in `hugo.toml`.
* Eeach segment consists of zero or more `exclude` filters and zero or more `include` filters.
* Eeach filter consists of one or more field Glob matchers.
* Eeach filter in a section (`exclude` or `include`) is ORed together, each matcher in a filter is ANDed together.
The current list of fields that can be filtered are:
* path as defined in https://gohugo.io/methods/page/path/
* kind
* lang
* output (output format, e.g. html).
It is recommended to put coarse grained filters (e.g. for language and output format) in the excludes section, e.g.:
```toml
[segments.segment1]
[[segments.segment1.excludes]]
lang = "n*"
[[segments.segment1.excludes]]
no = "en"
output = "rss"
[[segments.segment1.includes]]
term = "{home,term,taxonomy}"
[[segments.segment1.includes]]
path = "{/docs,/docs/**}"
```
By default, Hugo will render all segments, but you can enable filters by setting the `renderSegments` option or `--renderSegments` flag, e.g:
```
hugo --renderSegments segment1,segment2
```
For segment `segment1` in the configuration above, this will:
* Skip rendering of all languages matching `n*`, e.g. `no`.
* Skip rendering of the output format `rss` for the `en` language.
* It will render all pages of kind `home`, `term` or `taxonomy`
* It will render the `/docs` section and all pages below.
Fixes #10106
|
|
Fixes #12263
|
|
It's not in use and after #12266 it's also not corret to use on its own (use .Site.Home.Permalink).
|
|
Fixes #12266
|
|
Closes #12228
|
|
Fixes #12261
|
|
Fixes #12254
|
|
This commit also optimizes for the case where change events for both file (e.g. `_index.md`) and the container directory comes in the same event batch.
While testing this on Windows 11 (ARM64), I notice that Windows behaves a little oddly when dumping a folder of files into the content tree; it works (at least after this commit), but it seems like the event batching behaves differently compared to other OSes (even older Win versions).
A related tip would be to try starting the server with polling, to see if that improves the situation, e.g.:
```
hugo server --poll 700ms
```
Fixes #12230
|
|
Closes #12244
Closes #12245
|
|
Fixes #12195
|
|
Fixes #12214
|
|
hugo.IsMultiHost => hugo.IsMultihost
hugo.IsMultiLingual => hugo.IsMultilingual
Closes #12232
|
|
Closes #12224
|
|
Fixes #12188
|
|
Fixes #12190
|
|
matches content file name
Fixes #12198
|
|
Fixes #12193
|
|
Fixes #12175
|
|
Sass and Libsass
This fixes the reverse filesystem lookup (absolute filename to path relative to the composite filesystem).
The old logic had some assumptions about the locality of the actual files that didn't work in more complex scenarios.
This commit now also adds the popular Bootstrap SCSS Hugo module to the CI build (both for libsass and dartsass transpiler), so we can hopefully avoid similar future breakage.
Fixes #12178
|
|
with the same path
Fixes #12183
|
|
have an _index.md file
Fixes #12172
|
|
And possibly some other related file mount issues.
Fixes #12133
|
|
exist
Fixes #12132
|
|
Fixes #12169
|
|
Fixes #12141
|
|
Fixes #12163
|
|
Also clean up the log handling in the integration tester, most notably lost logs during the config loading.
Fixes #12151
|
|
Closes #12146
|
|
Which means that .Name now returns the same as it did in 0.122.0.
Closes #12142
|
|
Fixes #12144
|
|
Fixes #12137
|
|
```
name old time/op new time/op delta
GetPage-10 413ns ± 0% 287ns ± 1% -30.47% (p=0.029 n=4+4)
GetPageRegular/From_root-10 757ns ± 1% 706ns ± 1% -6.75% (p=0.029 n=4+4)
GetPageRegular/Page_relative-10 838ns ± 1% 786ns ± 1% -6.16% (p=0.029 n=4+4)
name old alloc/op new alloc/op delta
GetPage-10 312B ± 0% 24B ± 0% -92.31% (p=0.029 n=4+4)
GetPageRegular/From_root-10 328B ± 0% 200B ± 0% -39.02% (p=0.029 n=4+4)
GetPageRegular/Page_relative-10 360B ± 0% 232B ± 0% -35.56% (p=0.029 n=4+4)
name old allocs/op new allocs/op delta
GetPage-10 8.00 ± 0% 2.00 ± 0% -75.00% (p=0.029 n=4+4)
GetPageRegular/From_root-10 7.00 ± 0% 5.00 ± 0% -28.57% (p=0.029 n=4+4)
GetPageRegular/Page_relative-10 9.00 ± 0% 7.00 ± 0% -22.22% (p=0.029 n=4+4)
```
|
|
Fixes #12120
|
|
Whether to capitalize automatic page titles, applicable to section,
taxonomy, and term pages. Default is true.
Closes #9793
Closes #12115
|
|
Fixes #12105
|
|
But note that the overlay file system is set up horizontally (project -> module1 -> module2), so I would not recommend too complex overlapping mount setups within the same module.
But this worked in v0.122.0, so we should fix it.
Fixes #12103
|
|
Fixes #12101
|
|
Fixes #12092
|
|
Fixes #12094
|
|
Fixes #12096
|
|
Fixes #12082
|
|
Fixes #12072
|
|
Same as we do in .Get.
Fixes #12076
|
|
Fixes #12071
|
|
Fixes #12065
|
|
Fixes #12058
|
|
The partial rebuilds works by calaulating a baseline from a change set.
For new content, this doesn't work, so to avoid rebuilding everything, we first
try to collect a sample of surrounding identities (e.g. content files in the same section).
This commit fixes a flaw in that logic that in some (many...) cases would return a too small sample set.
Fixes #12054
|
|
|
|
By just removing the term page and all of its page entries.
Fixes #12055
|
|
Fixes #12041
|