anchor.diff:                Examples include the Media Object, the Nav Abstraction, and the Island Object.
                 These classes do not affect look-and-feel, only visual structure. Think back to
                 the #[b Layout] and #[b Box Structure] levels of the inverted CSS property triangle above.
  +              Object-Oriented CSS is where it all started.
             section
               h4 Components
               p: strong.
  
positive.code:           every time, whereas hopefully your stylesheet will have been downloaded only once
            and then cached.
        section.c-Document__Complete
          h2.-fs-i.-fv-i.-fw-i
            b.-fw-9 class&middot;i&middot;tis
            |  (kl&aelig;s-a&#x026a;&apos;t&#x0258;s) 
            abbr.-fs-t(title="noun") n.
          p.
            No, I&rsquo;m not talking about an overuse of classes&mdash;I don&rsquo;t
  
negative.code:             p.
                In contrast to Objects, Components are heavily dependent on content, cosmetics,
                and function. They are recognizable pieces of user-interaction that have a particular
                look-and-feel. Buttons, navigation bars, and labels are all good examples.
                Components have properties belonging in the smallest four layers of the
                inverted CSS property triangle.
              p.
                To build a fully-functional visual element on a page, you must combine
                Objects and Components. Using just a Component class is not sufficient, because
                you will get the skin without the structure.
              aside
                p: small.
                  In most cases, the cosmetics of a Component laregly contribute to its function.
                  As frequent as Components come, they are unusual in that
                  their semantics are derived from their presentation,
                  that is, the look-and-feel of a Component may determine its meaning in terms of usability.
                  For example, a #[code span] might not look like anything with CSS turned off,
                  but with the right class and CSS turned on it might clearly represent
                  an icon attached to a link.
                p: small.
                  As a consequence, authors should be careful with Components because users with
                  a visual interface might have an advantage over users with, say, an audio interface.
                  Therefore authors should continue to support
                  SEO and accessibility best practices. Read up on
                  #[a(href="https://developers.google.com/schemas/formats/microdata") HTML5 Microdata] and
                  #[a(href="https://www.w3.org/WAI/intro/aria.php") ARIA roles]
                  for more information.
              div.c-Document__Informative
                p.
                  I have not decided yet whether to make these next sections formal. This is just an idea:
  