excludeSubdir currently only has a boolean as an option. I read your post about submodules in Hugo and realized that you have set up your website to have markdown files in content for all pages, then for blog posts markdown files in the posts directory. This makes differentiating between "pages" and "posts" is very clean.
But: assume the following content structure (also Hugo):
content
page1/index.md
page2/index.md
blog/2020/...
blog/2021/...
This is currently not possible to set up. If excludeSubdir would allow for an array of folder names, the configuration could have an excludeSubdir: ['blog'] for the page content type. All would be well in these more complicated case structures.
(Edit: I currently do a content type per subfolder instead.)
`excludeSubdir` currently only has a boolean as an option. I read your [post about submodules in Hugo](https://www.eliostruyf.com/managing-hugo-website-content-asset-submodule/) and realized that you have set up your website to have markdown files in content for all pages, then for blog posts markdown files in the posts directory. This makes differentiating between "pages" and "posts" is very clean.
But: assume the following content structure (also Hugo):
content
- page1/index.md
- page2/index.md
- blog/2020/...
- blog/2021/...
This is currently not possible to set up. If `excludeSubdir` would allow for an array of folder names, the configuration could have an `excludeSubdir: ['blog']` for the page content type. All would be well in these more complicated case structures.
(Edit: I currently do a content type per subfolder instead.)
<!-- github-sync-id:1645318426 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
excludeSubdircurrently only has a boolean as an option. I read your post about submodules in Hugo and realized that you have set up your website to have markdown files in content for all pages, then for blog posts markdown files in the posts directory. This makes differentiating between "pages" and "posts" is very clean.But: assume the following content structure (also Hugo):
content
This is currently not possible to set up. If
excludeSubdirwould allow for an array of folder names, the configuration could have anexcludeSubdir: ['blog']for the page content type. All would be well in these more complicated case structures.(Edit: I currently do a content type per subfolder instead.)
We could make it an option to have it a
booleanor anarray.