Feedback for curators of the Web Design Track, please put Sass into the context a bit.

Sass is introduced as the last subject of the Web Design Track. Once you reach that point, you should already have some examples that you've built with vanilla CSS. (A portfolio, galleries, landing pages etc.) Suddenly, Sass comes into play and we find ourselves converting a single-page marketing type of website (Lake Utah) into Sass. While this Lake Utah serves as a good example in terms of simplicity of the demonstration, the placement of Guil's Sass course at the end of the track does leave the question hanging; "But why?" OK, organization and optimization is great but when is it worth it to convert a project to Sass?

I believe this question has to be discussed a bit to give beginners a perspective about CSS preprocessors. The current videos of Sass are actually good at explaining how it's written, so my feedback is merely about a context issue rather than the "CSS to Sass Course" itself.

I think answering these questions in the Web Design track would be extremely useful.

1) Would you use Sass for a single page marketing website? If yes, are we telling the students to write all of their new projects using Sass from that point on?

2) If we need preprocessors only at certain projects, at what level of complexity in a website do we need their help?

3) Why Sass? Are there better options for specific projects? If there are, let's at least explore these options.