Voting starts in March for the Drupal Association Board election.
Color module is outdated and was created for a nitch release/theme:
The current color.module is more of a garland-addon than a useful module for recoloring themes.
- Refactor the color module by creating a more comprehensible hook-able API
- Use modern CSS3 techniques.
- Update or add additional libraries.
Create a sandbox for development purposes.
- HSL/RGB +alpha transparency support
- Create swatch API
- Create swatch library
User interface changes
You can find various mock-ups of how things might/should look in comments bellow. The UI changes will be:
- Use a color/swatch palette on the theme settings form.
- Render the color settings form in the selected theme for preview.
Original report by JurriaanRoelofs
The current color.module is more of a garland-addon than a useful module for recoloring themes. I know because I've managed to build 5 themes for color.module _despite_ how it is built.
Various parties are interested in recoloring abilities for Drupal for various purposes. For me it's building great-looking themes that are abstracted from colors and given the freedom recoloring stylesheets and complex graphics with accuracy as well as good usability. Other parties are interested in using color.module as a feature on community websites, to enable users to recolor their profile page theme and/or recolor the sitewide theme to their preference.
In order to achieve these things, we need a Color API and some modules that interface with it. To ensure backward compatibility with colorable themes (garland) color.module should be a regular external module so that users can choose to download color module or any other modules that enable recoloring capabilities.
Freeing the color module out of core allows for new technologies to be developed for better recoloring and better writing/rewriting of images, and it will be an opportunity to redo the color module "The Drupal Way".