Say in the experiment description that it is not for live sites

The experiment is off by default, but nothing on the Experiments screen said what switching it on costs. Two things are worth knowing before anyone tries it on a site they care about: plugin styling on admin screens can render differently, because demoting WordPress's stylesheets into a lower cascade layer changes which rules win; and admin stylesheets arrive one by one, because style concatenation has to be off for the demotion to happen at all. Both are named rather than summarised as "not for production", which tells a reader nothing they can act on. The warning sits in the description rather than the label, as the experimental blocks entry does, so the feature keeps a plain name. "Visual only" is dropped. It read oddly beside a warning that plugin styles can change, and the change does have effects beyond appearance. "No markup changes" is the part that stays true. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
jasmussen · Oct 1, 2026 · Aug 28, 2026 · Aug 28, 2026 · Aug 28, 2026 · Sep 3, 2026
commit 160d0361782f7d69251ed29bb5555f219e4d21f2
@@ -107,7 +107,7 @@ function gutenberg_initialize_experiments_settings() {
 				array(
 					'id'          => 'gutenberg-wpds-admin-restyle',
 					'label'       => __( 'Admin design tokens', 'gutenberg' ),
-					'description' => __( 'Styles wp-admin from WordPress Design System tokens, so every admin screen reads as one product regardless of how it is rendered. Visual only; no markup changes.', 'gutenberg' ),
+					'description' => __( 'Styles wp-admin from WordPress Design System tokens, so every admin screen reads as one product regardless of how it is rendered. No markup changes. (Warning: this can change how plugin styles apply to admin screens, and it loads admin stylesheets one by one instead of combined. Use it for testing, not on a live site.)', 'gutenberg' ),
 				),
 				array(
 					'id'          => 'gutenberg-dashboard-widgets',