Make WordPress Core

Opened 7 weeks ago

Closed 10 days ago

Last modified 4 days ago

#61320 closed task (blessed) (fixed)

About Page 6.6

Reported by: marybaum's profile marybaum Owned by: marybaum's profile marybaum
Milestone: 6.6 Priority: high
Severity: normal Version:
Component: Help/About Keywords: has-patch dev-reviewed
Focuses: accessibility Cc:

Description

This is the ticket for the About page in WordPress 6.6. Message strategy is here: https://docs.google.com/document/d/10Qai-FXGHv36iAi-Onayr12PnSWUBc80xB3pVyxHMNo/edit?usp=sharing

Change History (30)

#1 @marybaum
7 weeks ago

Please note that between now and RC 1, this ticket will get and commit copy, code and visual assets for the About Page.

The copy must commit by RC 1, which is the hard string freeze. Code and assets can come in over the following two weeks, but I would like to see everything committed by RC 3.

cc: @richtabor @ellatrix @juanmaguitar @vcanales @meher @priethor @akshayar @audrasjb @estelaris

#2 @marybaum
6 weeks ago

  • Owner set to marybaum
  • Status changed from new to assigned

I've updated the message strategy.

#4 follow-up: @ryelle
4 weeks ago

Just a timeline note— I see the draft above still has ongoing comments, and I haven't seen a design in progress yet, so we won't be committing anything before beta-3. I'm a little concerned about the timeline of getting the finished strings & layout before RC1 (as I need at least a day to get this into code, so ideally content+design would be ready by friday).

Although regarding design, if we flag which items in the doc will have images (or icons), I could just lay out the page in the code and skip needing to rebuild it in figma?

This ticket was mentioned in Slack in #accessibility by sabernhardt. View the logs.


4 weeks ago

#6 in reply to: ↑ 4 @marybaum
4 weeks ago

Kelly, here's the Figma layout in progress: https://www.figma.com/design/W6dOEbfBOv99iVih53emOg/6.6-Highlight-Grid-%26-Microsite?node-id=201-13875&t=G7dBVpnahznZHlEE-0

There's a lively discussion over there, and I have told @annezazu I am planning to scrap nearly all of the copy in the Google doc and write to the layout. For transparency I will post separate screenshots of the section with the applicable visuals in place, and get feedback on that. I'm doing the rewrite now and hope to have all of it up in the next three hours but will in any case post those sections one at a time so people can start reacting asap and you can start coding as you see fit.

Replying to ryelle:

Just a timeline note— I see the draft above still has ongoing comments, and I haven't seen a design in progress yet, so we won't be committing anything before beta-3. I'm a little concerned about the timeline of getting the finished strings & layout before RC1 (as I need at least a day to get this into code, so ideally content+design would be ready by friday).

Although regarding design, if we flag which items in the doc will have images (or icons), I could just lay out the page in the code and skip needing to rebuild it in figma?

#7 @joedolson
3 weeks ago

  • Focuses accessibility added

Adding accessibility focus to ensure this gets reviewed.

#8 @ryelle
3 weeks ago

The About page discussion is happening over on the gutenberg github. To sync with this ticket, the latest mockup can be found in this comment.

As far as I know, this copy is final, and we'll be using the Highlights, Performance, and Accessibility sections verbatim for the About page (this is what I will pull content from). I'll start building this out shortly and should have a patch later today. I would like to commit today, to avoid holding up release tomorrow.

There's still an open question about the copy for the final CTA (above the Learn callout) — this should lead readers to visit the longer release page on wp.org. So far, @joen has suggested the following, but needs feedback:

And much more
For a comprehensive overview of all the new features and enhancements in WordPress 6.6, please visit the feature-showcase website.

This ticket was mentioned in PR #6892 on WordPress/wordpress-develop by @ryelle.


3 weeks ago
#9

  • Keywords has-patch added

This PR introduces the new content for the 6.6 About page. This release, the About page will have just the highlights for 6.6, and link off to the release page on WordPress.org for the full overview. See https://github.com/WordPress/wporg-main-2022/issues/454 for the release page tracking. Also see https://github.com/WordPress/gutenberg/issues/62631 for more discussion on this.

Desktop Small screen
https://github.com/WordPress/wordpress-develop/assets/541093/82b141ae-e0fb-4740-84b4-993449437fd1 https://github.com/WordPress/wordpress-develop/assets/541093/598a3a00-aafb-447c-9828-41a45f57c2fe

Trac ticket: https://core.trac.wordpress.org/ticket/61320

@ryelle commented on PR #6892:


3 weeks ago
#10

Based on feedback https://github.com/WordPress/gutenberg/issues/62631#issuecomment-2187678287, I've combined the subheadings & paragraphs into one paragraph:

https://github.com/WordPress/gutenberg/assets/541093/e5139d2e-9d6b-40c9-a811-e41417c5bd4b

#11 @ryelle
3 weeks ago

In 58568:

Help/About: Update the About page for 6.6.

Introducing the new content for the 6.6 About page. This release, the About page will have just the highlights for 6.6, and link off to the release page on WordPress.org for the full overview.

