• Initially, the new users are welcomed by the "Basic Interface Overview" tour, which currently is called "Homepage Tour"
• At the last step of the tour, users are encouraged to visit the "Documentation" link, which targets the Features page
• One change would be that, after the users finish the first tour, if they need more guidance they could head off to more tours

Before

After

• Help app will provide a dedicated section to Tours
• In order to limit the number of options we present and don't overwhelm the user, we compacted the "Features" entry to only 4 items
  • The "Page Editing" example link will be included as part of a tour
  • Merged the "Version Control" into the first section
  • Added a link that will showcase all the "Features"
  • Removed the "Import/Export" and "Content Organization" and rely on "more"

Before

After

• Tour.WebHome is the homepage for the Tour app and is hidden by default since it's considered a technical application
• We don't plan to reuse the Tour.WebHome, but to create a dedicated entry in the Help space for Tours
• Tour Application will be independent of Help, so people could remove the Help content, but still be able to create their own tours

Before

After

• A list with all the Tours will be available, but without the technical columns
• We also promote the suggested tours for beginners
• Help Application will have a dependency to the Tour Application
• Click on a tour name will automatically launch the tour

Before

-

After

• "Edit a page" could be listed as a separate tour or integrated with "Create a page" tour

Problems encountered so far: 

• TOUR-59: currently we can have only 1 tour per page. Ideally most of the tours should start on the Main.WebHome, since that's the wiki's Home. The current limitation ask that each tour has it's own starting page. That's why the tours are created on various pages on Sandbox;
• TOUR-57: we would need this Bootstrap Tour parameter in order to let the user click on the content menu "Create" button and continue the tour in the new location. Currently if he clicks on "Create" the tour ends, because the tour is not registered to the page. Another example: on the same page, in order to press on the "Drawer" and to highlight the "Administration" link;
• TOUR-62: on the Create step we would need to validate that the user entered a page title;
• TOUR-61: since the user entered a personalised page title we need to know what that it is in order to continue the tour at that location;
• Tours content can be improved, I mostly focused on what we can do technically;