Main: Use updated WordPress blue for site headers

[richtabor]

Summary

Updates the legacy WordPress.org site headers to use the newer WordPress blue value, #3858e9.

Why this approach

• The wporg and wporg-main themes are Sass-built legacy themes, not block themes with a shared theme.json color preset source.
• --wp--preset--color--blueberry-1 exists only in a scoped inline style on the wporg-main front page banner, so using it in shared header CSS would depend on a custom property that is not guaranteed to exist in the base wporg theme or other contexts.
• The existing $color__wp-blue: #0073aa variable is still used by legacy links, navigation, buttons, and other styles. Updating that variable would broaden this change beyond the headers.
• A new Sass variable keeps the change explicit and scoped while compiling to a deterministic static color in the generated CSS.

$color__wp-blueberry: #3858e9;

What changed

• Adds $color__wp-blueberry to the shared wporg Sass color settings.
• Uses that variable for the base wporg site header.
• Uses that variable for the wporg-main home page header.
• Includes generated style.css and style-rtl.css updates for both themes so committed assets match the Sass source.

Screenshots

Before

After

Test plan

• Visit the WordPress.org home page and confirm the header uses the updated WordPress blue.
• Confirm the compiled styles output static #3858e9 for the updated header backgrounds.
• Confirm no --wp--preset--color--blueberry-1 dependency is introduced for these header styles.

[github-actions]

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 richtabor.

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

[Copilot]

✅ Ready to approve

The change is scoped, consistent across Sass sources and compiled assets, and does not introduce a dependency on a runtime CSS custom property.

Note: this review does not count toward required approvals for merging.

Pull request overview

This PR updates the legacy WordPress.org theme headers to use the newer WordPress blue (#3858e9) by introducing a dedicated Sass color token and applying it to the relevant header styling in wporg and wporg-main.

Changes:

• Added a new Sass variable $color__wp-blueberry: #3858e9; to keep the change scoped to headers.
• Updated the wporg .site-header background to use $color__wp-blueberry.
• Updated the wporg-main home header styling to use $color__wp-blueberry and regenerated compiled CSS assets accordingly.

File summaries

File	Description
wordpress.org/public_html/wp-content/themes/pub/wporg/css/style.css	Updates compiled CSS so .site-header uses #3858e9.
wordpress.org/public_html/wp-content/themes/pub/wporg/css/style-rtl.css	RTL compiled CSS update to keep header color consistent (#3858e9).
wordpress.org/public_html/wp-content/themes/pub/wporg/css/settings/_colors.scss	Introduces $color__wp-blueberry Sass variable for the new header blue.
wordpress.org/public_html/wp-content/themes/pub/wporg/css/components/_site-header.scss	Switches header background from $color__wp-blue to $color__wp-blueberry.
wordpress.org/public_html/wp-content/themes/pub/wporg-main/css/objects/_site-header.scss	Updates wporg-main home header background to $color__wp-blueberry.

Copilot's findings

Files not reviewed (2)

• wordpress.org/public_html/wp-content/themes/pub/wporg/css/style-rtl.css: Generated file
• wordpress.org/public_html/wp-content/themes/pub/wporg/css/style.css: Generated file

• Files reviewed: 3/7 changed files
• Comments generated: 0

Note

Your feedback helps us improve the quality of this feature.
Please use 👍 or 👎 to tell us whether this assessment is correct.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.