Using local colour variables in Less

One of the most time-consuming aspects of website design is when the customer wants multi-coloured menus—and for those colours to cascade through the other attributes on those site areas. This can involve lots of different selectors, and having to change them all to different colours can be a pain—and this is where using local colour variables in Less can save lots of time.

Standard colour variables

Consider the following set of declarations:

Now, imagine that these all had to be altered depending on the .site-area-x, and that we have huge number of selectors to restyle.

Obviously, we could simply declare our @color2, but then we have to go through and change the colour in all of the other declarations too.

And this needs to be done for each one of the eight different menu areas—it’s going to be pretty time-consuming.

Local colour variables to the rescue

There is a better way in which to do this—by using local colour variables. Consider the following set of declarations:

We now only have to change two attributes—the .site-area-x class, and the @site-area-colour.

OK, it’s not entirely automated, but it will take considerably less time than the first method.

2 thoughts on “Using local colour variables in Less

  1. I hadn’t heard of Less, so I’m glad for this post. I’ll give it a try in my current project, which has some moderately challenging CSS requirements. As it’s an intranet project in a corporate environment I’m most interested to see how it works with IE8 🙁

    • Less is a language which is run through a compiler: the compiled output is CSS. So, as long as your CSS is IE8 compliant, you should be fine…


Leave a Reply

Your email address will not be published. Required fields are marked *