Problem/Motivation

Drupal effectively has two default administration themes: Claro for core, and Gin for Drupal CMS. This causes difficulty for UX designers and product managers, because new features must work well with both themes.

Gin is no longer an experimental fork of Claro to experiment with new ideas. It has matured into a state-of-the-art admin theme, while Claro has fallen behind, as evident by the decision to use Gin as the admin theme for Drupal CMS. As a result, we feel it is time for Gin to become the default theme for Drupal core.

Most of the initial work will happen in a 6.x branch of Gin #3530849: [META] Gin 6.x: Preparation for merging into core.

This issue is for tracking how and when to actually bring Gin into core, as well as all the tasks to make it the default admin theme once it is (standard profile, Umami etc.)

See also blog post here: https://www.drupal.org/about/core/blog/drupal-core-will-adopt-gin-admin-...

Comments

pameeela created an issue. See original summary.

catch’s picture

quietone’s picture

Adding as a child to the Modernization meta

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

quietone’s picture

Title: [META] Admin theme modernisation » [meta] Admin theme modernisation
Component: Claro theme » theme system
Status: Active » Closed (duplicate)
Related issues: +#3576488: [meta] Admin theme: path to beta and stable

Gin is now in core as an experimental theme. I think this is superseded by #3576488: [meta] Admin theme: path to beta and stable which is tracking all the issue to get it to stable.

Therefor closing this one.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.