Follow-up to #2575737: Copy templates, CSS, and related assets to Stable and override core libraries' CSS
The theme named Stable was added to core to function as a default base theme, and backwards compatibility (BC) layer for Drupal 8. This purpose goes beyond simple themer preference for how to do things, which resulted in Classy. Stable will exist so that changes to core templates and CSS can continue to happen after release. This information is not widely known and is a paradigm shift from previous version of Drupal.
To make it clear to anyone that might theme Drupal 8, we should add a README.txt file to Stable explain why it exists and how to use, or not use, it. It does not have to contain incredibly detailed information, but at least make people aware of the BC layer, what happens if you don't use it, and where to get more information. (We can point to the d.o theming guide.)
I put this in documentation, since Stable is not currently listed as a Component.
| Comment | File | Size | Author |
|---|---|---|---|
| #31 | interdiff.txt | 1.86 KB | star-szr |
| #31 | add_readme_txt_file_to-2612618-31.patch | 1.32 KB | star-szr |
| #28 | interdiff-2612618-21-28.txt | 1.28 KB | r_sharma08 |
| #28 | add_readme_txt_file_to-2612618-28.patch | 1.24 KB | r_sharma08 |
| #25 | interdiff-2612618-21-25.txt | 2.37 KB | r_sharma08 |
Comments
Comment #2
catchComment #3
davidhernandezHere is some text to get it started.
Comment #4
anil280988 commented@davidhernandez
Added few lines to the file. Kindly see if its fine.
Comment #6
anil280988 commentedRecreated the patch.
Comment #7
davidhernandezThanks, Anil. I don't think the headings are actually necessary. Since the readme is in Stable's directory, it should be obvious that it will only contain information about Stable. The "About Drupal Theming" heading is separating that section and link completely from the other text, which I wouldn't want to do. Also, I don't think we would use all caps headings like that.
Comment #8
anil280988 commented@davidhernandez
I have added Heading in accordance with other themes README files, to maintain similar format. As in Stark theme ReadMe file, there are heading in Caps, so it keeps Uniformity.
Comment #9
davidhernandezFair enough. I see what you mean. We have some definite inconstancies here. Some of core's file have headings, some don't, some have all caps headings, some like maintainers.txt don't have all caps.
Comment #10
anil280988 commentedChanging status
Comment #12
kaushalkishorejaiswal commentedI have compared the file with other Readme files and it is in proper format.
Comment #14
jhodgdonThanks! I've added a new Stable component to the issue queue.
And this is fairly good, but it really could use some improvement before we add it to Core:
Nitpick: Extra blank line here.
This first sentence is run/on and/or garbled.
The grammar here is garbled.
false => FALSE I think? Hm, maybe not. Someone check this?
This line is an example for the previous paragraph. It should not be separated by a blank line, and the previous line should end in : to make this clear.
Comment #15
star-szrFor 4 lowercase is correct.
Comment #16
anil280988 commentedCreated patch with changes suggested by jhodgdon.
Comment #18
star-szrInterdiff please :) also looks like the patch doesn't apply.
Comment #19
anil280988 commentedRecreated Patch and added interdiff file.
Comment #20
star-szr"in the current" here would read better.
I would consider ending the sentence after "very few classes" and starting a new one.
I didn't read this closely enough. Stable will *not* be used when you set base theme to false, that's how you opt out as is discussed in the previous paragraph.
Thanks @anil280988!
Comment #21
kaushalkishorejaiswal commentedComment #22
star-szrInterdiff please!
Comment #23
jhodgdonNeed comma after CSS in this line.
Should this say "... using Stable as a base theme." ?
I think we should not be talking about "the current theme" here.
Also in the second line, see Cottser's recent review. I think if you set base theme to false, you do NOT get Stable, right?
Comment #24
davidhernandezThat can probably be, "if no base theme is set in a theme's .info.yml file" ?
Correct. It looks like when that sentence was rewritten its meaning became reversed. False opts out from using Stable.
Comment #25
r_sharma08 commentedThanks Jhodgdon and davidhernandez for clarification.
Attaching patch for review.
Comment #27
star-szr@r_sharma08 both patch and interdiff don't seem quite right, can you try generating those again please?
Comment #28
r_sharma08 commentedRe attached the patch and interdiff files. Please review
Comment #29
jhodgdonThanks for fixing up the patch files, but the previous review comments *still* have not been addressed:
Can we please NOT use the word "current" here? See previous comments.
And this is still wrong.
Comment #30
star-szrIt seems to be a new person writing the patch each time which is not helping. I'm going to go ahead and make those changes.
Comment #31
star-szrSummary of changes:
Removed JS - Stable doesn't contain any JS. Changed "This" to "Stable".
as base theme = as a base theme, per #23.2.
Updated the opt-in/opt-out details and moved the "Themes that opt out of using Stable" to after where we tell them how to opt out. Made it more of a clear warning. See interdiff/patch for all the details :)
Overall to me the first paragraph reads more like an explanation we would give to a core contributor rather than a new themer (for example). It also contradicts the next paragraph with this phrase: "clean, minimal markup provided by core". I think we can make it easier to understand. Here's an attempt:
All the backwards compatibility, evolution, etc. stuff could be explained further down I think for those who are interested. I also think we should add a similar README to Classy which points back to Stable.
Thoughts?
Comment #32
davidhernandezThere is an open issue to add a README to Classy.
#2575387: Add README.txt to Classy Base Theme?
Comment #33
star-szrBueno.
Comment #34
jhodgdonExcellent. As Cottser is theme system maintainer, and I am docs maintainer, and both of us like this, I went ahead and committed it to both 8.x branches. And I'll take a look at the other issue too for Classy. THANKS!
Comment #37
star-szrWell we can still iterate on it (my thoughts about the first paragraph, I will open a new issue for that to not hold this up any more). Thanks @jhodgdon! Glad to see we have a README in now.
Comment #38
star-szr#2630592: Tweak Stable's README.txt to be more understandable by new users
Comment #40
cilefen commented