This is a basic step required for enabling multilanguage installations. There's been quite some discussion in #1917212: Add checkbox in installer to enable content translation (if in foreign language) and now in #2007632: Create multilingual install profile..

Creating a multilingual installation profile that enables the right modules and perhaps tweaks other things here and there is a good thing UX-wise (so that site builders don't go pogo-sticking after installation), but we first and foremost need to have a multilanguage site in place to begin with.

So, what needs to be changed is to allow the user to select multiple languages during installation. Having the drop-down language selection menu be a multi-select widget instead would do it, but having to ctrl+click or shift-click is not good UX. What if we kept the drop-down as is but added a "Add another language" button? This would trigger a multilanguage site installation with some additional steps (TBD).

Comments

Kristen Pol’s picture

I like the idea of "add another language". I mentioned the same thing to Gábor at DCPDX and he said that his concern (and maybe that of others?) was that if you let them choose multiple languages via the installer that the developer would assume they need to go back to the installer to add more languages.

I think this could be handled with a simple and clear message that additional languages can be added later... along the lines of:

Additional languages can be enabled now or at a later time using the site's language configuration page.
Kristen Pol’s picture

Adding tags.

Bojhan’s picture

Issue tags: +installer, +D8MI

We already did a design for this in the original selector, it was never implemented.

klonos’s picture

Well, perhaps we should put some effort in implementing it after all ;)

...as I said in the other issue, some might consider the pogo-sticking site builders have to go through the various admin screens a UX bug.

Kristen Pol’s picture

@Bojhan - was it not implemented because it was deemed not good UX? Or just because it the person doing the patch just went the simple route?

Kristen Pol’s picture

Here's some of the original discussion on "add another language" by @klonos et al:

#1917212-11: Add checkbox in installer to enable content translation (if in foreign language)

I couldn't find anything in #1260716: Improve language onboarding user experience about "add another language" type feature (there was talk about multiple select but that is different UX).

YesCT’s picture

just making a nice link to the comment... can be done with [ # NNNNNN - CC ]

#1917212-11: Add checkbox in installer to enable content translation (if in foreign language)

--

I thought we might already have another issue for "add another language" in the installer. Do we?

Kristen Pol’s picture

Thanks for the tip! I'll try to remember that... is there a dreditor helper for it? It only seems to tab to the full issue.

YesCT’s picture

no dreditor autocomplete... just built into d.o. it's documented under the input format collapsed field set, under "more information about formatting options" which links to https://drupal.org/filter/tips

Kristen Pol’s picture

Thanks!

Pancho’s picture

Our thoughts and discussions on #1988112: Add "Administration pages language" setting to "Configure site" page in installer might also be interesting for this decision.

Kristen Pol’s picture

This issue has been quiet... doesn't look like there is much interest in an "add another language" option during installation. :/ Guess that would be nice for a contrib multilingual install profile.

klonos’s picture

Being like a week away from freeze it's more likely that the people that can make things happen are busy getting really important issues fixed first. I agree that there might not be enough time, but I wouldn't jump into conclusions about interest.

Kristen Pol’s picture

True... could be interest but they are distracted by other things! :)

Pancho’s picture

Yes, we're a week from API freeze, while tasks and even some features may still flow in later, so that's defeinitely the reason for people caring about everything that is API-related... This certainly doesn't mean we won't make progress with UI-related aspects at a slightly later point.

David Latapie’s picture

Issue summary: View changes

This would be useful for Canadian, Belgian, Norwegian... governmental websites

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.