docs(UnoCheck)Improve Structure to find Troubleshooting and configuration options easyer via Searchengine #316
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
maybe we will need to update the toc.yml file also, please check this in addition, I have no idea how this file has to look like correctly and the docfx guide on contribution did not help because I did not find the discribed Uno.UI-tools.slnf mentioned here after installation of the docfx via dotnet |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What is this PR about
Moved the sub Topics into seperate Pages, so the search engine on the docs homepage can list them and they are more visible in the directory for research purposes of users.
also added the common
There are one or more proplems detectedwithout uno-check is providing information about it, where we need to run -verbose to see what is its problemSeperated also the configuration options for same reason, seems to get overseen in the past
[ ] Breaking Changes => no
[x] Closes issue #19015 on the main uno repository but has already been closed from creator, its answering additionally recent upcoming discussions to that problem:
Main Uno repo discussion #14395
Main Uno repo discussion #19079
Anything else?
could we link the Uno check trouble shooting from the main docs trouble shooting area, if the searching person is not first finding this nested area here? Thanks!