Question on limitations - nested documentation projects

Hello,

The documentation on Limitations states that "In an included mkdocs.yml, you cannot have !include. It is only supported in the root mkdocs.yml".

I would like to know if this is a design decision or a limitation that could be addressed in the future?

Start by reading the Limitations documentation section describing !include in nested mkdocs.yml files and reviewing the surrounding issue discussion. Done would be a clear decision on whether nested documentation projects should support !include, with the required scope documented if work is pursued.

Written by the indexing model from the issue text.