Update about page for release

[nacin]

• Images and videos need final versions and dimensions.

• The videos need to be converted to a few other formats.

• The about page's images and videos need to be transferred to the CDN.

• Add the release video to the about page for English installs.

• The playlist underscore templates no longer need to be included.

• We need a new "Release Lead" string for the credits page.

[helen]

Videos are converted but may get resized again. We also need to pass an option to MediaElement to allow both videos to play at once, which wonderboymusic has provided me with.

[nacin]

In 29700:

Add 'Release Lead' string to credits. see #29494.

[SergeyBiryukov]

Related: comment:9:ticket:29243

[helen]

Replying to SergeyBiryukov:

Related: comment:9:ticket:29243

Not an issue in final media.

[helen]

Media has been transferred to CDN. I've got the patch for this locally - don't want to spoil anything early :)

[helen]

#29502 was marked as a duplicate.

[helen]

In 29706:

Final about page for 4.0. Enjoy the videos!

props ryelle, melchoyce, smashcut, wonderboymusic, helen.
fixes #29494.

[helen]

In 29708:

About: Make sure the images are properly responsive.

props ocean90.
see #29494.

[knutsp]

Why is the video only available for en_US? By design? Small thing, but kind of disappointing.

[nacin]

Replying to knutsp:

Why is the video only available for en_US? By design? Small thing, but kind of disappointing.

Yes, by design. I understand it's disappointing but I think it's a bad UX to show an English-only video to non-English speakers.

We did the same thing in 3.9, FWIW, and I didn't hear any feedback like this.

helen and I like to make this better in the future, like with subtitles that ship with core.

[knutsp]

I tend to disagree. Because my native language is not English, I'm not a "non-English" speaker.

Many people with English as their native language just speak one language, because that may be all that is needed in the world. Many people who are not native English speakers, on the other hand, are multilingual, or at least understand English quite well.

In Norway, even children at age 8 understand and speak (some) English.

Showing just an image when a video is expected, is also bad UX. Ticket will follow later.

[nacin]

In Norway, yes, a large percentage of people speak English. Same as the Netherlands, Israel, Denmark, Sweden, and many other countries. I agree it is not ideal for them to not see the video. I think it is better to not show a video in places where they may be able to understand it than to show a video in places where they cannot possibly expect to understand it, but I have no data to back it up. I just think showing them a video not in a language they can understand would feel unpolished, lame, and American-centric.

I think our release videos are amazing and I want them shared far and wide. I've half-jokingly said numerous times that I help make WordPress mostly to see what Michael Pick turns them into, and I've been intimately involved in helping to produce the last three he's done for us (4.0, 3.9, 3.5).

I would like to make this better for 4.1. I think continuing the discussion here is actually fine, for the moment, at least until we have a better idea of what's next.

Also, for 4.0.1, maybe we can make the image link to wordpress.tv (I *nearly* did this) and we can see if anyone wants to create subtitles in their own language, too.

FWIW: You expect a video because you know it exists. The vast, vast, vast majority of users who see that image have no idea a video is expected and are not experiencing a bad UX.

[knutsp]

Thank you for replying so thoroughly to this, Nacin.

I mostly agree with you. But what ideally could have been done here is to have a simple filter. I just wanted to be able to let my (Norwegian) clients view the video without hacking a core file.

The "American-centric" part of this issue is, in my view, assuming most "non-English" speakers understand their native language only. Many Americans, and British, are in that category.

I'm sure we will find a solution that makes everybody happy, for the next release, it be 4.0.1, 4.1 or later. And I don't want to sound disappointed with 4.0. This is really minor ting, but it raises some quite interesting aspects when it comes to localization, and the fact that most of the WordPress developers being Americans, in their way of thinking and viewing the world. The attitude is excellent, at most, but understanding may lack, sometimes.

And, hmm, installing an untranslated plugin or theme is not considered bad UX? But it's a problem I face daily. Nobody would dare remove that option.

Main thing, WordPress 4.0 is a great step forwards when it comes to internationalization (language packs and language selection on install), many thanks to you, and the other contributing people. I'm very grateful. 4.0 is great!

[helen]

Replying to knutsp:

I mostly agree with you. But what ideally could have been done here is to have a simple filter. I just wanted to be able to let my (Norwegian) clients view the video without hacking a core file.

That's an interesting idea - if you do want a workaround in the meantime, since video playback typically requires JS and/or Flash, you could use JS to swap it into place and MediaElement for playback.

The "American-centric" part of this issue is, in my view, assuming most "non-English" speakers understand their native language only. Many Americans, and British, are in that category.

I agreed with keeping the video en_* only this time, and it was not based on that assumption. Being American does not equate to being a non-polyglot - we are, after all, a country composed almost entirely of immigrants and their descendants. My view is this: polyglots who count English among their languages who choose to use WordPress in another language are making the statement that they prefer their software to be in that language, and so long as we're still exploring the options for captioning (believe me, I did a fair bit of looking there), keeping something that is essentially untranslated when we make such an effort to translate everything else is inconsiderate. We've gone back and forth about the other visuals being in English so many times already. And before you jump on me for my American view, this is a view derived from my family (including my married family), who are almost all non-English speakers, and the significant time I've spent observing and talking to them about their computing habits.

As nacin noted - you know the video is there for English installs. Most people don't. The design needed balance, and the cover image kept it for when the video isn't shown. It's also beautiful work - would be a shame to lose having it at all. Linking it would probably have been a good idea, though :) Hope people are translating captions for it.

And, hmm, installing an untranslated plugin or theme is not considered bad UX? But it's a problem I face daily. Nobody would dare remove that option.

Nobody said that wasn't bad UX. This was something I wanted us to accomplish in 4.0, quite badly - that is, to default to showing plugins and themes in your language only (with the ability to see all, should you choose to). I even optimistically included a string on the about page originally: #29391.