Skip to content

Create About Page for 7.1 - #12845

Open
joedolson wants to merge 4 commits into
WordPress:trunkfrom
joedolson:about-7.1
Open

Create About Page for 7.1#12845
joedolson wants to merge 4 commits into
WordPress:trunkfrom
joedolson:about-7.1

Conversation

@joedolson

@joedolson joedolson commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Initial draft of the About Page for WordPress 7.1

This draft adds the feature images locally, as the CDN copies are not yet available.

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

Use of AI Tools

None


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props joedolson, rcorrales, markoserb.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@rbcorrales rbcorrales left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested locally at different breakpoints plus an he_IL RTL pass. All five pages render clean, no PHP notices, and the RTL headers resolve correctly.

Comments are mostly copy. The one worth catching before RC1 is the run-on on 141, since it's user visible. The rest is minor.

Comment thread src/wp-admin/about.php
</div>
<h3><?php _e( 'Performance' ); ?></h3>
<p><?php _e( 'WordPress 7.0 improves the accuracy of image loading prioritization, preventing hidden images in navigation overlays or interactive blocks from degrading the loading of critical resources. On-demand block stylesheet loading in classic themes is more reliable, and the ability is added for scripts to depend on script modules to reduce render-blocking.' ); ?></p>
<h3><?php _e( 'Improved Media Handling' ); ?></h3>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the only heading that is in title case on the page. The others are in sentence case.

Suggested change
<h3><?php _e( 'Improved Media Handling' ); ?></h3>
<h3><?php _e( 'Improved media handling' ); ?></h3>

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is probably a good change; but I'm going to leave it to @marko-srb and @annezazu to make that call.

Comment thread src/wp-admin/about.php Outdated
Comment thread src/wp-admin/about.php
<strong><?php _e( 'A centralized hub for your connections.' ); ?></strong><br />
<?php _e( 'The Connectors screen introduces a single hub for managing a range of external service integrations, including AI providers. Opt in by connecting your preferred AI provider, then put it to work across your site. The optional AI plugin adds a growing set of tools directly into the editor: create titles and excerpts, generate and edit images, and suggest alt text. Any plugin that needs to connect to an outside service can tap into this standardized connection management system, making it easy for users and developers alike.' ); ?>
<strong><?php _e( 'Consistent navigation, from dashboard to editor.' ); ?></strong><br />
<?php _e( 'The WordPress admin bar now stays with you as you move into the Site Editor and block editor, so you stay oriented as you move between the Site Editor and block editor. Admin bar also receives a small UI visual improvement.' ); ?>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the Site Editor and block editor appears twice in the same sentence, and so does as you move.

Suggested change
<?php _e( 'The WordPress admin bar now stays with you as you move into the Site Editor and block editor, so you stay oriented as you move between the Site Editor and block editor. Admin bar also receives a small UI visual improvement.' ); ?>
<?php _e( 'The WordPress admin bar now travels with you into the Site Editor and the block editor, so you stay oriented as you move between them. The admin bar also receives a small UI visual improvement.' ); ?>

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@annezazu This is a good suggestion for text revision; leaving it up to you.

Comment on lines 15 to 20
list( $display_version ) = explode( '-', get_bloginfo( 'version' ) );
$header_alt_text = sprintf(
/* translators: %s: Version number. */
__( 'WordPress %s' ),
$display_version
);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing the header image leaves $header_alt_text unused, and $display_version only feeds it, so both are dead now. Same in credits.php, freedoms.php and privacy.php.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to leave it for now; but thanks for noting it. If these images stay removed, I'll polish this and remove the dead code paths.

Comment thread src/wp-admin/credits.php
Comment thread src/wp-admin/freedoms.php
Comment thread src/wp-admin/privacy.php
Comment thread src/wp-admin/about.php
@rbcorrales

Copy link
Copy Markdown

One more thing, on narrow screens the header gets shorter, so the background image crops in and "WordPress 7.1" ends up sitting on the green part of the artwork instead of the blue. White on that green is 2.4:1, and it needs at least 3:1 for text that size. Checked at a 430px width. Desktop is fine as the title stays on the blue there.

Since the color comes from the image, it needs a different crop or a mobile version rather than a CSS change. Probably a separate ticket though.

image

@joedolson

Copy link
Copy Markdown
Contributor Author

No, there's no need for a separate ticket; this ticket covers the entire scope of building out the About Page, because it's a one-off task for the release.

@joedolson

joedolson commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

@marko-srb Can you take a look at the color contrast concerns on mobile? We could use something like a text shadow on mobile only that addressed this, e.g. text-shadow: 0 0 2px var(--background);, which would change the boundary with fairly minimal impact on the design.

(var(--background) is #3858e9, for the record.)

@marko-srb

Copy link
Copy Markdown

👋 Your suggestion works well. Let's go with minimal shadows. Not a good practice in general, but great fix suggestion for now. We will fix the images themselves so no contrast issues are present, prior 7.1 release. And swap them.

Do we still need svg images for RTL? I thought we are going with webp? If we need them, I can deliver them in 1hr

About page, text update is ok to happen, even if not applicable by someone on Google file. It's easy for us to change there, as long as it is good on the actual page. Though I'd leave this to Anne. But if this needs to ship, I can review, or provide text in an hr.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants