Part of #1921152: META: Start providing tour tips for other core modules.

Problem/Motivation

Multilingual configuration is spread throughout the site. It would be useful to have a tour to help users know how to configure the site for multilingual.

Proposed resolution

Write individual tours for each core multilingual module feature. Provide a multipage tour to allow going from one tour to another. See:

#1942576: Tour tips to be able to link to other pages and start tour's automatically.

Remaining tasks

Create tour yml files for the following. Some features can be combined into the same tour.

These should be included in the multipage tour:

These should NOT be included in the tour since the defaults are sane (or maybe there can be advanced tours?):

  • Detection and selection page (admin/config/regional/language/detection)
    • Enable/disable new detection and selection settings
    • Reorder detection and selection settings
    • Configure URL setting (subpage = admin/config/regional/language/detection/url)
    • Configure Session setting (subpage = admin/config/regional/language/detection/session)
    • Configure Browser setting (subpage = admin/config/regional/language/detection/browser)
    • Configure Selected language setting (subpage = admin/config/regional/language/detection/selected)
  • There will be other tours if the Configuration Translation module lands:

    #1952394: Add configuration translation user interface module in core

    User interface changes

    New tours

    API changes

    None

    Technical pointers when creating tour tips

    See: https://drupal.org/node/1921152#tour-tips-tech-note for tech notes on making tour tips.

    Related issues

    #1921152: META: Start providing tour tips for other core modules.
    #1942576: Tour tips to be able to link to other pages and start tour's automatically.

    Comments

    Kristen Pol’s picture

    Issue tags: +D8MI

    Adding tags.

    Gábor Hojtsy’s picture

    Title: Write tour integration for locale.module » Write a multilingual tour
    Issue tags: +language-base

    Reading the META issue, there are no tour issues for each multilingual module. I think we should treat this as one system. Retitled.

    Also Kristen Pol closed down #2007632: Create multilingual install profile. as a duplicate of this one FYI.

    Kristen Pol’s picture

    Agreed... one tour to rule all multilingual!

    klonos’s picture

    This would be a great deal in cutting down on all the pogo-sticking site builders have to go through in order to configure the right settings in order to create a multilingual site. I believe that this issue is related/helpful: #1942576: Tour tips to be able to link to other pages and start tour's automatically.

    I realize that #2007632: Create multilingual install profile. was closed and getting this fixed will be easier/faster, but I would like to take the opportunity to shamelessly "promote" #2010008: Multilingual site installation, Step #1: Allow selecting more than one language during installation. because I'd really hate to see it be pushed to D9.

    klonos’s picture

    Issue summary: View changes

    Updated issue summary.

    Kristen Pol’s picture

    Issue summary: View changes

    Updated issue summary.

    Kristen Pol’s picture

    Issue summary: View changes

    Updated issue summary.

    Kristen Pol’s picture

    I have added a lot of detail into the issue summary to outline what could be in the tours. These can be started even though the multipage tour patch hasn't landed yet. There is still a lot of work to get a tour per page.

    YesCT’s picture

    I dont think a tour needs to show *everything*
    For example, the detection and selection page probably does not need a tour, as we are expecting 80% will be fine with the defaults.

    Kristen Pol’s picture

    Agreed. I'll update the issue summary with what will be in the tour and what *won't* be in the tour. :)

    Kristen Pol’s picture

    Issue summary: View changes

    Updated issue summary.

    Kristen Pol’s picture

    Title: Write a multilingual tour » Write a multipage multilingual tour

    Will start adding sub-issues for each section for the tour. First one is:

    #2017471: Multilingual tour for language section

    Kristen Pol’s picture

    Issue summary: View changes

    Updated issue summary.

    Kristen Pol’s picture

    Issue summary: View changes

    Updated issue summary.

    Kristen Pol’s picture

    Issue summary: View changes

    Updated issue summary.

    Kristen Pol’s picture

    Issue summary: View changes

    Updated issue summary.

    Kristen Pol’s picture

    Issue summary: View changes

    Updated issue summary.

    Kristen Pol’s picture

    Issue summary: View changes

    Updated issue summary.

    Kristen Pol’s picture

    Issue summary: View changes

    Updated issue summary.

    Kristen Pol’s picture

    Issue summary: View changes

    Updated issue summary.

    Kristen Pol’s picture

    Kristen Pol’s picture

    Issue summary: View changes

    Updated issue summary.

    Gábor Hojtsy’s picture

    Title: Write a multipage multilingual tour » META: Write a multipage multilingual tour

    Retitled to expose this is a META.

    Gábor Hojtsy’s picture

    Issue summary: View changes

    Updated issue summary.

    David Latapie’s picture

    I saw a "Guided Tour" on Drupal 8 beta 6. Is it related?

    webchick’s picture

    Status: Active » Postponed

    This one seems like a good thing to do, but postponed on #1921152-109: META: Start providing tour tips for other core modules. for now.

    mgifford’s picture

    Version: 8.0.x-dev » 8.1.x-dev

    Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

    Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

    Version: 8.1.x-dev » 8.2.x-dev

    Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

    Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

    Version: 8.2.x-dev » 8.3.x-dev

    Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

    Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

    Version: 8.3.x-dev » 8.4.x-dev

    Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

    Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

    Version: 8.4.x-dev » 8.5.x-dev

    Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

    Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

    Version: 8.5.x-dev » 8.6.x-dev

    Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

    Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

    Version: 8.6.x-dev » 8.8.x-dev

    Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

    Version: 8.8.x-dev » 8.9.x-dev

    Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

    Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

    Version: 8.9.x-dev » 9.2.x-dev

    Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

    Version: 9.2.x-dev » 9.3.x-dev

    Version: 9.3.x-dev » 9.4.x-dev

    Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

    Version: 9.4.x-dev » 9.5.x-dev

    Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

    quietone’s picture

    Version: 9.5.x-dev » 11.x-dev
    Component: locale.module » tour.module

    This tour module is being deprecated, see #3336033: [Meta] Tasks to deprecate Tour module. It will be removed from core and moved to a contrib project, #3376099: [11.x] [Meta] Tasks to remove Tour.

    This is now Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.