SharePoint Design Ninja – Stefan Bauer was telling me about SASS last week and it sounds pretty cool. Tbh, I had seen it mentioned a few times here and there, but not really truly understood it. So I thought we could have a discussion on it!
Is anyone else using it on a regular basis with SharePoint? If so what are your thoughts? Are you finding it to be a big time saver and how easy was it to learn?
BTW – if you don’t know what SASS is – it stands for “Syntactically Awesome Style Sheets” and is a way to “programme” your CSS.Â
Here’s a definition on the SASS site :Â
“Sass makes CSS fun again. Sass is an extension of CSS3, adding nested rules, variables, mixins, selector inheritance, and more. It’s translated to well-formatted, standard CSS using the command line tool or a web-framework plugin.“
If there’s enough interest I am sure we can encourage Stefan to do an SPChat on this new way of developing CSS.
We are using SASS together with Mindscape Web Workbench in our SharePoint 2013 Projects. It works really good and makes it efficient to work with in a team or individually. We divide it up in different logic sections (at least for us) which make is fast and easy to add or change CSS in the solution. A configuration file defines if the final CSS file will be written directly to Visual Studio project or to the 15 hive (just for development). No need to use CKS Dev and “Copy to SharePoint root” or to work directly on the 15 hive to be productive here. Just use Visual studio and press save to be up2date. Attached an image which display a part of our CSS structure in SharePoint. Under modules and partials we have our specific components. Under vendor we keep the files for example bootstrap in this example.
SASS is great, but I don’t use it because it does not work with CKSDev Visual Studio Extension properly. It’s a deal breaker for me.
