guardian/frontend — pull request #5810 by sammorrisdesign (2014-09-01 17:55:30+00:00)
Title: Organise the use of colour in the project, update guss and include pasteup components

Beginning of the work to clean up the way we use colour in the project. The end result of which will be; colours are declared as variables in `_vars.scss` like so `$c-neutral1: guss-colour(neutral-1, $pasteup-palette);`. Then to specific a colour in a module you would just refer to the variable name and *not* by using the `guss-colour` function or manually typing in a hex code. I've managed to go through and catch all uses of `guss-colour` outside of `_vars.scss` but am yet to go through hex code usage throughout the project (baby steps for now).

All colour variables should be provided by use of a `guss-colour()` function call. For now however there are still some outstanding. This is part of an audit of colours across the site that will be visited soon (again, baby steps).

This also includes the start of the work to turn [guss](https://github.com/guardian/guss) in a collection of generic low-level helpers. This means that Guardian specific components in guss like guss-colours and guss-forms have now been separated into [pasteup-palette](https://github.com/guardian/pasteup-palette) and [pasteup-forms](https://github.com/guardian/pasteup-forms). For the moment these have just been included as separate dependencies inside `stylesheets/bower.json` but should be moved into a single pasteup component at a later date.

![colours](https://cloud.githubusercontent.com/assets/1607666/4111133/9d05bd88-31ff-11e4-8235-915d69fb8c76.gif)