Gin Admin Theme: The Future of Drupal Admin UX

What Is Gin Admin Theme?

The Gin Admin Theme is an open-source administration theme for Drupal that gives editors and developers a modern, opinionated alternative to the default Claro theme. It is built on top of Claro and Drupal's Olivero design language, then extends them with features Claro does not ship: dark mode, a sticky action bar, vertical sidebar navigation, custom accent colors, and a high-contrast accessibility mode.

Gin is maintained by Sascha Eggenberger and a community of contributors. According to drupal.org usage data, the project is installed on more than 50,000 active Drupal sites making it one of the most-used contrib admin themes in the ecosystem.

It is fully compatible with Drupal 10 and Drupal 11, ships as a Composer package (drupal/gin), and is released under the GPL.

Image

Why Gin Matters in 2026

For years, the standard answer to "the Drupal admin is dated" was either to live with Claro or to bolt on a custom backend theme per project. Gin changed that equation. By treating the admin experience as a product versioned, designed, and iterated on independently of core Gin has become the place where modern admin UX gets tested before it enters Drupal core.

Three things have made this matter more in 2025–2026:

1. Drupal CMS, the official marketer-ready distribution released by the Drupal Association in January 2025, ships with Gin enabled by default a meaningful endorsement of Gin's production readiness.
2. Gin 4.0 brought a Composer-level architecture overhaul and tighter alignment with Drupal core's design system.
3. Drupal's official Admin UI initiative has begun upstreaming Gin patterns into core, validating the project's role as a proving ground.

If you are building a new Drupal site in 2026, the question is no longer "should I install Gin?" it's "which version, and how should I configure it?"

Gin vs Claro: A Detailed Comparison

Claro is Drupal's official admin theme, maintained in core. Gin is a contrib theme built on top of Claro. Both are excellent they solve different problems.

hich should you choose?

• Choose Claro if you have a strict zero-contrib admin policy or you want to wait for these features to land in core.
• Choose Gin if your editors and content team will use the admin every day and modern UX directly affects their productivity.

For most editorial and marketing teams, Gin is the better choice in 2026. For government and highly regulated environments where contrib admin themes require additional review, Claro remains a safe default.

Standout Features of Gin

The features below are what set Gin apart from Claro and from older admin themes like Seven or Adminimal.

1. Light, dark, and auto modes

Gin syncs to the operating system's appearance setting, with manual override per user. Dark mode is not a tinted palette swap it is a deliberately designed scheme that maintains WCAG-compliant contrast on every admin surface.

2. Sticky action bar

The Save, Preview, and Delete buttons stay pinned to the bottom of the viewport while editors scroll through long content forms. This single feature meaningfully reduces edit time on content-heavy pages.

3. Vertical sidebar navigation

Replaces Drupal's traditional horizontal toolbar with a collapsible vertical sidebar. Mirrors the navigation pattern used by most modern SaaS admin tools, which makes onboarding faster for non-Drupal-native editors.

4. Custom accent and focus colors

Site owners can match the admin to their brand without writing CSS, and Gin validates contrast ratios in the UI to prevent accessibility regressions.

5. High-contrast accessibility mode

A dedicated mode that strengthens visual boundaries and focus indicators. Useful for editors with low vision and required by some public-sector accessibility audits.

6. Visual Type Tray

Replaces the standard content-type selector with a card-based picker, making "Add content" a faster, more visual action.

7. Layout Builder and Gutenberg refinements

Gin doesn't replace Layout Builder or Gutenberg, but it restyles their UI to feel native, reducing the visual seams editors usually feel when switching between core forms and the editorial canvas.

8. Gin Toolbar and Gin Login modules

Companion modules that bring consistent branding to the toolbar and the admin login screen. Useful for white-labeled client deployments.

Image

How to Install the Gin Admin Theme

The recommended way to install Gin is via Composer. The full process takes about five minutes.

Step 1 Require the package

composer require drupal/gin

Step 2 Enable the theme and its companion modules

drush en gin gin_toolbar gin_login -y

Step 3 Set Gin as your admin theme

Go to Appearance → find Gin → click Set as default administration theme.

Step 4 Configure Gin

Visit Appearance → Gin settings. From here you can:

• Choose dark, light, or auto mode
• Pick a custom accent color
• Enable the vertical sidebar
• Enable the high-contrast accessibility mode
• Adjust the toolbar layout

Image

Step 5 (optional) Override styles

For per-project customization, create a sub-theme or override via gin-custom.css. Gin's official documentation walks through both approaches.

How Vardot Approaches Gin on Client Projects

At Vardot, we have deployed Gin across editorial, government, and higher-education projects since the theme matured into a production-ready release. A few patterns from that experience are worth sharing.

We recommend Gin when

• The client's editorial team will use the admin daily and modern UX is a productivity gain.
• The site already runs on Varbase Gin pairs well with Varbase's pre-configured editorial workflows.
• White-labeled admin branding matters for the client experience.
• The client values having early access to UX patterns that will eventually land in Drupal core.

We default to Claro when

• The client has a strict zero-contrib admin policy (rare, but real in some regulated environments).
• The site is purely transactional with minimal editorial activity.

What we configure differently

Through the Vardot Delivery System our methodology for Drupal builds we treat the admin theme as part of the editorial experience, not a developer concern. During the Blueprint phase, we configure Gin's accent colors to match the client's brand, set the default theme mode based on the team's stated preference, and document the configuration so future agency partners can maintain it. This is the same approach we used contributing the content publishing track to Drupal CMS.