Multilingual tour for content translation settings

Tour needs tests since we now have #2028535

I'm working on this

Maybe you can use this as a starting point.

Updated issue summary.

I'm uploading a file that may be used for a tour for configuration of the Content Translation module. To use this file, remove the _.txt extension and install it using these instructions from Technical pointers when creating tour tips:

Add the yml file directly under your active config directory which looks something like:
sites/default/files/config_[gobbly-de-gook]/active

This tour file is a bit unusual, due to limitations with the current state of the Tour Module and Joyride. As a workaround, it asks the user to perform several actions in order to continue the tour and see parts of webpages. Here are the issues I encountered:

1. The location of a Joyride tip is either an HTML id or the first instance of a class on the page. Thus, you sometimes cannot put the tip exactly where you would like to. (It's surprising that a jQuery tool, with jQuery's excellent selection capabilities, has this limitation—I wonder if it is possible to improve upon this.)
2. If part of the page is hidden by default, a Joyride tip within that area will not open up that part of the page. For example, on the 'Extend' page, the user needs to click on the text in the Description column in order to see the Help, Permissions and Configure links. Thus, in this tour file, I instruct the user where to click in order to see the Configure link.
3. You may alter the text of a button, but this cannot contain a link. Joyride has options data-button and data-text which may be used to change the text on the button. However, a link does not work here, which would be useful in the same example for clicking the Configure button, which takes you to a new page. The attached file tries to skirt this problem by embedding a link in the text, instructing the user to click here to go to a new page.
4. Following the previous click here action, the same tip box still exists on the new page, which would be confusing. To get around this, the attached file asks the user to click here to go to the Configure / Content language settings page, and then click next. Hopefully this informs the user that the click takes them to a new page, where they will still need to click the next button to continue. It would be better if the next Tour tip occurred, though.
5. The data-options parameter does not seem to work. (See Joyride Demo and Joyride Step 5: Options and Upgrades). This would be useful for among other things placing the tip box. If the HTML element the tip is attached to is too large, the tip box will be unseen under the bottom of the screen. Other times, the tip box obscures the part of the web page you want the user to see. Being able to place the tip box to the left, right, or top might help here.

Uploaded file for comment #7.

Could we add info in the tour on "Content type translation" explaining how to translate menu entries related to this content type?

I am working on contributing a patch for this issue. The file attached in comment #8 needs to be updated a bit because of how things have evolved since it was created. I am re-working this and will provide a patch for this once I get it working.

I have taken the file that was posted in #8 by Mark_L6n and updated it to the new structure/architecture of the D8 site.

Relavant change notes are:
- This is actually a patch to the language core module
- The IDs as well as the path targeting structure has been updated to route_name equivalents (url path is no longer used)
- The tour is enabled as an installation item when the "language" module is enabled. This allows the 2 tour steps to be added to the Module enable page to add instruction to enabling and configuring the "content_translation" module
- The routes are actually declared by the language module (not the content_translation module) so making it part of the language module makes more sense

* I am a developer so I cleaned up the text a bit but left the content as it was previously created. Let me know if further content changes should be done.

Silly Git New Line character error. Adding a patch with a new line :)

These are all truncated, and hence missing the closing '

+++ b/core/modules/language/config/install/tour.tour.language.yml
@@ -0,0 +1,49 @@
+    body: 'Specify the parts of the website that may be translated, and default languages for them.<br>N
...
+    body: 'Relevant links and information are displayed here.<br>To continue tour, click <a href="/admin
...
+    body: '<em>Content Entities</em> are configured here for translation. <em>Content Entities</em> typi
...
+    body: 'Individual Content Types may be configured for translation.<br>Check <em>Article</em> and cli
...
+    body: 'The individual fields of a content entity may be separately configured.<br>Even sub-field com

These

Silly error. Didn't realize my patch was being truncated. Uploading a complete patch :)

I think we need two separate tours here - one generic for before the module is enabled, explaining what the various translation modules do.

The second tour can be attached to the content translation module and describe the page at admin/config/regional/content-language

I also think it needs just a bit more clarification around the interaction required to use this tour properly. If you don't check the Content option, the tour doesn't make sense. Might have a think about how to handle that.

Just one last thing, not sure whether it is a bug but the third tip appears at the bottom of the page and you can't see it unless you scroll down. Is it possible to anchor it to something a little higher on the page?

Tours are hard :(

I think is not a good idea to have a multilingual tour on the modules list (or Extend) page.
I confirmed that is not possible to have two sets of tips on the same page so this tour cannot take over that page to another future tour that explains the functionality of the Extend page.

I don't know how to handle the fact that the "Content language" page is provided by the language module and extended by the content translation module. You need tips for the language module and more tips once you enable "Content translation" module. As I said above there's is no way we can have two sets of tips.
I'm thinking that maybe the configuration provided in a yaml can be extended by another yaml and add more tips to that tour

I think the tour can be made more generic and don't rely on the standard installation profile. Not talking about Articles will make this tour suitable for any drupal installation that doesn't have that content type installed.

I created an issue to have the possibility to be more flexible with the tours
#2443713: Provide a way to have different set of tour tips for the same page

I also think it needs just a bit more clarification around the interaction required to use this tour properly. If you don't check the Content option, the tour doesn't make sense. Might have a think about how to handle that.

The tour is telling you to check it. I think is reasonable to make the following tips depend on that user action.

Apart from my comments and issues that need to be resolved to make this tour perfect and awesome I think this can go forward by providing a tour on the content translation module explaining everything that we can in the content translation settings page. It can be later splitted into more tours.

Here's a patch. There's no interdiff because I only took some strings from the previous tour.

As I commented on the other issue, you can use a tour tips alter to add a few items to a tour on an existing page, when a new module is enabled.

#1940590: META: Write a multipage multilingual tour is postponed on lack of directional decisions, so this one should be postponed too AFAIS.

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.