-
Notifications
You must be signed in to change notification settings - Fork 39
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
Improve doc coverage of GUI features #180
Comments
See also #93 |
Hi there, maybe not completly related to this but just in case, I was checking and running
Can give you access to a coverage report (running Example generated report
Also, running |
Very cool @dalthviz! I wonder if we should add a section to the docs like "development tips and tricks" to compile this sort of command. This wouldn't have to be very organised or anything, just an FAQ-style page, which would contain little tidbits like this one that our developers might like to share. |
Currently our narrative docs are task oriented, which is great, but they are not aiming to provide exhaustive coverage of all the things you can do in the viewer from the GUI. This would be the "reference" section of the diataxis section — currently we have reserved that for the API docs, but this leaves GUI-primary users in a lurch, particularly until we achieve GUI-API feature parity. It would be good to systematically cover everything we can adjust in the GUI somehow. (Probably good to start with napari/napari#5959.)
The text was updated successfully, but these errors were encountered: