About WordPress page for 3.4

[ocean90]

We shouldn't forget /wp-admin/about.php and should start to fill it with new information.

What's new?

• Theme Customizer
• HTML in captions
• Responsive/Mobile support
• XMLRCP API

(Feel free to continue.)

[pavelevap]

And what about old information (about 3.3)? They will be removed or there will be any new section (tab) "History"? What about people upgrading from 3.2 to 3.4? They should see news related to 3.3 and 3.4?

[jane]

Yes, we need to update it before RC1, since that is string freeze. We'll also update Credits, but that happens on .org.

I think we agreed last cycle that the only time a 'history' would come into play was within a major release cycle (3.3.1 and 3.3, for example).

@ocean90: The tag I make sure to check is ux-feedback (it's in the dropdown menu), vs ui-feedback.

[lightningspirit]

A proposed model to handle history

[lightningspirit]

The new page history.php

[ryan]

In [20720]:

Dummy test for about.php. see #20423

[scribu]

Weren't there more i18n changes besides the string loading?

[pavelevap]

I think that "History" page would be really helpfull. Many users update their versions once a year and they would like to read what is new (and not only in the latest version). Or there should be any hook to enable returning back older "About" pages with the help of custom plugin?

BTW: Now, there is message that there were 12 bugs fixed in WordPress 3.3.2. Is it right? I found only 2 bugs in Trac...

[SergeyBiryukov]

Replying to pavelevap:

Now, there is message that there were 12 bugs fixed in WordPress 3.3.2. Is it right?

​http://core.trac.wordpress.org/log/branches/3.3?rev=20552&stop_rev=20087

[pavelevap]

Yes, but these commits are mostly related to part "some security issues"? I found only 3 or 4 fixed bugs...

[nacin]

12 total bugs were fixed (according to my napkin math at the time). That included some security issues.

[pavelevap]

:-) I thought that we differ security and other bugs. Also our localization was made in sense of "security" + "other" bugs, so "some" security problems + several (4) bugs = 12 issues.

"... addressed some security issues and fixed 12 bugs"

This sentence suggests that there are some security issues + other bugs, but it was probably only our misunderstanding...

In 3.3.1 it were 1 security issues and 15 fixed bugs, I guess...

[jane]

Replying to pavelevap:

Many users update their versions once a year and they would like to read what is new (and not only in the latest version).

This is not behavior we should encourage, period. A link to a Codex page that lists out previous versions would be more appropriate. About the current version is just that, about the current version. Not about all the versions since the last time you updated your software.

[jane]

Sketch of 3.4 about screen layout

[jane]

Having Chelsea make screenshots for About screen, gave sketch of layout (attached here) to go with new text. She'll do CSS patch as well if Ozz or other likely candidate isn't available.

[chexee]

HTML caption backend screenshot

[chexee]

HTML caption front end screenshot

[chexee]

Large flexible header screenshot

[chexee]

Small flexible header screenshot

[chexee]

Medium flexible header screenshot

[chexee]

Wide theme customizer screenshot

[chexee]

Theme customizer screenshot

[chexee]

Flexible header media library upload screenshot

[chexee]

I uploaded 3.4 screenshots per Jane's sketch above.

[azaozz]

Replying to chexee:

Thanks, will put the css together by tonight.

[chexee]

New caption screenshot with the word "Default" removed

[azaozz]

In [20840]:

Simpler layout for the about screen (still needs text), props chexee, see #20423

[azaozz]

The above patch scales images with max-width: ...%, this can be changed to @media rules instead.

[azaozz]

In [20842]:

Crush flex-header-media-library.png, see #20423

[jane]

Text for about page

[jane]

cc @azaozz: Uploaded text file for about screen text. Needs appropriate link to Codex for describing theme support for flex headers (or can remove reference to theme support). Should we ditch the mobile section? I think that stuff might be better in the announcement post.

[ocean90]

Note:

Look for the Customize button on the Themes screen.

wp.com has a button, here we have only a link.

[jane]

Replying to ocean90:

wp.com has a button, here we have only a link.

Right you are modify at will. Main point is to call out that the word there is Customize vs Live Preview.

[ryan]

In [20843]:

about.php text. Props jane. see #20423

[kobenland]

After [20843], is it too early to make them strings translatable again?

[azaozz]

In [20847]:

About screen: make the text translatable again and escape <img src=admin_url(), see #20423

[dd32]

There's a few cases of --- in that text, Perhaps we should change those to a ndash (or mdash?) asap before translators get to work :)

[nacin]

In [20848]:

Use mdash. see #20423.

[azaozz]

In [20849]:

About screen: fix typo, see #20423

[jane]

Closing. Re-open if any typos etc.

[duck_]

Replying to jane:

Closing. Re-open if any typos etc.

20423.minor-typos.diff​

[duck_]

In [20855]:

Fix minor typos in about.php. See #20423.