>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3064880. --> Reported by: [mherchel](https://www.drupal.org/user/118428) >>> <h2 id="problemmotivation">Problem / Motivation</h2> <p>Bartik&rsquo;s design is almost 10 years old (See <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/683026" title="Status: Closed (fixed)">#683026: Add a new theme to D7 core: Bartik</a></span>). It has served as an amazing theme for that time period and has proved itself extremely adaptable. However, the design is dated, and Drupal could create a more positive first impression if the default theme had a more modern look and feel.</p> <h2 id="proposedresolution">Proposed Resolution</h2> <p>Now is the time to design and develop a new theme, and set it to be Drupal&rsquo;s default theme!</p> <h2 id="processtools">Process / Tools</h2> <ul> <li><a href="https://www.drupal.org/slack">Drupal Slack</a>, #d9-theme channel.</li> <li>Bi-weekly meetings. This will likely become more often as the development process proceeds.</li> <li><a href="https://www.figma.com">Figma</a> for creating / storage of designs</li> <li>The design process will take place off of Drupal.org. This will include the gathering of adjectives, objectives, style tiles, homepage, and key pages mockup.</li> <li>Once the design is visually complete, it will be made available on Drupal.org for a timeboxed period and enter a feedback loop with the Drupal community at large. </li> <li>After the feedback loop is complete, work will begin on a design system (including documentation).</li> <li>When the design system is near completion, the development will start.</li> </ul> <h2 id="keyfeaturessolutions">Key Features / Solutions:</h2> <ul> <li>Modern design <ul> <li>Component-based</li> <li>Responsive</li> </ul> </li> <li>Adaptable to various scenarios/use cases.</li> <li>Flexible, to allow site builders to do interesting things <ul> <li>Responsive menu <ul> <li>Multi-level Dropdown menu</li> </ul> </li> <li>Call to action</li> <li>Hero region</li> </ul></li> <li>Functional without JavaScript</li> <li>Support LTR and RTL</li> <li>Aim to conform with <a href="https://www.w3.org/WAI/WCAG21/quickref/?versions=2.1&amp;currentsidebar=%23col_customize&amp;showtechniques=125&amp;levels=aaa">WGAC 2.1 Level AA</a> success criteria. Note: not all criteria are the responsibility of a CMS theme.</li> <li>Support for the front page, node page, user page, contact form, and taxonomy pages.</li> </ul> <h2 id="limitations">Limitations</h2> <ul> <li>Webfonts must meet Drupal.org distribution packaging requirements <a href="https://www.drupal.org/node/1475972">https://www.drupal.org/node/1475972</a></li> <li>No images for the hero/lead-space, except for a swappable Drupal logo, and an option for SVG pattern image that can add to the design.</li> <li>This theme will not have any support for the Color module</li> <li>PostCSS can be used, but no CSS preprocessors</li> <li>Vanilla JavaScript only</li> </ul> <h2 id="timeline">Timeline</h2> <p>While it would be amazing to get this new theme into Drupal 9.0, the timeline is fairly unrealistic.</p> <p>A more realistic timeline would be for the theme to be added in a Drupal 9 minor release (9.1 or 9.2). <a href="https://www.drupal.org/u/lauriii">laurii</a> confirmed with <a href="https://www.drupal.org/u/xjm">xjm</a> that we could change Standard installation profiles default theme in a minor release, therefore even if the theme gets stable in a Drupal 9 minor release, It could be made the Standard installation profiles default theme before Drupal 10.</p> <h2>Scope</h2> <p>The scope of this initiative is to replace Bartik's look, feel, and functionality. Within the initial MVP stage, we will not be adding new features such as layout options, etc.</p> <h2 id="initialteam">Initial Team</h2> <p>The team below is the initial team on the project. Once the design is finalized, we expect the team to grow to include people throughout the Drupal community.</p> <ul> <li><a href="https://www.drupal.org/u/jwitkowski79">Jen Witkowski</a> - UX Designer. Has worked on design systems in the past and has a deep knowledge of UX, Design, and putting it all together. </li> <li><a href="https://www.drupal.org/u/proeung">Putra Bonaccorsi</a> - Front-end Developer. Worked on many enterprise-level projects and has a deep understanding of design systems, component libraries, and modern development techniques.</li> <li><a href="https://www.drupal.org/u/mtift">Matthew Tift</a> - Developer / Community lead / Cat herder. Matthew was also the co-lead of the configuration management initiative.</li> <li><a href="https://www.drupal.org/u/mherchel">Mike Herchel</a> - Front-end Developer (and Lead Initiative Coordinator)</li> </ul>