-
Notifications
You must be signed in to change notification settings - Fork 0
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
Organisation of help pages #600
Comments
Hovering would exclude those who cannot do so, whether through disability or a broken pointing device. |
I agree: a proper sub-menu would be better, but I don't know how straightforward that would be to implement. |
Reviewing the pages on the beta site, I see that some links from the FAQ page take you out of the BMD2 site and into the generic FUG site, without flagging that they are doing so. Given the similarity in layout of the help pages on the two sites, this can cause confusion. (It certainly confused me!) Links would be OK if flagged as being to an external site. |
I have attempted to document all the links between help pages to pages within the FreeBMD2 site: https://drive.google.com/drive/u/1/folders/1qcuyMN3_jHoXQuDPBdGlSNNWHTJe9m2C. Apologies for the scruffy Paint-generated diagram ... also for the fact that the URL doesn't work (thanks, Google Docs!). It's the file BMD2 Help Pages structure.png in the list. |
The main menu has About and Help, separated by other headings (Volunteer and Logout/Member). There are other help pages, but they can only be accessed if you happen to click on the 'right' link. There is no place you can go to to get a sense of all the help that is available. Also, I would question the utility of having two routes down into [different] help on the main menu, randomly separated from each other. I would suggest, as a minimum, a 'help elsewhere' contents list at the bottom of the main Help page with links to all the help pages. Ideally, the Help Menu item would also have sub-menu options appearing below it when hovered over.
We also need to document exactly what help pages we plan to produce for MVP.
The text was updated successfully, but these errors were encountered: