- Issue created by @andy-blum
- 🇬🇧United Kingdom dreamleaf
I see the logic and thinking behind this, but is this not effectively making Drupal harder to work with?
The ability to subtheme means that a person doesn't need to understand everything a base theme is doing, to sometimes just make trivial styling changes. I get that Olivero is intended to be a showcase of what is possible and that's great, but it's also a bit misleading if that is the face of Drupal and people can't easily customise it without knowing the nuts and bolts.
Starterkit goes some way to providing an abstracted version of a theme, but it still doesn't solve the barrier to entry issue - which subtheming provides.
Agency and enterprise will likely be creating themes from scratch, and have no need for subtheming - unless they are avoiding reinventing the wheel (ie using bootstrap or another framework base theme).
The introduction of Single Directory Components ✨ Add Single Directory Components as a new experimental module Fixed (if this gets approved) could also go some way to providing a respectable answer to disallowing subtheming while still allowing overriding of components. So, assuming that goes ahead, maybe there should be a suggestion that if a theme is disallowing subtheming, it still provides a method for customisation.
