-
Notifications
You must be signed in to change notification settings - Fork 203
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
Community feedback request regarding docs discoverability #420
Comments
Ok, the JavaScript roadmap is very cool! Coming in cold with most things regarding actual application building, I have been very confused in a lot of things, including exactly how Avalonia actually works. I know there is the “how it works” page on the main site and the “Architecture Overview” diagram but it is still not clear. I watched the 2023 (and 2022 actually) .Net Conf video that had a graphic that compared Avalonia to Maui. That block diagram was actually helpful. |
Looking for feedback from the community pertaining to their experience with finding relevant docs, assuming they exist.
There are a few ways to address discoverability that I'm aware of:
An example of a roadmap would be similar to this JavaScript roadmap to give a high-level overview of what's available in XAML and linked to existing relevant information in docs. I don't know how to create one though without building it from scratch. Controls would have their own roadmap or at least a centralized table that can be sorted alphabetically and categorically with use cases.
The text was updated successfully, but these errors were encountered: