You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I miss a feature for website plugins. When I implemented Etherpad and DokuWiki, I felt that I should be able to give the user additional hints on how to proceed once the plugin is installed. I also played with GitWeb.. there, for example, the user should be able to easily access information on how and where to set up the git repository, and not having to consult other docs or even to search the web for a guideline.
For this it would be nice to have a help symbol in the row of symbols under the website, maybe even as the first symbol. On click it would open an overlay, just like the config button.
The layout could be provided as help.xml in the layout folder. If help.xml is found, the help button is shown, otherwise not.
What do you think? If you like it, I could try to implement this.
The text was updated successfully, but these errors were encountered:
The scope of this issue has been expanded to include app-wide help dialogs. This should use a dedicated Ember component that loads a partial depending on the active route.
I miss a feature for website plugins. When I implemented Etherpad and DokuWiki, I felt that I should be able to give the user additional hints on how to proceed once the plugin is installed. I also played with GitWeb.. there, for example, the user should be able to easily access information on how and where to set up the git repository, and not having to consult other docs or even to search the web for a guideline.
For this it would be nice to have a help symbol in the row of symbols under the website, maybe even as the first symbol. On click it would open an overlay, just like the config button.
The layout could be provided as help.xml in the layout folder. If help.xml is found, the help button is shown, otherwise not.
What do you think? If you like it, I could try to implement this.
The text was updated successfully, but these errors were encountered: