README
1Summary
2-------
3
4* Do not edit the CSS directly, edit the source SCSS files and process them with SASS (run
5 `./parse-sass.sh` when you have the required software installed, as described below)
6* To be able to use the latest/adequate version of sass, install ruby, gem, sass & bundle.
7 On Fedora F20, this is done with `sudo dnf install rubygems && gem install bundle && bundle install`
8 from the same directory this README resides in.
9
10How to tweak the theme
11----------------------
12
13Adwaita is a complex theme, so to keep it maintainable it's written and processed in SASS. The
14generated CSS is then transformed into a gresource file during gtk build and used at runtime in a
15non-legible or editable form.
16
17It is very likely your change will happen in the _common.scss file. That's where all the widget
18selectors are defined. Here's a rundown of the "supporting" stylesheets, that are unlikely to be the
19right place for a drive by stylesheet fix:
20
21_colors.scss - global color definitions. We keep the number of defined colors to a necessary minimum,
22 most colors are derived form a handful of basics. It covers both the light variant and
23 the dark variant.
24
25_colors-public.scss - SCSS colors exported through gtk to allow for 3rd party apps color mixing.
26
27_drawing.scss - drawing helper mixings/functions to allow easier definition of widget drawing under
28 specific context. This is why Adwaita isn't 15000 LOC.
29
30_common.scss - actual definitions of style for each widget. This is where you are likely to add/remove
31 your changes.
32
33You can read about SASS at http://sass-lang.com/documentation/. Once you make your changes to the
34_common.scss file, you can either run the ./parse-sass.sh script or keep SASS watching for changes as you
35edit. This is done by running `bundle exec sass --watch --sourcemap=none .` If sass is out of date, or is
36missing, you can install it with `bundle install`.
37