We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Related to #19
The Home Page is a wall of blocks:
It'd be nice to group it and have at least a group of 'new' things at the top.
This kind of related to the 'experimental' field in Markdown we use for the yellow 'labs' label.
Maybe we could have the concept of tags?
In our cases we'd have 'NEW' and 'LABS' which would get their own groups on the home page and get bubbles next to items in the navigation view.
Not sure if we should have others as tags are generally a general concept. But these are like big identifiers...
Thoughts?
Maybe we'd change the 'experimental' markdown field to tags or something and have it be more freeform? Not sure what the best approach here is... https://github.com/search?q=repo%3ACommunityToolkit%2FTooling-Windows-Submodule%20experimental&type=code
N/A
Better organization of Home Page
No response
No, I'm unable to contribute a solution.
The text was updated successfully, but these errors were encountered:
We should consider adding a view that groups sample docs by the component they're in. Needed for #8
Sorry, something went wrong.
Arlodotexe
No branches or pull requests
Describe the bug
Related to #19
The Home Page is a wall of blocks:
It'd be nice to group it and have at least a group of 'new' things at the top.
This kind of related to the 'experimental' field in Markdown we use for the yellow 'labs' label.
Maybe we could have the concept of tags?
In our cases we'd have 'NEW' and 'LABS' which would get their own groups on the home page and get bubbles next to items in the navigation view.
Not sure if we should have others as tags are generally a general concept. But these are like big identifiers...
Thoughts?
Maybe we'd change the 'experimental' markdown field to tags or something and have it be more freeform? Not sure what the best approach here is... https://github.com/search?q=repo%3ACommunityToolkit%2FTooling-Windows-Submodule%20experimental&type=code
Steps to reproduce
Expected behavior
Better organization of Home Page
Screenshots
No response
Code Platform
Windows Build Number
Other Windows Build number
No response
App minimum and target SDK version
Other SDK version
No response
Visual Studio Version
No response
Visual Studio Build Number
No response
Device form factor
No response
Additional context
No response
Help us help you
No, I'm unable to contribute a solution.
The text was updated successfully, but these errors were encountered: