3 ms·
This is the key point. You save time working with Haml and Sass if your designers can use them, edit them, etc. I am longing to get to a point where the desig
by grandalf 17y ago
This is the key point. You save time working with Haml and Sass if your designers can use them, edit them, etc.
I am longing to get to a point where the designers I work with can be expected to write templates using mustache or django template language...
Ideally the designer can check out a submodule of the project and commit ongoing UI enhancements by simply modifying mustache/django templates that they wrote in the first place.
This could easily be implemented by using a static site generator to populate the templates with static data so that the designer could check his/her work before committing.
With Haml you end up translating the whole mess over and over again, and if you decide to make a big change to HTML/CSS you are spending lots of time redoing the HAML/Sass.
The other key thing to realize is that CSS is an extremely expressive spec when used properly I really don't think that the small bit of conciseness offered by Sass is worth adding another layer...
- nex3 17y agoCSS, although a very cool and powerful language, leaves a lot to be desired in one key area: abstraction. Not coincidentally, this is the area that Sass is best at. Chris Eppstein has an excellent blog post (http://chriseppstein.github.com/blog/2009/09/20/why-stylesheet-abstraction-matters/ http://chriseppstein.github.com/blog/2009/09/20/why-styleshe...) explaining why abstraction in stylesheets matters.
- grandalf 17y agoInteresting. Thanks for the link, I will check out Compass. I think the widgets/plugins are really an awesome idea.