Update README.md

Author: Richard Bray

README.md

@@ -140,177 +140,16 @@
 }
 ```
 
-### Breakpoints (Media Queries)
-```html
-<article class="listing-card listing-card--featured">
-
-  <h1 class="listing-card__title">Adorable 2BR in the sunny Mission</h1>
-
-  <div class="listing-card__content">
-    <p>Vestibulum id ligula porta felis euismod semper.</p>
-  </div>
-
-</article>
-```
+### Nesting
+* Do not nest more than 3 levels deep. This way css doesn't become too specific making it easier to use on other parts of the site.
 
 ```css
-.listing-card { }
-.listing-card--featured { }
-.listing-card__title { }
-.listing-card__content { }
-```
-
-  * `.listing-card` is the “block” and represents the higher-level component
-  * `.listing-card__title` is an “element” and represents a descendant of `.listing-card` that helps compose the block as a whole.
-  * `.listing-card--featured` is a “modifier” and represents a different state or variation on the `.listing-card` block.
-
-### ID selectors
-
-While it is possible to select elements by ID in CSS, it should generally be considered an anti-pattern. ID selectors introduce an unnecessarily high level of [specificity](https://developer.mozilla.org/en-US/docs/Web/CSS/Specificity) to your rule declarations, and they are not reusable.
-
-For more on this subject, read [CSS Wizardry's article](http://csswizardry.com/2014/07/hacks-for-dealing-with-specificity/) on dealing with specificity.
-
-### JavaScript hooks
-
-Avoid binding to the same class in both your CSS and JavaScript. Conflating the two often leads to, at a minimum, time wasted during refactoring when a developer must cross-reference each class they are changing, and at its worst, developers being afraid to make changes for fear of breaking functionality.
-
-We recommend creating JavaScript-specific classes to bind to, prefixed with `.js-`:
-
-```html
-<button class="btn btn-primary js-request-to-book">Request to Book</button>
-```
-
-## Sass
-
-### Syntax
-
-* Use the `.scss` syntax, never the original `.sass` syntax
-* Order your `@extend`, regular CSS and `@include` declarations logically (see below)
-
-### Ordering of property declarations
-
-1. `@extend` declarations
-
-    Just as in other OOP languages, it's helpful to know right away that this “class” inherits from another.
-
-    ```scss
-    .btn-green {
-      @extend %btn;
-      // ...
-    }
-    ```
-
-2. Property declarations
-
-    Now list all standard property declarations, anything that isn't an `@extend`, `@include`, or a nested selector.
-
-    ```scss
-    .btn-green {
-      @extend %btn;
-      background: green;
-      font-weight: bold;
-      // ...
-    }
-    ```
-
-3. `@include` declarations
-
-    Grouping `@include`s at the end makes it easier to read the entire selector, and it also visually separates them from `@extend`s.
-
-    ```scss
-    .btn-green {
-      @extend %btn;
-      background: green;
-      font-weight: bold;
-      @include transition(background 0.5s ease);
-      // ...
-    }
-    ```
-
-4. Nested selectors
-
-    Nested selectors, _if necessary_, go last, and nothing goes after them. Add whitespace between your rule declarations and nested selectors, as well as between adjacent nested selectors. Apply the same guidelines as above to your nested selectors.
-
-    ```scss
-    .btn {
-      @extend %btn;
-      background: green;
-      font-weight: bold;
-      @include transition(background 0.5s ease);
-
-      .icon {
-        margin-right: 10px;
-      }
-    }
-    ```
-
-### Mixins
-
-Mixins, defined via `@mixin` and called with `@include`, should be used sparingly and only when function arguments are necessary. A mixin without function arguments (i.e. `@mixin hide { display: none; }`) is better accomplished using a placeholder selector (see below) in order to prevent code duplication.
-
-### Placeholders
-
-Placeholders in Sass, defined via `%selector` and used with `@extend`, are a way of defining rule declarations that aren't automatically output in your compiled stylesheet. Instead, other selectors “inherit” from the placeholder, and the relevant selectors are copied to the point in the stylesheet where the placeholder is defined. This is best illustrated with the example below.
-
-Placeholders are powerful but easy to abuse, especially when combined with nested selectors. **As a rule of thumb, avoid creating placeholders with nested rule declarations, or calling `@extend` inside nested selectors.** Placeholders are great for simple inheritance, but can easily result in the accidental creation of additional selectors without paying close attention to how and where they are used.
-
-**Sass**
-
-```sass
-// Unless we call `@extend %icon` these properties won't be compiled!
-%icon {
-  font-family: "Airglyphs";
-}
-
-.icon-error {
-  @extend %icon;
-  color: red;
-}
-
-.icon-success {
-  @extend %icon;
-  color: green;
-}
-```
-
-**CSS**
-
-```css
-.icon-error,
-.icon-success {
-  font-family: "Airglyphs";
-}
-
-.icon-error {
-  color: red;
-}
-
-.icon-success {
-  color: green;
-}
-```
-
-### Nested selectors
-
-**Do not nest selectors more than three levels deep!**
-
-```scss
-.page-container {
-  .content {
-    .profile {
+.m-page-container {
+  .o-content {
+    .c-profile {
       // STOP!
     }
   }
 }
 ```
 
-When selectors become this long, you're likely writing CSS that is:
-
-* Strongly coupled to the HTML (fragile) *—OR—*
-* Overly specific (powerful) *—OR—*
-* Not reusable
-
-
-Again: **never nest ID selectors!**
-
-If you must use an ID selector in the first place (and you should really try not to), they should never be nested. If you find yourself doing this, you need to revisit your markup, or figure out why such strong specificity is needed. If you are writing well formed HTML and CSS, you should **never** need to do this.