docs(Configuration): adding visual content and improve structure for brevity #362
Conversation
Latest dotnet will guide user to right direction xref applying like main uno repo added include by xref for GettingHelp with TroubleShooting sourced from Main Repository includes
Latest dotnet will guide user to right direction xref applying like main uno repo added include by xref for GettingHelp with TroubleShooting sourced from Main Repository includes
deleted second trailing new line at file end after rebase
see docfx issues for future details to this
…ot solvable conflicts
|
@agneszitte FYI: all checks passed here :) |
|
|
||
| ### `--target` Choose target platforms | ||
| # [**target platforms**](#tab/arg-target) |
There was a problem hiding this comment.
Can we instead of the descriptions use the name of the parameter instead everywhere? In that case [-t|--target]. Becuase to users that not familiar with these parameters just "Target platforms" or "Continuous Integration" won't tell anything. Lets make the parameter name the header of the tab and the context of the tab will describe what it does
There was a problem hiding this comment.
will check on them and then add the screenshots taken here. but for those with the --version and --help I only get them with localized description, maybe that will then need someone with en-us localization to adjust this parts
| [!INCLUDES [uno-check-help](../includes/uno-check-help.md)] | ||
|
|
||
| The following command line arguments can be used to customize the tool's behavior. | ||
| [!INCLUDES [Uno-Check-Windows-Elevation](../includes/uno-check-help.md)] |
There was a problem hiding this comment.
Not sure why we need these?
For me it doesen't render and also it references the same link
There was a problem hiding this comment.
@Takoooooo are those the build or vs code preview? seems like no extension is capable of rendering includes at this moment. try it with local build instead. I set up for myself a docfx with modern template (PR at main repo thats needs someone fix the last powershell location issue to hopefully than enable also non uno team contributors use the import external docs script to get their externals if some to check them) to validate those kind of things locally. as you will know, thats not optimal as workaround but I dont know any other way to get there realistically otherwise
|
@Takoooooo added the local images I meant already now, maybe you want to take a look and replace if yours is localized correctly so i could link them then later on |
Visual Content to simplify understanding possibilities (skip and list of skips can be tricky)
added information about help argument is available
Seperated CI topic to own area
Done:
TODO:
Help needed: