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
Add documentation for Help menu #7634
Comments
Good idea.
Since we tweetdeck now requires paid subscription, we don't have access to it anymore. So, it makes sense to officially stop using twitter. To make this clear, we could ask Isaiah to make a final post where we describe the rationale. |
@ihnorton are you around to comment on the Twitter/X issue above? |
For me, removing tweetdeck was just the last straw (rename to X, practically removing moderation, making people pay for features that none of the alternative services ask money for, aim to become a universal app for everything, etc.) that made me not want to contribute to twitter anymore. I've also found that somehow there are much more meaningful discussions and larger viewer counts on linkedin. I find twitter has become more suitable for political debates and linkedin better for professional conversations. |
Adding a last post on "twitter" to retrieve and phase out our twitter activities seems sensible. This last post would be referencing either this issue or a discourse post with relevant context and details. |
Is your feature request related to a problem? Please describe.
When helping users on the forum we don't have documentation to point to about the Help menu.
Describe the solution you'd like
Add description of the items in the Help menu, ideally here: https://slicer.readthedocs.io/en/latest/user_guide/user_interface.html#application-menu
Other menus are described but not Help. As a side note we should remove Twitter since it's not used much as far as I know.
Describe alternatives you've considered
We might also want to extend some of our help text in the documentation so users don't need to ask on the forum for some simpler questions (probably there are lots of people with the same questions who never ask on the forum).
Additional context
The text was updated successfully, but these errors were encountered: