Problem/Motivation
The Drupal core Bartik theme was released as part of Drupal 7 in January 2011, 9 years ago. It was great! It also stayed pretty much the same ever since and been included with Drupal 8 as well and potentially will be the default theme of Drupal 9 even. The web moved forward a whole lot in 9 years and Bartik is not doing justice to Drupal anymore. It was great in 2011, it is not great anymore.
Proposed resolution
Drupal 9 needs a new default frontend theme. A new, modern, clean frontend theme, Olivero is being built in the contributed project https://www.drupal.org/project/olivero for inclusion in Drupal core. This issue is to gather requirements for Drupal core inclusion.
Designs are at #3088378: Designs for new front-end theme for Drupal 9.
Olivero “beta” criteria
Once the following level of feature completeness has been reached, we will consider tagging beta release for Olivero:
Must-haves for the beta release:
Features
- #3115420: Add search block(s) to the header
- #3115190: Configure and theme the Header Region using POC components
- #3115194: Configure and theme the body field using work pulled from POC
- #3117239: Theme inline Media types
- #3117242: Theme/style the Form elements
- #3118063: Theme Warning/Error Messages
- #3118065: Theme Pager/Pagination component
- #3118071: Theme Content/Article Listing - Node Teaser
- #3118086: Theme/Config Comments
- #3118088: Theme Tags/Categories component
- #3095736: Create content for Drupal's initial "Getting started" page (after minimal or standard profile installation)
- #3115160: Adding additional menu items overlapping with logo
- #3122990: Style administrative tabs
- #3151500: Style views grid row style plugin markup
- #3123836: Support route:<nolink> and route:<button> within Olivero menus
- #3152050: Style core's progress bar
- #3153060: Theme forum module
- #3153061: Theme Book module pages and menu
Accessibility
- #3153334: All caps titles and Dyslexia
- #3153806: incorrect use of aria-labelledby in powered-by-drupal block
- #3153265: Skip link focus should not create layout shift
- #3153465: Focus on menu items
- #3153466: Search icon outline is not coming on keyboard focus as per other link in main menu.
- #3095152: Improve focus and error styles for form elements
- #3153260: Standardize focus states across all controls
Design/Usability improvements
Bugs
- #3152535: Site breaks when primary menu has external link
- #3153535: Automated Drupal 9 compatibility fixes
- #3151586: Remove bullet of link action
- #3139046: Search block form outside of header is not styled properly
- #3149714: Audit form items within settings tray for visual inconsistencies
- #3152333: Dropdown arrow in settings tray not visible and properly aligned
- #3152382: Radios and checkbox not aligned with label in settings tray
- #3129257: Fix order of the mobile tabs
Technical debt
- #3152624: Remove core 8 property from theme info file
- #3151405: All css colors must be variable
- #3138850: Optimize svg of system-powered-by block and fix linter
Core inclusion/Dependencies
- #3092753: Allow PostCSS Plugin “Custom Media” in core for Olivero theme - "Must have"
- #3093013: Allow PostCSS Plugin “PostCSS RTL” in core for Olivero theme - Very strong "should have"
- #3093010: Allow PostCSS Plugin “PostCSS Nested” in core for Olivero theme - Very strong "should have"
- #3117698: Allow PostCSS Plugin “Px to Rem” in core for Olivero theme - "Should have"
- #3153009: Create "Wide" image style for standard profile - "Should have"
Olivero “stable” criteria
Once the following level of feature completeness has been reached, we will consider tagging stable release for Olivero:
Must-have issues for stable release:
Features
- #3153874: Theme Ajax progress and throbber
- #3152545: Make fixed/fluid width page wrapping and aligning on wide screen optional via settings
- #3153860: Theme and Configure the RSS Feed Views Block
- #3130726: Add layout--content-full+ small correction on layout--content-narrow css classes
Accessibility
Design/Usability improvements
- #3153868: Design 404 "Page not found" and 403 "Forbidden/Access denied" pages
- #3151687: Entity reference with label formatter should not have separate styling
- #3144070: Extra space about taxonomy views
- #3092718: UX Issue in Search
- #3128163: H1 font size is really too big in some context
- #3129153: Improve theming of field-multiple-table fields
- #3088572: Very little content is visible on 13" Macbook screen (without scrolling)
Bugs
Technical debt
- #3124796: META: Adjust codebase to meet Drupal coding standards
- #3153234: JavaScript should be selecting [data-*] attributes (or js- prefixed classes)
- #3142857: layout class is not populated in some template + why using include
- #3153321: Olivero Utilities - debug.es6.js toggleLogo() use hardcoded logo path/name
- #3135518: Replace correct text in README.md file
- #3128132: Move burger and cross animated icons into single component
Core inclusion/Dependencies
- #3124339: Add new image style to Standard installation profile and update CT Article Default display
- #3153009: Create "Wide" image style for standard profile
Post-stable
- #3086514: Investigate use of the changing color themes for Olivero
- #3127588: Theme language switcher
- #3145934: social media icons
Olivero Staging Preview
Preview Link: https://bit.ly/olivero-tugboat
User interface changes
A new default frontend theme.
New image style for the standard profile: #3153009: Create "Wide" image style for standard profile
API changes
None.
Data model changes
None.
Release notes snippet
A new modern, clear frontend theme has been added to Drupal core called Oliver. (continue TBD)
Ability to Subtheme
Subtheming Olivero will not be initially supported, but we may include formal support in the future. That being said, if we find simple issues that can lead us toward making this more simple, we will commit them.
TimelineDisclaimer: I have no idea what I'm doing as far as core timelines and tend to be optimistic in my estimations
- Now: As of June 18th, 2020, we're on alpha3. We plan on releasing alpha4 on the week of June 29. release.
- Week of July 3 First beta. The beta will concentrate on
- Accessibility
- Coding standards
- The process to get into core
- Every one to two weeks: new beta
I'm not sure what's involved to get this into core, or if it can go straight to stable, but we hope to have it ready for inclusion by early August going into the core as stable. If we do not meet these criteria, it can go into the core as experimental.