docs(TOC): Align Overview Items to improve user-experience while lookup #2898
+89
−89
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GitHub Issue (If applicable): closes #
PR Type
What kind of change does this PR introduce?
What is the current behavior?
the C# Markup, Maui Embedding and Mvux section of the Learn Folder Contents are not right below the
OverviewTOC Parent Entry then showing up like a standalone entry.Always when I am searching for the Mvux Overview Contents I am intuitivly searching below Overview, in case I not search for the in depth Reference, until I remember that this is having this misaligned TOC structure. So its no actual issue solving PR, but a improvement and simplification for those like me who looking up something in the docs and kind of stumbling over this, which is a quite easy and quick fix 👍
What is the new behavior?
All UnoFeatures available Topics, especially those who have an additional Reference Entry are now correctly listed under the Overview Section instead of be each a standalone entry, so we can quick and intuitivly find them 👍
PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Runresults.Other information
Its no actual issue solving PR, but a improvement and simplification for those like me who looking up something in the docs and kind of stumbling over this, which is a quite easy and quick fix 👍
Internal Issue (If applicable):