Getting ready

Read the Installing Sass for command line usage recipe of Chapter 1, Getting Started with Sass, to find out how to install Ruby Sass.

How to do it...

Learn how to make your code more intuitive by performing the steps shown beneath:

How it works...

Web browsers use the hierarchy of your HTML structure to calculate CSS property values that have not been explicitly set. Consider an HTML structure like that shown here:

<div>
  <h2>blue</h2>
</div>

Here, the font color set by the color CSS property of the h2 HTML element inherits its value from the div HTML element. Note that the color CSS property has a default value of inheritance.

Now, you can use an SCSS code like that shown here to visualize this inheritance:

div {
  color: blue;

  h2 {
   font-size: 1.3em;
  }
}

In the preceding SCSS code, it is directly clear that the nested h2 selector got a calculated color value of blue inherited from the div element.

There's more...

Although nesting your selectors can make your code more intuitive, it can equally break other things. For instance, when considering OOCSS principles, this does not allow the nesting of headings (h1 - h6). Headings are considered to be built-in objects in OOCSS, so their appearance should be consistent across an entire website. You can read more about OOCSS in the Applying the OOCSS, SMACSS, and BEM methodologies recipe of this chapter.

You should restrict the levels of nesting in your SCSS code. If you apply too much nesting to your selectors, your CSS will get broken for every change in your HTML structure. Read more about this topic in the Avoiding nested selectors too deeply for more modular CSS recipe of this chapter.

See also