Search code examples
csslesscss-frameworks

Less CSS performance and implementation

What are the best ways to use LESS for CSS.

  • Basically should the Devs write a Less File and then have it compile for production
  • Should I link the LESS code and the javascript file.
  • Or should I skip the LESS rout altogether and just remake the classes

I am trying to wrangle together some rather sloppy css and want to get control of it before making major improvements. I think it would be very good to have site wide variable so Less seems like a good thing with the variables and nesting.

I am replacing a lot of the background images with css gradients and box shadows so I am also trying to get rid of the vendor prefixes. Sometimes I see what kindof looks like class overload but is it bad to append a lot of classes to an element such as 

<div class="comment dark-shadow round-corners"></div>
Solution

  • Less is a great styling language. I use it extensively, and it really helps with code maintainability, as well as with speed of writing the styles.

    I personally feel that your styles should not be dependent on javascript to render, so I use the less.app to compile all my LESS into CSS. I rest more peacefully knowing that all my CSS is there and that it works correctly before I put anything "live".

    If you are interested I have also been compiling a LESS mixin library that can be very useful: https://github.com/jdmiller82/-lessins-