Specifying sub-theme location

support
1

The Hugo docs state that:

a project can configure a theme as a composite of as many theme components you need
[…]
You can even nest this, and have the theme component itself include theme components in its own hugo.toml (theme inheritance).

Consider a project with the following structure:

project/
project/themes
project/themes/config.yaml
project/themes/our-theme-name
project/themes/our-theme-name/config.yaml
project/themes/our-theme-name/themes/sub-theme-name

To use the sub-theme, we currently have to specify, in our-theme-name/config.yaml:

theme:
  - our-theme-name/themes/sub-theme-name

The project 'project/config.yaml` would then use our theme using:

theme:
  - our-theme-name

This works fine, but I worry about projects that, e.g., check out our theme under a slightly different name. With our implicit assumption around the folder structure, that would break things.

Would it make sense to have the following our-theme-name/config.yaml work?

theme:
  - sub-theme-name  # searches in `our-theme-name/themes`