Follow up for #1940590: META: Write a multipage multilingual tour.
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. There should be individual tours for certain multilingual features and these can be linked together to make a multipage tour later via #1940590: META: Write a multipage multilingual tour.
Proposed resolution
Write individual tours for the language switcher block only.
Remaining tasks
Create tour yml files for the language switcher block tour:
- Block config page (admin/structure/block)
- Place block
- Place language switcher block (subpage = admin/structure/block/list/block_plugin_ui%253A[theme]/add)
- Configure language switcher block (subpage = admin/structure/block/add/language_block%253Alanguage_content/[theme])
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.
#1940590: META: Write a multipage multilingual tour
Comment | File | Size | Author |
---|---|---|---|
#14 | placeblock.jpg | 224.05 KB | balagan |
#8 | drupal8.language-module-tours-2017501.patch | 2.58 KB | c-c-m |
Comments
Comment #1
Kristen PolComment #1.0
Kristen PolUpdated issue summary.
Comment #2
Kristen PolThis one is a bit more challenging as it depends on the theme. I won't mark Novice here.
Each page needs its own "tour". We don't need to worry about tying the tours on different pages together yet.
The yml files are pretty simple. You just need to know how to inspect the HTML to know what CSS tags to target. See:
https://drupal.org/node/1921152#tour-tips-tech-note
Comment #2.0
Kristen PolUpdated issue summary.
Comment #3
Kristen PolActually, I don't think this one is do-able as is (on the admin/structure/block) because you can only have one tour per page (it would be great to have multiple tours per page!). So... really, info about the block will need to be surfaced on the other tours.
Comment #4
nick_schuch CreditAttribution: nick_schuch commentedMultiple tours per page is do-able. We have test coverage for this. Have you run into issues with this?
Comment #5
Kristen PolOh! I guess I just assumed it didn't work :) Not sure when I can get to testing though...
Comment #6
Kristen PolI'll un-postpone per #4.
Comment #7
c-c-m CreditAttribution: c-c-m commentedDespite being a complete novice, I will try to help on this issue. Assigning to me.
Comment #8
c-c-m CreditAttribution: c-c-m commentedHere's a first attempt.
I didn't know how to handle urls', since they depend on the active theme. Is there any token such as [site:url] I can use? (I haven't found anything on Tour API).
Comment #9
Kristen PolYes, [site:url] works! It just got committed recently:
#2017471-25: Multilingual tour for language section
:)
Thanks!
Comment #10
c-c-m CreditAttribution: c-c-m commentedHello Kirsten, do you know if there's a custom token such as [site:theme] I can use in order to create links like
admin/structure/block/list/block_plugin_ui%253A[theme]/add
admin/structure/block/add/language_block%253Alanguage_content/[theme]
Thank you
Comment #11
Kristen Pol@c-c-m - I don't see a token with that in the code base but it shouldn't be hard to make one... just not sure where it would go... maybe in system module? I'm not sure it would get in at this late date though... hmm...
Comment #12
Kristen PolI searched and don't see an issue for this. If you want to open an issue, I don't think the patch would be difficult unless I'm not understanding something fundamental. Something like adding the following to
system.tokens.inc
:Comment #13
nick_schuch CreditAttribution: nick_schuch commentedComment #13.0
nick_schuch CreditAttribution: nick_schuch commentedUpdated issue summary.
Comment #14
balagan CreditAttribution: balagan commentedSuggestion: Adding the "Language Switcher" block
suggestion: ..."arrange blocks into specific regions of a theme.
The "Language Switcher block" allows users to quickly switch the language of the site."...
The rest of the sentence suggests that we are stupid and evil, and we are not enabling a useful thing for the user by default. I would just stick to the following:
"This is not enabled by default, and unless it is added, cannot be seen on the page."
Suggestion: "In order to see the "Language Switcher" block"...
Suggestion: "After having clicked on the "Place blocks" button a new ..."
There is definately a mistake in the rest of the sentence: "Under one the existing regions"
Suggestion: "under one of the existing regions."
I would also change "Place block"''s page to something like:
""Place block" panel,..."
Also for continuing the link should be saying: Placing the "Language Switcher" block, this is what it is called. There is also an occurence of 'Language Selector' block, that should be changed.
I have enclosed a screenshot of the Language Switcher and the Place block panel.
Comment #15
mgiffordComment #16
Gábor HojtsyPostponing due to #1940590: META: Write a multipage multilingual tour.
Comment #17
mgiffordComment #18
mgiffordComment #31
quietone CreditAttribution: quietone as a volunteer commentedThis 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.