Define the support lifecycle for Olivero sub theme or switch to a module
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3493220. -->
Reported by: [catch](https://www.drupal.org/user/35733)
>>>
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>The <a href="https://www.drupal.org/project/drupal_cms_olivero">https://www.drupal.org/project/drupal_cms_olivero</a> currently only includes styling for exposed filters in views.</p>
<p>Olivero in core could customise that styling instead, then there would not be any need for an extra project.</p>
<p>I think it is going to be a somewhat awkward upgrade path for sites if/when drupal_cms_olivero becomes redundant, either because issues are fixed in core or because there is a new Drupal CMS front-end theme. Either way it'll need to be deprecated, eventually unmaintained etc., sites are going to have to manually switch theme and uninstall it. If Drupal CMS only used Olivero sites could stay on that indefinitely via core even if Drupal CMS changes theme in the next year. So it would be better to fix this sooner and later before tens of thousands of sites are running it.</p>
<p>Opening as a Drupal CMS issue to track removing the logic from the theme once the core issue is fixed, also I don't know if a core issue has even been opened for this - if so would be great to link from here and vice versa.</p>
<h4 id="summary-steps-reproduce">Steps to reproduce</h4>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<h3 id="summary-ui-changes">User interface changes</h3>
<h3 id="summary-api-changes">API changes</h3>
<h3 id="summary-data-model-changes">Data model changes</h3>
> Related issue: [Issue #3491807](https://www.drupal.org/node/3491807)
> Related issue: [Issue #3491823](https://www.drupal.org/node/3491823)
> Related issue: [Issue #3491816](https://www.drupal.org/node/3491816)
> Related issue: [Issue #3491821](https://www.drupal.org/node/3491821)
> Related issue: [Issue #3491820](https://www.drupal.org/node/3491820)
> Related issue: [Issue #3491819](https://www.drupal.org/node/3491819)
> Related issue: [Issue #3491817](https://www.drupal.org/node/3491817)
> Related issue: [Issue #3491818](https://www.drupal.org/node/3491818)
> Related issue: [Issue #3491814](https://www.drupal.org/node/3491814)
> Related issue: [Issue #3491815](https://www.drupal.org/node/3491815)
> Related issue: [Issue #3491813](https://www.drupal.org/node/3491813)
> Related issue: [Issue #3491811](https://www.drupal.org/node/3491811)
> Related issue: [Issue #3489037](https://www.drupal.org/node/3489037)
issue