🚲🏡⇢ 🚲🏡⇢ 🚲🏡⇢ 🚲🏡⇢ 🚲🏡⇢ 🚲🏡⇢
Problem/Motivation
A new Stable theme will be created for Drupal 9 #3050374: Create Drupal 9 stable theme. It needs a name.
This may wind up being a simple process, but deserves it's own issue as the theme will be a fundamental part of D9 core and has the potential to generate a lengthy discussion. The cost benefits of choices such as stable9 vs. stable_9 should be carefully considered.
Options proposed so far:
- stable9
- stable_9
- d9stable
- stable_drupal9
- drupal9_stable
- neuf
- estable
Proposed resolution
Name Drupal 9 Stable as stable9.
Feedback is open till 13th of December 23:59 GMT.
Remaining tasks
Discuss name options.- Feedback on proposed name
User interface changes
...
Comments
Comment #2
wim leers😂
Comment #3
xjmI think that:
stableduring Drupal 9's core lifetime.stablewill be retained in Drupal core until Drupal 10.stable9(and subsequent themes should be calledstable10,stable11, etc.)Comment #4
xjmAlso, I'd like to propose timeboxing this discussion to 1 week.
Comment #5
xjmFinally, for context, this decision is related to the overall plan in: #2659890: [Policy] [Plan] Drupal 9 and 10 markup and CSS backwards compatibility
Comment #6
xjmOne more consideration that I think we can leave out of scope here. This is about the machine name for the theme; however, we're going to communicate about what
stablevs.stable9are, and at that point we'd want UX and Product input. Are Classy and Stable hidden from the UI? I have a vague memory that they are. If so there's a lot less to worry about.Comment #9
xjmSo I was expecting the scope of this discussion to be about whether it's called
stable9orstable_9ord9stable, etc., along those lines, but @larowlan proposed a couple more name-like suggestions, like a tribute name orneuf.My preference is to have the naming in a consistent, simple pattern from release to release, since this is what gives us something like a continuous upgrade path for themes. Someone should be able to figure out that it's the version of the Stable base theme for N major version at a glance. For that reason I think the name's pattern should be consistent from major to major, and should include
stableand the major version somehow.Comment #10
larowlanYep, plus one for stable9
Comment #11
larowlanComment #12
lauriiistable9seems fine but I also like the options that make it more obvious that the number is tied to a Drupal major version. Something likestable_drupal9ordrupal9_stablewould better communicate that.If we wanted to try something completely else, maybe
stablein some other language would work, likeestablein Spanish.Comment #13
bnjmnmI see the appeal of the variations in #12, but am still partial to
stable9. Part of this may be because it's the temp-name we've been using so I'm accustomed to it, but I also like that- It's very easy to remember correctly, so there's less risk of accidental renaming, which can reduce dev frustration and increase the likelihood of accuracy in comments/documentation/etc.
- Hypothetical test code that uses a variable to specify the Stable version will be easier to read.
Comment #14
lauriiiPeople who don't want to extend Classy will have to remember the theme name because the base theme property has been made required in Drupal 9: #3065545: Deprecate base theme fallback to Stable, therefore it's important that we come up with a theme name that is easy to remember.
stable9seems easy enough to learn, and it scales well for future major releases (at least better than coming up with something that doesn't use numbers).If
stable9is the machine name, what would the human-readable name be then?Comment #15
webchickSorry, just re-titling this slightly, since I initially thought this was about naming the Drupal 9 stable release itself. :P
Comment #16
bnjmnmThe human-readable name I've been using for the patches in #3050374: Create Drupal 9 stable theme is a not-particularly-surprising "Stable 9". I've internalized it to the point that it's hard to think of anything different, but this is probably the best place to have those instincts questioned. Because it's a hidden theme I don't think it will appear in the UI other than possibly errors and other log messages, but I'm sure it will get used in online docs and code comments.
Comment #17
zrpnr+1 for
stable9and "Stable 9" - I think it makes sense to have a version number that matches the Drupal version (unlike theseventheme which we still use in 8 🙂) Especially if the plan is to have stable10, stable11, etc in the future.It's also my preference to not have an underscore in the theme machine name.
Comment #18
dwwAnother +1 to "stable9".
-1 to having an underscore in the name.
-1 to using cute "stable-esque" names from other languages. That would simply cause confusion + frustration, wouldn't scale to future releases, would require more bikeshedding about which language to use for each major, and adds no value at all.
-1 to "stable_drupal9". It's a Drupal core theme. IMHO, it's obvious the 9 is from Drupal core, not some other random source. ;) If we wanted, we could make the human readable name "Stable - Drupal 9" or something, but I don't think that's needed, either. "Stable 9" seems fine.
+1 to a mural. ;)
Cheers,
-Derek
Comment #19
lauriiiIt seems like there are at least no clear objections to moving forward with stable9 so marking this as RTBC.
Comment #20
wim leersIf I remember correctly, I proposed this very name months ago, so 👍 from me too obviously.
EDIT: first mention of this is in #2352949-68: Deprecate using Classy as the default theme for the 'testing' profile, 3 months ago tomorrow. Might've been @lauriii, might've been me — doesn't matter obviously :) I'm relieved this was a surprisingly simple bikeshed 😅🙈
Comment #21
lauriiiComment #22
lauriiiThank you, everyone, for your input! Closing this issue since we didn't get any objections on moving forward with the proposed name.