- Issue created by @markconroy
- 🇮🇪Ireland markconroy
When creating custom themes, I quite like the process of just creating the bare minimum
- theme.info.yml
- theme.libraries.yml
- CSS + JS + templates as needed
- everything else inheriting from Stable9 or some other base theme
This means the custom theme directory is as small as possible and very easy to find your way around. Removing Stable9 would mean a change to this process. I'm not against that, but I would guess there are others that have the same process and maybe do not want a copy of every template, for example, in their custom themes.
- 🇳🇿New Zealand quietone
If deprecated is the intention to move it to a contributed project or just delete?
- 🇬🇧United Kingdom catch
@quietone we'd need to move it to a contributed project as we did for stable.
- 🇳🇿New Zealand quietone
@catch, thanks.
Adding tags. Since @markconroy is the Stable9 maintainer, this already has subsystem maintainer approval.
- 🇺🇸United States nicxvan
I don't know that matkconroy is in favor, I think he created this to track catch's discussion, but I don't want to speak for him.
- 🇮🇪Ireland markconroy
I'm not totally against this idea, but I'm also not totally for it either. As @nicxvan said, I created the issue to track @catch's discussion and so that it wouldn't get lost in the Slack history.
- 🇮🇪Ireland markconroy
Thinking about this further, if the future way to create themes is the starterkit method, then my "create the bare minimum and just overrides the templates that you want" is a moot point.
So I guess this proposal to deprecate Stable9 and move it to contrib has my approval (as subsystem maintainer).
Removing "Needs subsystem maintainer review" tag.
- 🇦🇺Australia 2pha
I am in the same boat and have been subtheming stable9 for the past few years.
The "create the bare minimum and just overrides the templates that you want" reasoning is what I liked about doing it this way.
Just me chiming in incase it's relevant.
