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
@critzo@georgiamoon The functionality we are using to allow us the setup wizard path also encapsulates the structure of the pages from the dispatcher function we use for menu's and the page objects that it contains. As such, creating click-able menu's for moving between the pages will be infeasible for R1. I have put a back button on every page, as that accessibility is available. I think I have a fix for R1.1 that should get us full functionality. But, it is too theoretical to put in place before R1. If youl would like we can put a page(x) of (y) on every page to show progress through the setup wizard, but the ability to move back and forward multiple pages is currently not possible.
@elationfoundation @georgiamoon I think that it's fine to move this to the 1.1 release to give proper time for testing. Adding a (page x of y) to each page seems appropriate, as well as looking at the language again on the first setup wizard page to make sure it's clear that users will need to go through all steps to complete setup.
@elationfoundation @georgiamoon S2E and I just discussed this more. We think that during the setup wizard we'll show the left menu, but only the items in setup wizard. This will show the user where they're at in the setup process but won't be clickable. The content area will also have forward, back and pagination info (x of y).
side menu's should be greyed out (and un-likable) during the quickstart process
The text was updated successfully, but these errors were encountered: