Summary

This issue is proposing a new design for the default frontend theme for Drupal 9 (targeted for inclusion in Drupal 9.1). Note this is separate from the new administration theme, Claro, which was just committed to core several days ago.

This new frontend theme will have a modern look and feel based on adjectives and principles that were identified during the design process (more on this below). It will be WCAG AA conformant, support updated functionality in Drupal, and is intended to feel modern going into the future. The theme is named “Olivero” after Rachel Olivero, who was an advocate for accessibility and a Drupal community member (more on that below).

Need

The design of the current default theme (Bartik) has not changed since the release of Drupal 7 in January of 2011. While Bartik has proved itself to be versatile over the years, its design has aged with the years and fails to showcase Drupal’s state-of-the-art power and functionality.

Goals

  • Updated modern design: Our intention is to design a theme that feels modern and ages well. Design elements such as drop shadows, and gradients are used sparingly while typography, animation and color palettes have been thought out.
  • Functionality that supports new features: We want the theme to include support for recent commonly used Drupal functionality such as second-level navigation, embedded media, layout builder, and more.
  • WCAG AA Conformance: The theme will be WCAG AA conformant. We will be working closely with accessibility experts and the Drupal Accessibility team to ensure that the theme passes Drupal’s stringent accessibility standards with flying colors.

We will work with the community to help ensure that the new theme is aligned with the above goals in order to create a successful theme.

Design Process

The first step was to solicit community feedback within the Drupal Core ideas queue: #3064880: Create new default front-end theme. This issue confirmed that the idea to add a new theme is sought after by the community.

Initial Stakeholders

Once we knew our idea was valid and sought after by the community, we moved to identify the stakeholders for the design process that we deemed essential for the theme to be successful, and to help guide us throughout the process. The following community members were identified:

First step: Stakeholder Survey

During the research phase, we worked with stakeholders to identify adjectives to help guide the visual design. We created a sliding scale exercise where stakeholders could add a points across several tone spectrums. Some of these were clearly one adjective or the other (“Formal” not “Casual”) while others highlight the importance of a balance (“Approachable” and “Official”).

Sliding Scale Survey showing various terms (Formal, casual) with dots placed between them.

Voice and tone of Olivero

The below are keywords that were identified and will serve as the voice and tone of the new theme:

  • Formal
  • Light & Bright (vs dark & impactful)
  • Contemporary
  • Approachable and Official
  • Novel (with some constraint)
  • Cool
  • High contrast with some restraint
  • Light (and not heavy)

Design Principles

The following principles were established through research and collaboration, and are useful for guiding future additions and feedback for changes.

  • Accessible: WCAG AA conformance is a top priority for the design. The layout, colors and functionality should provide an accessible theme that can be enjoyed by everyone.
  • Simple: Avoid unnecessary visual elements, colors, effects, and complexity.
  • Modern: Take advantage of the capabilities and strengths of modern browsers and interaction patterns.
  • Focused: Embrace high contrast, saturated color, and negative space to draw the eye to what’s most important. Design defaults for the 80%.
  • Flexible: Provide options and overrides to account for varied needs and preferences.

The Meeting / Feedback Loop

Once the design principles and the voice & tone were established, we then created 3 separate zoom mocks to explore how those styles could apply to pages and components. These were then presented to the stakeholders, who choose a design to move forward with.

3 designs for the new theme. Left one is more traditional, center is 😍, and the right one is kinda weird.

The chosen design was iterated upon, and once again brought in front of the stakeholders, who then provided additional feedback.

The design process continued with the addition of internal accessibility testing, which highlighted several contrast deficiencies that were subsequently fixed.

We then brought the designs to one of the Drupal core accessibility maintainers (thank you Rain!) to validate accessibility, give additional accessibility feedback, and answer some lingering questions.

The Design System

The goal is to create a design system that helps provide efficiency and flexibility while empowering team members from varied disciplines to maintain, extend and iterate on the design of the theme into the future.

Note that the design system is still a work in progress. We will continue to adapt and define the system to meet the needs of the community and software well into the development process.

Responsive Grids

What follows are the rules and guidelines that define the responsive grid for the design system.

Theme design with a uniform grid overlayed

Vertical Rhythm

"Vertical Rhythm" describes the visual rhythm of elements as a user scrolls down a page based on things like type size, line height and the margins between paragraphs and headings (and other page elements). We establish vertical rhythm by setting a target height for a VRU (vertical rhythm unit) and then leveraging that proportionally to guide things like line height, paragraph and heading margins, and sectional spacing. We also employ incremental leading when necessary to maintain the proper feel within varied type sizes.

  • Throughout the design system, 1 VRU = 9px

Spacing

Spacing such as padding and margin will be tied to the VRUs, and the grid system to help create a well balanced design that is predictable and easy to scale.

Typography

Typography is based on a scale to help keep type sizing, line-height and spacing consistent throughout the design. The base font used for body copy is 18px. From there, we created sizes for headers, metadata, quotations, and various ui elements. The font size is adjusted for smaller screen sizes.

Fonts utilized in this design are licensed under SIL Open font License 1.1. This license is compatible with the Drupal.org distribution packaging requirements.

Typography for the design showing headings, etc

Color Palette

The color palette created uses a bright blue as a base color and introduces neutral grays to help balance out the layout and design elements. The colors chosen help create a modern, bright feel while also bringing in some of the Drupal branding. Darker colors were introduced to help with accessibility while lighter colors are used for supporting design elements throughout the layout.

Colors used for the design

UI Patterns

Header & Navigation The header has been designed to accommodate the versatility of text titles or logos. Different versions of the header will display depending on what the user chooses to enable as their site identity (more on this below).

On scroll down, the header will collapse into a hamburger-button menu, allowing the user to always be able to access the menu on longer pages.

Desktop nav collapsing into a button when scrolled down. Also shows menu is open after button is clicked.

The theme will have an option toggle to turn on hamburger-button based navigation at wide widths. This will be useful in the case where the website has many long first-level navigation items.

Theme at wide widths showing button menu

Theme at wide widths showing button menu open

Olivero will also support secondary dropdown menus!

Theme showing dropdown secondary menu

Site branding variations

Theme settings will exist to change the background-color and width (if necessary) of the site-branding to support a wide range of logos and long text.

Site branding block variation with white background

Site branding block variation with gray background

Site branding block variation with logo

Site branding block variation gray with logo

Site branding block variation blue with logo

Buttons The goal for buttons is for users to easily recognize a clickable action. For the theme, we designed a primary button style that’s filled, and a secondary button style that’s an outlined version of the button.

Button variations and states. Focus states have extra outline.

Forms Form inputs are kept simple, yet modern. The goal is to have form elements feel part of the design, while still being recognizable, usable and accessible. The left color bar signals the form element, and labels are placed above the form field to help avoid any confusion. Form fields all have a similar look to help establish that they are a form element. States such as focus, disabled and errors have also been accounted for.

Form element styles showing variations and states. Text variations have extra left border.

Tables Table divider lines are kept at a minimum to help with readability. The theme will support responsive table features of Drupal.

Sidebar The new default theme supports a single sidebar region that allows content creators to showcase related posts and other types of utility blocks. This region will float next to the primary content. We eliminate the previous adaptation of having two sidebars so that the content stands out in a rich and meaningful way without having to compete for space.

Sidebar floating to the right of the body text

RTL Support The theme will fully support right-to-left languages as required by Drupal core.

Design is flipped with a right to left language (showing arabic).

Messages Messages are used to inform the user of an action that they may need to take, important information that they may need to know, or provide feedback on an action already taken. Messages are clear and easily notable. Messages have been designed in a way where bright color is used to highlight the message, but doesn’t interfere with the readability of the message itself. Icons are used to support the type of message that the theme is displaying.

Messages block variations have a gray background and icon. They are dismissable.

Breadcrumbs The placement of breadcrumbs near the top of the page above the page title is a familiar location where users can instantly identify them as breadcrumbs. Breadcrumb links will be displayed in the link color used throughout the design. On smaller devices, breadcrumbs will displayed left to right or right to left, spilling off the edge of the screen. A visual cue will let users know that there’s more breadcrumbs to see, and they can access those breadcrumbs by swiping left to right or right to left.

Breadcrumb links at desktop. There's a border bottom, and they are separated by chevrons.

At smaller widths, the breadcrumbs will have a horizontal overflow scroll functionality if the length goes beyond the width of its container. This is a common approach for providing access to the full breadcrumb trail on narrow screens.

Breadcrumbs at small widths. Text is cut off with indicator showing that it is horizontally scrollable.

What will not make MVP

We will not be supporting the Color module within the initial release, but this or similar functionality may be included later. We’re tracking this as a feature request in #3086514: Investigate use of the changing color themes for Olivero.

Proof of Concept HTML

Throughout the process, we’ve been building a prototype in static HTML, CSS, and JavaScript. The intention of this is to validate the scroll / header interactions, and ensure they can be made accessible. In addition, we’re validating the use of CSS grid and overall front-end architecture to ensure it can be made to be accessible, as well as work with Internet Explorer 11 (as well as other core supported browsers).

This proof of concept is not yet fully accessible, although it will eventually be made to be. At that point we plan on getting a full sign-off from the Drupal accessibility team, which will hopefully alleviate last minute time-crunches when the patch is submitted to Drupal core.

The proof of concept is at https://olivero-poc.netlify.com, and the git repository for this is at https://github.com/Lullabot/olivero-poc.

Theme Name

Drupal’s current theme, Bartik, was named after Jean Bartik, one of the original programmers for the ENIAC computer. We wanted to continue in that spirit and name this theme after a pioneering female programmer. Earlier this year, the Drupal community mourned the passing of Rachel Olivero, and we have named this new theme in her honor. Rachel touched many people in both the Drupal and accessibility communities. She worked at the United States National Federation of the Blind and she was committed to making technology accessible to ALL people. We chose the name Olivero not just because we have made accessibility a top priority, but also because we aspire to develop this theme in our community in a manner that is consistent with the qualities that Rachel embodied, including patience, generosity, and inclusivity.

Special thanks to Tearyne Almendariz for thinking of the idea to name the theme after Rachel.

Contributors to the design

Below is the initial team that worked through the designs (alphabetical)

Feedback

Our team would love for this to be a wider community effort, and we welcome feedback and thoughts around the style and design system. We have worked iteratively with the stakeholders to come to this point, and will continue to work iteratively with the community to ensure that we complete the best theme possible for Drupal.

We are especially looking for feedback related to the accessibility of the design, and we also want to ensure that the system is flexible with the capabilities of Drupal. This is a volunteer effort, and we will work hard to ensure all comments will be addressed in a thoughtful approach. You can review the Figma here. Please refrain from adding comments directly in Figma.

Feedback will be time-boxed to Friday, November 8th, 2019. We want to keep all feedback and comments in this issue. Please do not leave comments in Figma. If you are interested in having a conversation or want to help out, you can join the Drupal #d9-theme slack channel.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mherchel created an issue. See original summary.

ultimike’s picture

This looks amazing! Things about this I love:

  1. The site logo handling.
  2. Support for main menus with many items.
  3. 2nd level nav support.
  4. Horizontal sliding of breadcrumbs on narrow screens.
  5. Commitment to accessibility from the ground up, clearly not an afterthought.
  6. So long, Color module, enjoy your retirement with Overlay module.

-mike

jazzdrive3’s picture

I love how polished this feels, and I can tell a lot of thought has been put into each decision.

mherchel’s picture

Issue summary: View changes
mherchel’s picture

Issue summary: View changes
FileSize
241.98 KB
142.94 KB
bnjmnm’s picture

(All the usual disclaimers before I present concerns, because this looks fantastic and I look forward to using it)

I'm concerned there's too much whitespace, something I've also brought up with Claro. On some displays it's not particularly noticeable, but on a 13" MacBook or on an Ipad, the amount of whitespace makes it difficult to contextualize the page as a whole. The h1 sizing amplifies this effect.

"Not enough whitespace" is such a common newbie mistake it feels weird to suggest there is too much, but I think Olivero would benefit from having it toned down a bit. For example, on my 13" MacBook, the breadcrumbs occupy 22% of the vertical space on the page, and author/date occupies 20% of it. If a page title is even slightly longer than the one at https://olivero-poc.netlify.com then there's very little, if any, page content visible without scrolling - not the worst problem in the world, but quite different from most good-UX sites I visit.

The breadcrumbs and author elements mentioned above probably do not need so much separation from everything else, as they are both can be intuitively grouped with other elements on the page. Breadcrumbs can be visually grouped with navigation or with the page title, and author/date can be grouped with the page title.

iamnoskcaj’s picture

Beautiful work.

saschaeggi’s picture

My first impression on this proposal: This is a great idea and I really like it. It looks sleek, modern and minimalistic to me. I can also see that there was already put a lot of work into it.

Two things we learned over at what we're working on for Claro is that buttons and messages can be quite controversial. Maybe you can profit from the research and iterations we run through for messages styles until we landed at the current design implementation (find the specs here: https://www.figma.com/file/OqWgzAluHtsOd5uwm1lubFeH/Drupal-Design-system...). The synergies could be used to port it over to Olivero. Also for the focus styles we did a lot of feedback loops also with the accessibility team until we landed at the current implementation, see #3028099: Element focus: accessibility review and #3021087: Buttons.

If I can help you out with reviewing stuff I'm happy to volunteer.

Keep up the good work!

Cheers,
Sascha

johnwebdev’s picture

Fantastic work! And I cannot wait to be able to use it!

I'll have to agree with the whitespace from #6, I am on a MacBook Pro 13', and for me there is no page content visible before scrolling.

ryanapsmith’s picture

this is great work.
my only feedback so far is if you've explored using a polyfill for IE's lack of Intersection Observer support.
I've used the one at https://github.com/w3c/IntersectionObserver/blob/master/polyfill/interse... with relative success.

seanB’s picture

I just want to say this looks really good. Especially love the strong focus on accessibility. Great work!

e0ipso’s picture

This looks pretty fantastic. I cannot wait to be able to use this. Huge congrats to everyone involved.

fhaeberle’s picture

Wow, amazing work! I really like the colors, overall look and feel, the navigation and spacing. Also, the type system looks very solid. I also like the first idea on how to layout content.

I'm wondering: Is it planned to include dummy content in Olivero? Like displayed in the screens?

As @saschaeggi mentioned in #8, we have some learnings out of the design process from the Claro Admin Theme which can be adapted because they are already reviewed by accessibility maintainers.

brianperry’s picture

Nicely detailed proposal with lots of visibility into the process - looks like a huge step in the right direction. Happy to see a static browser prototype available. That should help folks wrap their heads around this in a way that mocks may not have.

jayakrishnanj’s picture

Awesome 🌟

fazni’s picture

Great work +1

isalmanhaider’s picture

Amazing!!!!!!!!!!

Great work - we are STUNNED with the brilliance and elegance of this them, I must say Goodbye to Bartik for sure :p

darren.fisher’s picture

Not much I can add that is useful other than I'm fully on-board with this. I think this will really help our clients get to work on their content before we switch to our custom theme which will allow content and development to happen in parallel more seamlessly. In short, I love it!!

tmsss’s picture

Congratulations for the amazing work!

I was wondering that a dark version would be useful. In terms of frontend development, it would be good if the Twig templates came organized under an Atomic Design perspective, this would facilitate the integration with component libraries like Storybook or Pattern Lab, but I admit that this could be to much opinionated for some folks.

jrockowitz’s picture

This proposal and initial designs look great.

To add to @saschaeggi's suggestion in #8 to take some lessons learned from the Claro theme and apply them to the new default theme.

For forms, the Claro theme is doing some exciting and well-thought-out experimentation. For example, Claro is using a bright green border for all focused page and form elements, which has excellent accessibility and looks great.

The new proposed default theme and the Claro admin theme should have a different look-n-feel, but for forms and maybe other key components, it is going to help to have consistent UX for people evaluating and managing a Drupal site.

mherchel’s picture

Thanks for the positive feedback everyone! It's heartening to hear that other people like it (and always a little scary when you release to the community) ❤️


@bnjmnm / @johndevman in #6 / #9 about the 13" screens:

Agree 100%. I've opened #3088572: Very little of Olivero's content is visible on 13" Macbook screen (without scrolling) to see what we can do (for example screen-height based media queries).


@saschaeggi / @fhaeberle / @jrockowitz in #8 / #20

Those links are super helpful! Opened up #3088569: Investigate further refinements to messages to investigate further improvements to messages. And #3088568: Further refine focus styles and buttons for buttons and focus styles.


@ryanapsmith in #10

I've also used that polyfill in the past. My initial concern is that we're shipping extra JS to handle a small use case. Currently IE11 uses graceful degradation and just doesn't get the sticky header features (which is okay). Also, keep in mind that we'll eventually stop supporting IE11. That all being said, this isn't a super-strong opinion. If you feel strongly about this, I'll open a followup issue!


@fhaeberle in #13

We do not plan on including dummy content. For MVP, I'm strictly limiting the scope of this to theme only. Dummy content would require much more work (the Umami team did this in an install profile).


@tmsss in #19

I would love a dark theme. Note this won't be in MVP. I'm adding this to the issue summary of #3086514: Investigate use of the changing color themes for Olivero. It would be nice to have two active themes. One for light mode and one for dark mode.

Although I do love atomic design and Pattern Lab, we will not be implementing atomic design on this because Drupal's default template structure doesn't lend itself to that organization structure out of the box. We're strictly limiting the scope of this project to theme only.

tmsss’s picture

Thanks for the feedback @mherchel, I'm looking forward to see a dark theme. Regarding the atomic design, I totally understand that this might get out of the scope of the project, but let me add that shila theme already handles this pretty well via twig namespaces and the Component Libraries module.

Keep up the good work!

MrPaulDriver’s picture

Excellent work!!!

It would be great if this could be included as an experimental theme, long before Drupal 9.1

davo20019’s picture

It is awesome!

aburrows’s picture

Beautiful and touching work everyone! Well done!

kjay’s picture

It's so exciting to see more design work happening in core and this design looks great! :)

I think that updating Drupal's front end theme so that it plays really well with new features and delivers a welcoming, accessible, and intuitive starting point will do a great deal for improving the overall experience of using Drupal. Great work!

MarianT’s picture

This design is modern and fresh. Good work you guys!

Taco Potze’s picture

At a first glance it looks great! Only thing is the menu action when closed that is slides out is a bit much on desktop. Why not leave it on top, much easier on the eyes. And when out and scrolling up fast the content overlaps with the menu so you might want to check that as the flickering should not have to be there I think. Lets do this!

andrea_london’s picture

looks very promising, i guess this is going to be also responsive (but not mobile first)

afsch’s picture

It looks amazing!
In further work would be great to consider UI improvements using techs like React or Vue as well :)

ckohl’s picture

Looks very promising, Amazing work so far!

donpwinston’s picture

Drop down menus!

mherchel’s picture

Issue summary: View changes
mherchel’s picture

Issue summary: View changes
heilop’s picture

So great! Looks amazing!

ipwa’s picture

@jrockowitz has some really good points about borrowing the forms approach and styles from Claro on #20.

cawi’s picture

Issue tags: +Sprint DrupalCon Amsterdam

Sitting at sprintroom in Amsterdam and looking for contributing I decide to help with Olivero. It is really a huge project and I really have a lot of respect for the ones who still invested a lot of work. Great job!

So, this is my feedback:

color concept:
- missing the color green
- love all the blue tones
- red is too bright (shade darker)


Blog Post

navbar desktop-version:
- main-navigation:
- hover-state:
distance to the border-bottom is too big, the distance in submenu is less, the login-in is totally different, so this confused me I can’t find the rhythm and harmony
- search:
- position of icon is too much left, I would expect much more right
- active state:
* no need to change font family for the placeholder
* black background is too strong contrast, should be much more smoother
* user experience for the position of closing icon is normally very closed to the right side. Here it is between „log in“ and main menu. This is little bit confusing.
* maybe moving the search icon to the very right could solve the problem
- check wether it is really necessary to have login and sign in. I could well imagine to have only login, and the possibility to sign in at the login-page

links inside text:
Really well done. It is total clear, that it is a link for the visitor. I really love the hover-state.

links to author:
I wish they would be the same like the links inside the text

lists:
The distance to the upper paragraph is too big. It looks like it stands alone and not in context to the list (https://olivero-poc.netlify.com/)

footer:
- Powered by Drupal
In english it sounds good. But translations are sometimes a little bit strange and not a good advertisement for Drupal.

beautifulmind’s picture

Let's do something about the fonts after the alpha/beta release. 'Lora' doesn't seem quite good. 'metropolis' is fantastic.

Regards,

Bhavin

rachel_norfolk’s picture

Issue tags: -Sprint DrupalCon Amsterdam +Amsterdam2019

Just adding the official DrupalCon Amsterdam 2019 issue tag...

baddysonja’s picture

Looks amazing. Great work.

I'm a bit unsure about the search input field and the behavior of it. I expected the same font as in the menu links when I opened it, but you have chosen to use large Lora which doesn't really fit when you haven't scrolled the site yet (on a Mac 13'). Wondering if it would be better to use Metropolis for the input field font?
Then also the autocomplete from the browser needs to be optimised (if that is possible, i'm not a frontender only a user ;)

Otherwise just great great great work and I'm looking forward seeing this go forward and will encourage my team to help out if they can.

andrewmacpherson’s picture

Issue summary: View changes

correcting wcag terminology

mherchel’s picture

@baddysonja yeah, it's not supposed to do that.. that's a bug! The designs have the input field being black. Out of curiosity. What device/browser are you using?

hudat’s picture

This looks awesome! Leaving a few minor comments below. Apologies if this is late in the game.

Anyhow, even more stoked for D9 after seeing this! Early congrats!

1. The space between the Subheadings and associated paragraph copy can be tightened. In some cases, like on Mobile, there’s ambiguity whether the Subheading relates to the paragraph text above or below the Subheading: See “Subheadings are the best!” https://www.figma.com/proto/x5zBLbvoW1jsvyAOt4Gp9I/Olivero-Theme---Publi... and https://www.figma.com/proto/x5zBLbvoW1jsvyAOt4Gp9I/Olivero-Theme---Publi...
2. Errors/alerts/warnings — In cases where the alerts/warnings are long, the light text might be hard to read over the dark background. Perhaps consider softening the black background a bit, or exploring a dark text over light bg format
3. The View/Edit/Devel toolbar can benefit from greater affordance (https://www.figma.com/proto/x5zBLbvoW1jsvyAOt4Gp9I/Olivero-Theme---Publi...). Using a different background color or shade (Maybe Blue Dark) would help differentiate it from the left tool bar and make it stand out more on the page
4. Inactive/disabled buttons are a little too subtle. Perhaps darken a bit so they have some more affordance: https://www.figma.com/proto/x5zBLbvoW1jsvyAOt4Gp9I/Olivero-Theme---Publi...
5. Breadcrumbs could benefit from Active state. In the following case, Products and Category can be dialed back (maybe Gray: Dark) and Subcategory can retain the blue treatment https://www.figma.com/proto/x5zBLbvoW1jsvyAOt4Gp9I/Olivero-Theme---Publi...

grantkruger’s picture

I just got around to watching the Amsterdam Driesnote where this was introduced and also where Dries talked an awful lot about lowering the bar for newbies. Past conversations often also talked about cheaper sites looking too much like Drupal sites, i.e. too much like every other simple Drupal site. I can't help but wonder if there are ways this theme could be more customisable, maybe not the unabashed craziness of themes like Garland and general use of the color module, but rather a selection of predefined color schemes that the Drupal newbie can select from, where each color scheme matches the thoughtfulness and guidelines above (primarily accessibility). Maybe even some different layout options as well? I'm thinking of things like the layout options gmail offers (Default, comfortable, compact) that are relatively minor style tweaks that drastically change the appearance. This could address concerns like those above concerning dark themes, whitespace, etc, while also making it possible for a newbie with limited design skills to make a site that looks a bit different and stock.

And maybe a way for well-thought-out variations of these color and or layout schemes to be contributed by dev shops and others, where we can pick from all contributed color and/or layout variations, maybe being a much more customizable variation of what the Zen theme used to try and do. I know we're unlikely to ever go the Weebly/Wix kind of route, but there's no denying how empowering design and layout control can be.

Overall I like the new theme and it is well overdue, but just thinking about ways Drupal can go back to being more friendly to newcomers and small shops, instead of assuming bigger teams and budgets. I have no skin in the game since we are well-funded and will always hire designers and themers for our site, but I'm a Drupal guy from way back and I miss how much more welcoming Drupal used to be.

ressa’s picture

@grantkruger: I agree that it would be great to offer the option of

... relatively minor style tweaks that drastically change the appearance. This could address concerns like those above concerning dark themes, whitespace, etc, while also making it possible for a newbie with limited design skills to make a site that looks a bit different and stock.

... so I am glad to see progress in #3086514: Investigate use of the changing color themes for Olivero. It would be really awesome to have several styles to choose between, like for example Bootswatch is structured, where you can change the entire design from a dropdown in Bootstrap.

webchick’s picture

Priority: Normal » Major

There was an informal poll over Twitter about features people would like to see in Drupal 9.1 https://twitter.com/webchick/status/1235689652838776832 (there will be a formal poll not over (just) Twitter coming later this month), and this was one of the most highly requested features. Just leaving a note. :)

volkswagenchick’s picture

Status: Active » Needs review
Related issues: +#3177296: [META] Make Olivero stable

The theme is now in Drupal core as an experimental theme. Moving this to needs review as it is now out of the ideation phase and into the project.

mherchel’s picture

Status: Needs review » Fixed

Marking this as fixed, as there's only occasional new design work with Olivero.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.