-
-
Notifications
You must be signed in to change notification settings - Fork 357
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 a 'help/information' link for all quests #94
Comments
I do not plan to add this because this app does not expose the user to the "raw" OSM tags, so linking a wiki site that talks about these tags is counter-productive. Rather, I want to design the UI in a way that it is self-explanatory. Where it is unavoidable, I add short explanation texts (i.e. in the "add road name" form). Especially in the case of the building levels by the way, it would only confuse the user more (because the app is not asking for the values as they are input via the tags). What I would probably eventually add, is a small info button for each quest (type), that pops up a dialog that explains in short words:
If this is about what you meant, I can leave this issue open, but a wiki link I would definitely not add. |
Yeah, that's more the direction I was heading - arbitrary link - with the osm wiki documentation as a fallback of last resort Check out https://www.openstreetmap.org/user/JanBohmMSF/diary/40072 as a 'how to' guide and it has a built in Q&A section as more of where I was going with it. Obviously, that's aimed at tasking manager and is complex, compared to what the design goal is here. |
Sample explainer text to fix #89 #66 |
No, thank you. As said, I will rather make the quests self-explanatory than to add "guides". |
Similar:
ID does a pretty good job of this by adding an "Info" link into the UI:
For an individual quest, it could be useful to add a link into the UI pointing at the relevant openstreetmap wiki page.
IE:
Alternatively, pointing to a specific quest set of documentation (similar to what is done with some HOT tasks) would also be useful.
hotosm/osm-tasking-manager2#979 talks about a similar usability need.
This could likely be represented in the UI in a consistent icon/location on each form.
The text was updated successfully, but these errors were encountered: