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

Setting up Source Maps in Firefox


Before I continue I want to say one thing to Firefox users: PLEASE STOP USING FIREBUG!!! The built-in Firefox dev tools have been far better than anything Firebug has had to offer for at least 6 years. Also give Firefox Developer Edition a go, it's really nice. For me Firefox Developer Edition is my development browser of choice. Overall, I'm a long time Firefox fan boy. I just think Firefox makes everything look nicer than Chrome/Safari and other browsers. Text looks better in Firefox, animations are smoother (especially animating SVG paths), and overall performance is better in Firefox, especially when multiple tabs are open (Open in New Tab is my friend). Also, the built-in dev tools are as good as Chrome's dev tools for the most part. That's just me.

My issue is not with Chrome, it's Webkit. Chrome is great for development. Their source map support is really nice. It should be, Google proposed the original source map specification. My problem is entirely...