Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
following up from https://drupal.org/comment/8613183#comment-8613183
"I’ve been trying to follow the Drupal 8 CSS architecture guidelines for the past 8 months or so and have ended up having "field" be a SMACSS component. Thus my markup looks like this:
<div class="field field--name/type/etc">
<div class="field__label"></div>
<ul class="field__items">
<li class="field__item"></li>
<li class="field__item"></li>
</ul>
</div>
Problem/Motivation
As a follow up to the remove the divitis #2214241: Field default markup - removing the divitis
Proposed resolution
- first fix the divitis #2214241: Field default markup - removing the divitis
- get the css wrapper classes fixed: #2217731: Move field classes out of preprocess and into templates
Comments
Comment #1
mortendk CreditAttribution: mortendk commentedComment #2
mortendk CreditAttribution: mortendk commentedComment #3
RainbowArrayComment #4
mortendk CreditAttribution: mortendk commentedComment #5
pixelmord CreditAttribution: pixelmord commentedI will look into that, with the first step being to find out what makes the test for https://drupal.org/node/2214241 fail
Comment #6
pixelmord CreditAttribution: pixelmord commentedTalked to @Galooph working on the other (divitis) issue and it makes only sense for one person to work on this.
Comment #7
galooph CreditAttribution: galooph commentedComment #8
mortendk CreditAttribution: mortendk commentedthis is now incorporated back into the divitis issue [#https://drupal.org/node/2214241] cause using correct classnames solved one of the issues around divitis -> #win