Make WordPress Core

Opened 3 weeks ago

Last modified 15 hours ago

#64546 new enhancement

Change the default admin color scheme from "Default" to "Modern"

Reported by: fabiankaegy's profile fabiankaegy Owned by:
Milestone: 7.0 Priority: normal
Severity: normal Version:
Component: Administration Keywords: has-patch
Focuses: ui, accessibility, administration Cc:

Description (last modified by sabernhardt)

This is a subticket of #64308 (WordPress Admin Visual Reskin).

As part of the WordPress 7.0 visual refresh, this ticket proposes changing the default admin color scheme from "Default" (fresh) to "Modern" for all users.

Background

The "Default" color scheme has been the admin default since WordPress 3.8. The "Modern" color scheme was introduced more recently and better aligns with the WordPress Design System and the visual direction established by the Block Editor and Site Editor.

With the visual reskin effort underway, switching to the "Modern" scheme as the default provides a more cohesive experience out of the box.

Proposed Changes

  • Update the default for new users: Change the fallback color scheme from fresh to modern in user creation and the color picker.
  • Migrate existing users: Add a database upgrade routine that migrates users currently set to fresh to modern.

Files Affected

  • src/wp-includes/version.php – Bump $wp_db_version
  • src/wp-admin/includes/upgrade.php – Add upgrade_700() function
  • src/wp-includes/user.php – Change default in wp_insert_user()
  • src/wp-admin/includes/misc.php – Change fallback in admin_color_scheme_picker()

Important Consideration

WordPress does not track whether a user explicitly selected a color scheme or inherited the default. This means users who intentionally chose "Default" will also be migrated to "Modern". These users can re-select "Default" from their profile settings if desired.

The "Default" color scheme will remain available as an option for users who prefer it.

Testing

  • Verify new user accounts receive the "Modern" color scheme
  • Verify the upgrade routine migrates existing fresh users to modern
  • Verify users with other color schemes (Light, Blue, Midnight, etc.) are unaffected
  • Verify "Default" scheme remains selectable in user profile

Related Tickets

  • #64308 – Explore a "Coat-of-Paint" Visual Reskin of the WordPress Admin for WordPress 7.0

Change History (10)

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


3 weeks ago
#1

  • Keywords has-patch added

#2 @sabernhardt
3 weeks ago

  • Description modified (diff)
  • Focuses accessibility added
  • Milestone changed from Awaiting Review to 7.0

@fabiankaegy commented on PR #10782:


2 weeks ago
#3

@mukeshpanchal27 Great catch! I found a few more similar instances where fresh was used as a fallback in case no value was set. Should all be fixed now!

#4 @Joen
2 weeks ago

I would support this change, as the modern color scheme matches in color with those of WordPress.org, and features higher contrast than the current default.

Should the schemes be renamed? I.e. Default → Classic, Modern → Default?

#5 @fabiankaegy
2 weeks ago

@Joen yeah exactly, in the patch I renamed it to Classic :)

#6 @jsmansart
9 days ago

Test on local WordPress

Environment

WordPress: 7.0-alpha-20260202.084607
PHP: 8.2.30
Server: pache/2.4.66
Database: mysqli 10.6.24-MariaDB
Browser: Firefox 148.0b8
OS: MacOS 26.2
Theme: Twenty Twenty-Five 1.4
MU Plugins: None activated

Test report

  1. Before the upgrade to the PR version

Creation of a blueuser user with blue color scheme selected
Creation of a webmaster user with classic color scheme selected
admin user has the classic color scheme

  1. After upgrade to the PR version

The screen with the Database upgrade button showed up -> OK
webmaster user color scheme is now modern -> OK
admin user color scheme is now modern -> OK
userblue user color scheme is still blue -> OK
Creation of a new user, the modern color scheme is automaticaly selected -> OK
Change of color scheme for user webmaster to classic -> OK

Last edited 9 days ago by jsmansart (previous) (diff)

#7 @karmatosed
7 days ago

I fully support this also and it looks like it tests well. To me this is ready to get into at least an initial commit as a result. What does everyone else think? If I was to pick one of these it would to start with this one.

@fabiankaegy commented on PR #10782:


7 days ago
#8

@peterwilsoncc thanks for the feedback :) all items should now be covered. Would love another review :)

@peterwilsoncc commented on PR #10782:


5 days ago
#9

@fabiankaegy What do you think about changing the onscreen display to Default which was done last time the default theme was changecd.

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


15 hours ago

Note: See TracTickets for help on using tickets.