70 likes | 196 Views
Emerging Web technology. SASS. What is SASS?. SASS stands for Syntactically Awesome StyleSheets . SASS was designed by Hampton Catlin and developed by Natalie Weizenbaum . SASS is like an extension of CSS3 which provides more power and several other mechanisms that CSS does not have.
E N D
What is SASS? • SASS stands for Syntactically Awesome StyleSheets. • SASS was designed by Hampton Catlin and developed by Natalie Weizenbaum. • SASS is like an extension of CSS3 which provides more power and several other mechanisms that CSS does not have. • The latest version of Sass is 3.4.2 which was released on August the 28th of this year. • SASS is coded in Ruby though there are other implementations such as PHP, libSass (C implementation) and JSass which is a Java implementation.
Why would I use Sass? • Sass plugs the holes in CSS meaning it is easier and faster to work with. • CSS does not use variables, mixins, nesting, inheritance and selectors but Sass uses a syntax that enables this so in return it speeds up things when using style sheets. • It can translate its syntax into a CSS file through a command line program. • Sass extends CSS for the better through many different mechanisms.
How do I use SASS? • To start you have to create a file and save it as .scss. • Sass stores information that is used on numerous occasions through variables by using the $ symbol to do so. • An example of using variables is displayed below:
Where do I get SASS? • You can download Sass from http://sass-lang.com/install • Before you can use Sass you will also need to install RubyGems from http://rubygems.org/pages/download
Are there any limitations or flaws? • Mixins could be a possible limitation depending on how it is used as it is a duplication tool which means the files size will increase when used resulting in overall performance being degraded.
Bibliography • http://sass-lang.com • http://en.wikipedia.org/wiki/Sass_(stylesheet_language) • http://cs3.bradshawenterprises.com/blog/why-sass/ • http://blog.millermedeiros.com/the-problem-with-css-pre-processors/