Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/horizon-themes. Description: Motivation ========= The current state of the Horizon CSS (SCSS) does not allow a streamlined way to change the default skin, rather than overriding each style by hand. Most of the CSS style rules, other than those dealing with layout, can easily be abstracted to allow for a plug-n-play theme architecture. Description ========== Horizon makes use of Twitter's Bootstrap CSS, which has a great preprocessor layer already defined and many variable already accessible and useable for customizing Horizon's look and feel. There are a number of implementations of skins that already exist for Bootstrap. For the purposes of this task, I propose that we use an existing and well accepted implementation of Bootstrap's CSS called Bootswatch. Bootswatch already has a method for defining overrides that are clean and a number of already attractive Skins available. By creating an interface layer between Bootstrap's CSS and Horizon that matches the interface layer defined by Bootswatch, we will get a lot of useful skins immediately, as well as a path defined for any future skins that wish to get implemented. As part of this task, there will be some work to create an entirely new Bootswatch skin that mimics the current Horizon dashboard look and feel. UX === Since this task is 100% UX, see the description above. Specification URL (additional information): None
to make it clear, unfortunately this blueprint can not replace our -theme package
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2015:1548