Editing the theme
Editing the CSS based themes in the
common directory (cinnamon, gnome-shell, gtk-3.0)
This theme uses libsass to process the various .scss files. Never edit any of the .css files manually.
Rebuild to generate all css files using
Editing the GTK 2 themes
The colors and includes are defined in
darker/gtkrcfor each theme variant
main.rccontains the major part of the theme
panel.rccontains the panel styling for Xfce and MATE
apps.rccontains some application specific rules
Because this theme is heavily based on the pixmap engine, a lot of the styling comes from the images in the
dark/assets folders. Don't edit these images directly. See the next section.
Editing the images for the GTK 2, GTK 3 and XFWM4 themes
Go to the
assets.svgfile in inkscape. Each object in the .svg file corresponds to an image in the
Find the object you want to edit and make your changes. Important: Don't change the object id!
Contributing to the project
The main purpose of this fork is to maintain the theme. This means that all major changes to the visual style should be avoided, unless there are very good reason for them.
All contributions to the theme are appreciated, as long as they are useful and well implemented, and don't increase the maintenance load, or unnecessarily alter the visual style. If you're unsure about anything, or would like to work on some larger project, it's not a bad idea to open an issue for discussion before submitting a pull request.
Sending pull requests
Nicely split single-purpose commits, and clean and descriptive commit messages are greatly appreciated. Please abide by the following commit message guidelines if possible:
Prepend the first line of the message with a tag describing what part of the theme is affected, e.g.
build:etc. This makes the commit logs much cleaner.
Add a full link to the pull request you opened, or a related github issue at the end of the commit message for future reference.