Book Image

Mastering Sass

By : Luke Watts
Book Image

Mastering Sass

By: Luke Watts

Overview of this book

CSS and Sass add elegance and excellence to the basic language, and consist of a CSS-compatible syntax that allows you to use variables, nested rules, mixins, inline imports, and much more. This book will start with an overview of the features in Sass and Compass, most of which you'll already be familiar; however, this will ensure you know what’s expected as the book goes deeper into Sass and Compass. Next you will learn CSS and HTML concepts that are vital to a good Sass workflow. After all, Sass exists to simplify writing CSS, but it won’t teach you how to make clean, scalable, reusable CSS. For that, you need to understand some basic concepts of OOCSS, SMACCS, and Atomic Design. Once you’ve brushed up on the important concepts, it’s time to write some Sass. Mainly you’ll write a few functions and mixins that really leverage control flow using @if / @else loops and you’ll learn how to figure out when and why things are going wrong before they bring you to a stop. Moving further, you’ll learn how to use @debug, @warn and @error to properly handle errors. You’ll also learn about Gulp and how to use it to automate your workflow and reduce your repetitive tasks. And finally you’ll learn about sourcemaps. With sourcemaps, you’ll be able to write, debug, and view your Sass and Compass all from within the browser. It’ll even LiveReload too! As a bonus, you’ll take a look at that funky Flexbox, currently all the rage! You’ll learn how powerful and flexible it really is, and how you can use it with Compass. Best of all, it falls back very gracefully indeed! In fact, you’ll be able to apply it to any existing project without having to change a line of the original CSS.
Table of Contents (16 chapters)
Mastering Sass
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

Summary


In this chapter we set up the last piece in our "optimized workflow" puzzle. We learned what Source maps are and what problems they're designed to overcome. Problems such as having to manually find the line of SCSS among dozens of files because your browser only shows you the filename and line number of the CSS file. Or needing to copy and paste the changes you make in the browser to your text editor and save them there to make changes permanent.

We looked at setting up support for source maps in Firefox and Chrome and the slight differences between those. Mainly workspaces to sync an entire folder as opposed to Firefox's method of only syncing files as you save them.

We looked at how to solve an issue which can arise if you do not tell BrowserSync to be more selective about the files it watches. By default, BrowserSync will try match a file to a linked file in your HTML. If it finds a matching file it simply updates that one file and "injects" the changes. However, when it finds files...