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

Remaining tasks

User interface changes

API changes

Comments

mortendk’s picture

Issue summary: View changes
mortendk’s picture

Title: field class follow the drupal coding standards » field items class follow the drupal coding standards
Issue summary: View changes
mdrummond’s picture

Issue summary: View changes
mortendk’s picture

Issue summary: View changes
pixelmord’s picture

Assigned: Unassigned » pixelmord
Issue tags: +sprint

I will look into that, with the first step being to find out what makes the test for https://drupal.org/node/2214241 fail

pixelmord’s picture

Assigned: pixelmord » Unassigned

Talked to @Galooph working on the other (divitis) issue and it makes only sense for one person to work on this.

galooph’s picture

Assigned: Unassigned » galooph
mortendk’s picture

Status: Active » Closed (duplicate)

this 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