Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Theme Strategy #82

Open
ebollens opened this issue Sep 19, 2012 · 0 comments
Open

Theme Strategy #82

ebollens opened this issue Sep 19, 2012 · 0 comments
Milestone

Comments

@ebollens
Copy link
Contributor

During our discussion on color strategy (https://github.com/ucla/WebBlocks/wiki/Color-Strategy), Howard Kim pointed out:

One thing I would add is a “theme” class may be useful. If a theme class is added to the body element, then that can provide a nice way of grouping the visual definitions of the semantic classes (e.g., primary, secondary, error, etc.). I could see the theme used for institutions (e.g., ucla, dark, modern, etc) and then the rest of the classes could be defined or overridden based on the existence of the theme (e.g., #ucla .primary-1{} could mean something different than #dark .primary-1{}). Obviously, there would have to be a default theme as well for all the styles to fall back on if a custom theme did not redefine one of the classes.

I think this makes a lot of sense and is something we should look at implementing support for down the line.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant