After many policy discussions it has been decided that Seven and Bartik will be marked @internal. This means they can change over time and no one should depend on their markup and CSS staying exactly the same.
See:
#2544740: [policy] Consider not supporting core module markup and CSS between minor releases
#2550249: [meta] Document @internal APIs both explicitly in phpdoc and implicitly in d.o documentation
The recommendation for themers and site builders/owners is that if you wish to make modifications to Seven or Bartik, you should copy, not subtheme, them. If you still choose to subtheme, be aware that it can change with an update to Drupal so be prepared to chase the current release.
In this issue, we need a patch to add a warning message to Seven's and Bartik's info file with the recommendation to copy instead of subtheming.
| Comment | File | Size | Author |
|---|---|---|---|
| #35 | interdiff-2575533-29-35.txt | 645 bytes | leolandotan |
| #35 | add-warning-message-to-bartik-2575533-35.patch | 1.94 KB | leolandotan |
| #29 | interdiff-2575533-21-29.txt | 989 bytes | leolandotan |
| #29 | add-warning-message-to-bartik-2575533-29.patch | 1.94 KB | leolandotan |
| #26 | interdiff-2575533-21-25.patch | 989 bytes | leolandotan |
Comments
Comment #2
lewisnymanHere's a patch.
Comment #3
star-szrhigh recomended = highly recommended
Comment #4
lewisnymanComment #5
j2r commentedMinor change as per the comment number 3.
(If I understand correctly thats the only change require.)
Comment #6
lewisnymanHere's the draft change record: https://www.drupal.org/node/2582945
I've provided two options, maybe we should do that in the code comment as well? Is it good practice to link to the change record?
Comment #7
Bojhan commentedWhoo :)
Comment #8
lomo commentedI'm not sure what more could need to be done now, but if we want to nit-pick word changes, we can either:
1) Do it now and keep this ticket open for a month longer with 50 more comments, or
2) Call this finished and allow other people who feel like nitpicking reference this issue in the new issue they create.
I'm inclined to call this finished. ;-)
RTBC?
Comment #9
davidhernandezAlways make sure the add the issue to the change record so people see it linked there and it is linked here. I added it.
I just realized, should we do the same for Bartik? I'd make a separate issue for that.
Comment #10
catchComment #11
xjmThis can actually be RC eligible since it only adds documentation of a policy we've already agreed upon. Thanks!
Comment #12
xjmSince this documentation helps set an important expectation for themers, tagging as an 8.0.1 target.
Do we have that separate issue for Bartik? I'd be fine with it in this patch as well, actually.
Should we put an @internal on a line by itself à la phpdoc? Nothing probably scans Twig templates atm, but it would be good to be consistent.
Comment #13
xjmNR for #12. Thanks!
Comment #14
joaogarin commentedI have added the two options as mentioned by @LewisNyman.
I think probably the same should be done in Bartik. Also I added the link to the change record
Comment #15
Bojhan commentedMoving to Bartik queue. Lets also include this message with Bartik
Comment #16
lewisnymanComment #17
alvimurtaza commentedI added the same to the Bartik theme as well.
Comment #18
imkartik commentedCan be reviewed when the same has been implemented in Bartik theme as well. Status changed.
Comment #19
imkartik commentedLooking into it.
Comment #20
Bojhan commentedPatch should include both Seven and Bartk.
Comment #21
alvimurtaza commentedRe-adding with change for both Bartik and Seven.
Comment #22
imkartik commentedTested it.. Looks fine. Just a suggestion.. The change record mentioned for Bartik is 'https://www.drupal.org/node/2582945' .. The thing is this node speaks about change in 'Seven' theme only and there is nothing mentioned about 'Bartik'. I am new to this, but do we need to modify the 'Change record' or edit the node-2582945 to include 'Bartik' theme.
Comment #23
imkartik commentedUnassigning..
Comment #24
star-szrThanks! The title should be updated to include Bartik, and component can just be theme system :)
Bartik is not (generally) an admin theme. Take out the word "admin" here.
Comment #25
leolandotan commentedComment #26
leolandotan commentedHi,
Here I have applied the suggested changes from @cottser.
Thanks!
Comment #27
leolandotan commentedSorry I wasn't able to use the right file format for the interdiff. :(
Comment #29
leolandotan commentedThis is a copy of the patch and interdiff files from comment #26. I just renamed them accordingly too.
My apologies for the mistake on the interdiff.
Thanks!
Comment #30
leolandotan commentedComment #31
davidhernandezComment #32
emma.mariaThis applies to both Bartik and Seven.
Comment #33
emma.mariaThe link to the change record is for Seven, we need to create one for Bartik.
Also @leolando.tan can you please unassign yourself from the issue when you finish working on it please.
Comment #34
emma.mariaI have created the Bartik change record at the link below; please can it be added to the patch :)
https://www.drupal.org/node/2673014
Comment #35
leolandotan commentedHi @emma.maria, I'm very sorry. I'll do that on my future work with issues. Thank you very much!
Here I have also applied the Bartik change record link in Bartik's info.yml file.
Thanks!
Comment #36
leolandotan commentedComment #37
emma.mariaI checked over the patch in #35 and the copy for both themes is now correct, plus both themes have separate change records. Setting this to RTBC.
Comment #38
catchCommitted/pushed to 8.1.x and cherry-picked to 8.0.x. Thanks!
Comment #42
quietone commentedPublish the change record