Skip to content

docs(Configuration): adding visual content and improve structure for brevity #362

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

DevTKSS
Copy link
Contributor

@DevTKSS DevTKSS commented Apr 8, 2025

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:

  • Will check if toc.yml needs future adjustments
  • Check added files to be linked properly
  • Enhanced Readme.md file so it can also be used as Intro

TODO:

  • Build has to show if the link to UnoCheck.Intro is successfull this way

Help needed:

  • Structure inside of Tabs should be unified similar to api docs with syntax, explaination incl. sample and to be checked synonym arguments, but this could also be done in syntax area before.

@DevTKSS
Copy link
Contributor Author

DevTKSS commented Apr 30, 2025

@agneszitte FYI: all checks passed here :)

@DevTKSS
Copy link
Contributor Author

DevTKSS commented May 6, 2025

@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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's keep using english for the screenshots

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeromelaban okay, then I will need someone to help for the screenshots, as my system is only german and until now I did not found an option to tell dotnet cli I want en-US loc output.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@DevTKSS you can simply "set DOTNET_CLI_UI_LANGUAGE=en" if you are on Windows

@DevTKSS DevTKSS requested a review from Takoooooo June 17, 2025 18:37
@DevTKSS DevTKSS force-pushed the docs-adding-skip-details branch from 6555c30 to eb902f3 Compare June 22, 2025 14:30
DevTKSS and others added 2 commits June 22, 2025 16:42
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

docs(uno-check): Add visual content and improve structure for brevity

docs(uno-check): Add visual content and improve structure for brevity

Co-authored-by: Jérôme Laban <[email protected]>
@DevTKSS DevTKSS force-pushed the docs-adding-skip-details branch from 5680686 to d2ffbaf Compare June 22, 2025 14:43
@DevTKSS
Copy link
Contributor Author

DevTKSS commented Jun 22, 2025

To check: the tfm flag should normally not be equal to the target flag:

--target should stand for the current checked targets like desktop, windows, winsdk ios or android
--tfm should stand for the net version like net9.0 or net10.0 in the future or major-prerelease case

@DevTKSS
Copy link
Contributor Author

DevTKSS commented Jun 22, 2025

Seems like this is indeed failing just because of issue #417 While I did not even realize the CI would fail on this PR because of the version 😅
I am curious how that worked out before. 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants