Postponed
Project:
Drupal core
Version:
main
Component:
other
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
3 Jun 2025 at 10:30 UTC
Updated:
29 Aug 2026 at 12:54 UTC
Jump to comment: Most recent
Problem/Motivation
#2860419: [Meta] Appearance page is too long and confusing identified many problems with the Appearance page. With the advancement of Drupal CMS and especially Drupal Canvas, it became clear that having one consistent UX for admin interfaces is better and should be encouraged.
Steps to reproduce
Proposed resolution
- The advanced option to change the admin UI with Drush and similar backend means should be kept.
- The UI for changing the admin theme should be removed.
Comments
Comment #2
cilefen commentedI have encountered community members who operate web sites but do not use Drush and don’t know what it is. I don’t know what portion of the total works this way.
Comment #3
alexpottHaving a single admin theme for contrib modules (and core) to provide the best admin UX with makes lots of sense to me. Also using a different admin theme feels like something that does not need to be configurable alongside the frontend theme.
Comment #4
gábor hojtsy@cilefen: do they change the admin theme? Which is that admin theme? How do they obtain that different admin theme?
Comment #5
cilefen commentedI don't know whether the site admins who don't use Drush change the admin theme. I am only saying that these people exist. I don't know if there is an intersection between non-Drush users and the 73k sites that use Gin, for example. I can't answer your questions.
Comment #6
gábor hojtsyI asked how do they obtain it not how they enable it :)
Comment #7
cilefen commentedI didn't say they obtained anything. I was indicating that it's been my experience to discover that some site admins do not use Drush to add some context to this issue.
Comment #8
avpadernoDoes not #2860419: [Meta] Appearance page is too long and confusing suggest just removing the theme selector shown on the bottom of the page? It would still be possible to select the admin theme by clicking on the theme screenshot.
It would not be possible to set a theme for the node edit pages, though.
This issue seems to propose to remove any selector for the admin theme, which I take would be the default admin theme Drupal comes with, except when the admin theme is set via Drush commands.
Comment #9
gábor hojtsyYes, it could be Drush commands or a contrib module. With Experience Builder taking on a lot of the admin UI, it will be more and more odd to try to have a separate different admin theme unless it blends in with Experience Builder (which is not quite theme-able as such).
Comment #10
quietone commentedComment #11
catchComment #13
gábor hojtsyPostponed until #3576488: [meta] Admin theme: path to beta and stable and Claro is removed, then there will only be one admin theme in core again.
Comment #14
catchOne thought about this. When default admin is the default, we're still going to have a lot of sites running Gin and Claro.
Gin I think won't support Drupal 12 so all of those sites will need to move to default admin, that will be fine.
For Claro I think we might want to keep the UI around so that people can switch from claro to default admin easily. We could make the UI 'one way' so it's hidden when the theme is default admin and shown for any other admin theme. Then fully remove it in a later release.
Comment #15
xmacinfoI agree 100%. Let's wait for Drupal 13 before removing the UI completely.