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
It's been a couple of years since the initial addition of IntroJS onboarding guide in Hajk (see #398).
This feature has always been behind an experimental flag - for a good reason. I had a feeling that the implementation has its' limitations: no ability to control the guide via Admin UI, no per-map setting - those are only two of many inconveniences.
Halmstad has taken a closer look into this and our focus group proposes the following changes:
We must distinguish between features of Hajk itself and the contents of current map. Hajk features are best presented within IntroJS, but a About this map window (part of the Information plugin currently) is also very useful - perhaps even more so than showing users where the search bar is located. Therefore we think that the rendering order should be changed:
If Information is to be shown, show it first. Let us present the map's contents.
At the end of the Information window there should be an option that allows user to start a guided tour (IntroJS). If user clicks this, the Information window is closed and IntroJS does its' job, pretty much as it does currently.
The IntroJS tool (which should either be transformed into a plugin or made a part of core) is available as a Control button, perhaps using the question mark as an icon. This way the user has an option to always start the guided tour.
The IntroJS starting window could display more information, something that let's user know that "you will now be taken on a guided tour of this web map solution".
We probably shouldn't start with IntroJS visible ever (even if it can remain an Admin UI setting). Our focus group has concluded that if we should start with something visible in front of the map it should be the Information window with clear and concise text introducing the user to the map's contents.
One aspect that needs to be taken into consideration here is when and how the #284 Cookie notice should be shown. We can't have any race conditions here. Hence, this must be done in coordination with #939.
The text was updated successfully, but these errors were encountered:
- Moved the settings for Introduction from appConfig to mapConfig.
- Removed the 'experimental' flag on those properties.
- Added basic validation of supplied 'steps', with a fallback to defaults if parsing fails.
It's been a couple of years since the initial addition of IntroJS onboarding guide in Hajk (see #398).
This feature has always been behind an experimental flag - for a good reason. I had a feeling that the implementation has its' limitations: no ability to control the guide via Admin UI, no per-map setting - those are only two of many inconveniences.
Halmstad has taken a closer look into this and our focus group proposes the following changes:
One aspect that needs to be taken into consideration here is when and how the #284 Cookie notice should be shown. We can't have any race conditions here. Hence, this must be done in coordination with #939.
The text was updated successfully, but these errors were encountered: