Cascade from _index.md

support
1

I have a site that will utilise a similar setup to the one described here. Isn’t there a way to cascade from _index.md file instead of hugo.toml? Since I would hate to clutter my configuration file with tens or hundreds of these entries.

2

when testing this one Conditionally hide section of site not working

i found no problem when cascading from using _index.md. except if you have a multilingual site. In that case you would have to duplicate the cascades to every languages _index.html

you may switch to a config` directory which a- as of the docs - could have a separate cascade config file

3

I actually tested a cascade.toml file in the config directory but it does not work. I am assuming from the docs that such a file is possible?

[cascade.build]
    list                                    = 'never'
    publishResources                        = false
    render                                  = 'never'
  [cascade._target]
    path                                    = '{/glossary,/glossary/**}'
    lang                                    = '*'
4

shouldn’t you omit the root key?

5

You are correct, but now another issue arises with toml. For example, I have a build and a params key. Using _target throws an error unmarshal failed: toml: table _target already exists.

[build]
    list    = 'never'
    publishResources  = false
    render     = 'never'
  [_target]
    path   = '{/glossary,/glossary/**}'
    lang     = '*'

[params]
foo = 'bar'
[_target]
path = '/books/fiction/**'
6

You must define cascades in the root config file (e.g., hugo.toml). See:
https://github.com/gohugoio/hugo/issues/12899

7

Bummer! And the fact that it is set to unscheduled means it will not be acted upon anytime soon.

8

Well, it’s open source…

9

And the beauty of it is that there are other solutions out there :grin:. I will see if I can restructure the site or find another solution out of Hugo.

1 Like
10

Out of curiousity, why can’t you place the cascade tables in config/_default/hugo.toml?

11

Will that work with the default hugo.toml in root? If it works, then I will go with that. I just didn’t want to clutter the root one.

12

If you are asking, “Does this work?”

project
├── config/
│   └── _default/
│       └── hugo.toml
└── hugo.toml  <-- cascade tables here

The answer is, “Yes.”

However, I find that confusing.

Getting back to the original problem, why would your file be cluttered? Or to put it another way, why would you need hundreds of cascade tables?

13

Like in the link post shared, somehow a decision was made at a place I volunteer to group together some content and I presented the multipage posts solution you shared in another post. However, they wanted again to break that content down like in the linked forum post so that similar content share different titles across different folders in the multipage bundle. I tried that trick and it worked, but when we are talking about more than one multilingual posts, those cascades will add up. Hence my concern about cluttering the hugo.toml at root (and back to my first post about using _index.md to cascade instead).

14

I don’t understand the above, but needing hundreds of cascade values to make it work suggests a design flaw.

15

My thoughts too. But I cannot find a solution yet. So, for now, Hugo might be limited to what we thought we wanted with this project.

content/
├── books/
│   ├── fiction/
│   │   ├── book-1.md
│   │   └── book-2.md
│   ├── non-fiction/
│   │   ├── book-3.md
│   │   └── book-4.md
│   └── _index.md
└── _index.md

I was thinking of doing this but books becomes a nested section of a section. then other pages will be branch bundles in the same structure. So, posts/books, news/books, etc.

So, we will only operate with branch bundles as pages, not leaf bundles.

16

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.