See #61320, https://github.com/WordPress/gutenberg/issues/62631.
Props ryelle, andrewserong, annezazu, joen, beafialho, richtabor, kristastevens, marybaum, cbringmann, DanSoschin, youknowriad.

@ryelle commented on PR #6892:


3 weeks ago
#12

Committed in r58568.

#13 @ryelle
3 weeks ago

  • Keywords needs-copy needs-design has-patch removed

I missed the echo for the button, so the link to the release page is not output.

<a href="<?php esc_url( __( 'https://wordpress.org/download/releases/6-6/' ) ); ?>" class="button button-primary button-hero"><?php _e( 'See everything new' ); ?></a>

We need another update for the images anyway, so this can be fixed then.

@joen What's the plan for the images here (core About page)? Are the images on the release page on w.org good, should I just grab those?

#14 @Joen
13 days ago

I have today updated the release site with final imagery and CSS tweaks. The individual features on the page are still to be replaced with videos, where the images present there at the moment will be video posters. I hope to have those in a more solid place later today.

This ticket was mentioned in PR #6954 on WordPress/wordpress-develop by @ryelle.


12 days ago
#15

  • Keywords has-patch added

The images have been uploaded to the w.org CDN and added into the About page. Additionally, the link to the release page has been fixed, and an extra translator note about the escaped percent sign has been added.

https://github.com/WordPress/wordpress-develop/assets/541093/0af5c79a-59b6-4598-bad9-26e8f6afc8f1

Trac ticket: https://core.trac.wordpress.org/ticket/61320

#16 @ryelle
12 days ago

In 58618:

Help/About: Add images to the About page.

The images have been uploaded to the w.org CDN and added into the About page. Additionally, the link to the release page has been fixed, and an extra translator note about the escaped percent sign has been added.

Follow-up to [58568].

Props ryelle, joen.
See #61320.

@ryelle commented on PR #6954:


12 days ago
#17

Committed in r58618.

#18 @ryelle
12 days ago

  • Keywords dev-feedback added

Need a second committer review to backport [58618] to the 6.6 branch.

#19 @davidbaumwald
12 days ago

  • Keywords dev-reviewed added; dev-feedback removed

Looks good to backport to the 6.6 branch.

#20 @ryelle
12 days ago

In 58620:

Help/About: Add images to the About page.

The images have been uploaded to the w.org CDN and added into the About page. Additionally, the link to the release page has been fixed, and an extra translator note about the escaped percent sign has been added.

Follow-up to [58568].

Reviewed by davidbaumwald.
Merges [58618] to the 6.6 branch.

Props ryelle, joen.
See #61320.

#21 @ryelle
12 days ago

  • Resolution set to fixed
  • Status changed from assigned to closed

I think [58618] was the last thing needed for the About page so I'll close this ticket 🎉

This ticket was mentioned in PR #6958 on WordPress/wordpress-develop by @peterwilsoncc.


12 days ago
#22

Modifies the performance string to make the following changes:

  • Replaces 6.6 with WordPress 6.6 for clarity
  • Wraps WP_Theme_JSON in a code tag to match data-wp-on-async styling
  • Updates translator comment accordingly

Trac ticket: https://core.trac.wordpress.org/ticket/61320

#23 @peterwilsoncc
12 days ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

I noticed the performance improvements string had a couple of inconsistencies, so am re-opening the ticket.

  • It referred simply to 6.6, elsewhere in the document it's always WordPress 6.6.
  • Inconstant formatting of code.

I've linked a pull request to fix each of these issues.

I don't think either of these are blockers so feel free to close the ticket again if y'all decide these changes are not needed.

#24 @ryelle
11 days ago

From @annezazu on this github issue

Was just coming here to connect those dots around performance numbers since we put 40% faster and now we're looking at 33%. @ryelle is this possible to update?

So I think we can go ahead with @peterwilsoncc's update & also change that "40" to "33", is that right @annezazu?

#25 @annezazu
11 days ago

That's right! I will comment here going forward for any future changes. Apologies for making it hard by diffusing the convo.

#26 @peterwilsoncc
11 days ago

  • Keywords dev-feedback added; dev-reviewed removed

r58671 isn't showing up in trac for whatever reason:

Help/About: Update performance improvements string.

Updates the performance improvements string with the finalized percentage improvement in the editor and to improve styling and language consistency.

Props ryelle, annezazu, peterwilsoncc.
Fixes #61320.

I've added the dev-feeback keyword for backport consideration to the 6.6 branch. If the commit hasn't shown up, it's 80b7747e on the GitHub mirror.

#28 @ryelle
10 days ago

  • Keywords dev-reviewed added; dev-feedback removed

[58671] looks good for backporting.

#29 @peterwilsoncc
10 days ago

  • Resolution set to fixed
  • Status changed from reopened to closed

In 58675:

Help/About: Update performance improvements string.

Updates the performance improvements string with the finalized percentage improvement in the editor and to improve styling and language consistency.

Reviewed by ryelle.
Merges [58671] to the 6.6 branch.

Props ryelle, annezazu, peterwilsoncc.
Fixes #61320.

This ticket was mentioned in Slack in #core by ryelle. View the logs.


4 days ago

Note: See TracTickets for help on using tickets.