anchor.diff:            ### Why BEM over the others?
   
       .grid__row
  +      .grid__cell-sm_size_12.raw-text
  +        p No matter what methodology you choose to use in your projects, you will get advantages of structured CSS and UI. Some of them are less strict and more flexible, other is easier to understand and adapt in team. Instead of writting our opinion on BEM advantages, we leave you with some quotes about it:
  +
  +    .grid__row
         .grid__cell-sm_size_4.raw-text
           h4(style="text-align: right")
  -          | "
             a(href="http://www.integralist.co.uk/posts/maintainable-css-with-bem/#why-bem-over-the-others") Maintainable CSS with BEM
  -          | "
             br
             | by Mark McDonnell
         .grid__cell-sm_size_8.raw-text
  
positive.code:     .grid__row
        .grid__cell-sm_size_5.raw-text
          h4(style="text-align: right")
            | "
            a(href="http://justinmarsan.com/css-methodology-and-frameworks/") CSS methodology and frameworks
            | "
            br
            | by Justin Marsan
        .grid__cell-sm_size_7.raw-text
  
negative.code:         h1 Introduction
            .badge.badge_yellow work in progress
          :markdown
            On smaller brochure sites, how your organize your styles isn’t usually a big concern. You get in there, write some CSS, or maybe even some SASS. You compile it all into a single stylesheet with SASS’s production settings, and then you aggregate it to get all the stylesheets from modules into a nice tidy package.
  
            However, when it comes to larger, more complex projects, how you organize your code is a key to efficiency. Not only in how how much time it takes, but also in how much code you write, and how much a browser has to load. This is especially important when you’re working with a team of themers, and when performance is important.
  
            This also true for long-term projects with legacy code (read "[How to Scale and Maintain Legacy CSS with Sass and SMACSS](http://webuild.envato.com/blog/how-to-scale-and-maintain-legacy-css-with-sass-and-smacss/)" — some nice SMACSS and BEM mixing in there).
  
            ### Methodologies
  
            There are plenty of [methodologies](https://github.com/ikkou/awesome-css#architecture) out there which aimed on reducing CSS codebase and organizing programmers cooperation and maintaining of CSS code. This is obvious in large projects like Twitter, Facebook and [Github](http://markdotto.com/2014/07/23/githubs-css/#two-bundles), but other projects often grows into same “Huge CSS file” state pretty quickly.
  
  