You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are managing documentation for around 100 products in a single repository using the MkDocs Monorepo Plugin. The root mkdocs.yml file utilizes !include to include configuration files for each product.
Current Structure:
mkdocs.yml
products/
prod1/
mkdocs.yml
docs/
index.md
topic1.md
topic2.md
prod2/
mkdocs.yml
docs/
index.md
topic1.md
topic2.md
# and so on for 100 products
docs/
index.md
Currently, each rendered HTML page includes the sidebar tree for all 100 products, which significantly increases the artifact size. This is inefficient and can negatively impact the performance and usability of our documentation site.
The text was updated successfully, but these errors were encountered:
Hi @RaizadaHaroon, It's not clear to me how this can be avoided as you are explicitly adding this as you mention. Can you share what you would like to see done for a case like this?
he root mkdocs.yml includes 100 product-specific MkDocs configurations. To manage the large sidebar size, we are using the navigation.prune setting to reduce artifact size. However, this leads to an undesired behavior: clicking on a top-level section in the navigation opens the first available page instead of staying on the current page or expanding the section.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
We are managing documentation for around 100 products in a single repository using the MkDocs Monorepo Plugin. The root mkdocs.yml file utilizes !include to include configuration files for each product.
Current Structure:
Root mkdocs.yml Configuration:
Concern:
Currently, each rendered HTML page includes the sidebar tree for all 100 products, which significantly increases the artifact size. This is inefficient and can negatively impact the performance and usability of our documentation site.
The text was updated successfully, but these errors were encountered: