Automatic Color Palette Generation
Built with ❤️
Supporting
Palette Webpack Plugin is an open source project and completely free to use.
However, the amount of effort needed to maintain and develop new features and products within the Roots ecosystem is not sustainable without proper financial backing. If you have the capability, please consider donating using the links below:
Overview
Palette Webpack Plugin allows you to generate a JSON
file during the build process containing your color palette from existing Sass maps and/or Tailwind.
While we hope someone may find this useful for other purposes, this plugin and it's output format were specifically built for handling WordPress' Gutenberg editor-color-palette
theme support feature.
Features
- Built to take the headache out of maintaining the WordPress editor palette.
- Merge, filter, and sort Sass color maps and your Tailwind theme colors with a configurable priority.
- Uses computer vision algorithms to detect and deprioritize grayscale colors to the bottom of the list.
- Gracefully loads Sass and/or Tailwind support as needed.
Getting Started
To begin, you'll need to install palette-webpack-plugin
:
$ yarn add palette-webpack-plugin -D
Then add the plugin to your webpack
config. Here is an example containing the default values:
webpack.config.js
const PalettePlugin = require('palette-webpack-plugin');
module.exports = {
plugins: [
new PalettePlugin({
output: 'palette.json',
wp_theme_json: false,
output_prepend: '',
blacklist: ['transparent', 'inherit'],
priority: 'tailwind',
pretty: false,
tailwind: {
config: './tailwind.config.js',
shades: false,
path: 'colors',
},
sass: {
path: 'resources/assets/styles/config',
files: ['variables.scss'],
variables: ['colors'],
},
}),
],
};
If you are using Laravel Mix, you may use the Mix helper like so:
webpack.mix.js
const mix = require('laravel-mix');
require('palette-webpack-plugin/src/mix');
mix.palette({ ... });
Usage
The plugin's signature:
webpack.config.js
module.exports = {
plugins: [new PalettePlugin(options)],
};
webpack.mix.js
mix.palette(options);
Options
Name | Type | Default | Description |
---|---|---|---|
output |
{String} |
'palette.json' |
The filename and path relative to the public path. |
wp_theme_json |
{Boolean} |
false |
Output the palette to WordPress 5.8's theme.json format. If enabled, the palette will replace the "settings.color.palette" property of the output file (which you should usually set output to theme.json ). If the output file does not exist, it will be created with a skeleton theme.json format. If you're the plugin with mix and a setPublicPath , you probably want to set output_prepend to ../ so the file gets written to the theme root. |
output_prepend |
{String} |
'' |
The value of this option is prepended to output. This is required when using wp_theme_json to make the output leave the public path when using mix. Set it to ../ to write the output to the top level of the theme. |
blacklist |
{Array} |
['transparent, 'inherit'] |
Globs to ignore colors. |
priority |
{String} |
'tailwind' |
Priority when merging non-unique colors while using both Tailwind and Sass. |
pretty |
{Boolean} |
false |
Use pretty formatting when writing the JSON file. |
tailwind |
{Object} |
{ ... } |
Set Tailwind options. (See below) |
tailwind.config |
{String} |
'./tailwind.config.js' |
Path to the Tailwind configuration file relative to the project root path. |
tailwind.shades |
{Object|Array|Boolean} |
false |
While set to true , every color shade (100-900 ) will be generated. When set to false , only 500 will be used. Optionally, you may define either an array of shades as strings ['50', '100', '500'] or an object containing shade labels {50: 'Lightest', 100: 'Lighter', 500: ''} . Enabling this option will also enable support for custom palettes. |
tailwind.path |
{String} |
'colors' |
Path to Tailwind config values for palette colors in dot notation. Uses Tailwind's color palette theme('colors') per default. |
sass |
{Object} |
{ ... } |
Set Sass options. (See below) |
sass.path |
{String} |
'resources/assets/styles/config' |
Path to Sass variable files relative to the project root path. |
sass.files |
{Array} |
['variables.scss'] |
An array of files to search for the defined Sass variables. |
sass.variables |
{Array} |
['colors'] |
An array of Sass variables (with or without $ ) to use for the color palette. |
WordPress
WordPress 5.8+
WordPress 5.8 supports a new theme.json configuration file which can automatically load the palette for you from a json file.
If you enable the wp_theme_json
option, and set output
to theme.json
, this plugin will automatically build your palette and write it to that file, no add_theme_support
required, and you get the added benefit of the right classes for block editor support built for you by WordPress.
Vanilla WordPress
The general idea is to file_get_contents()
and json_decode()
the palette and pass it to add_theme_support('editor-color-palette', $palette)
.
Here is an example of doing that:
/**
* Register the initial theme setup.
*
* @return void
*/
add_action('after_setup_theme', function () {
/**
* Enable theme color palette support
* @link https://developer.wordpress.org/block-editor/developers/themes/theme-support/#block-color-palettes
*/
add_theme_support('editor-color-palette', json_decode(file_get_contents('path/to/palette.json'), true));
}, 20);
Sage 10
When using Sage 10, you can take advantage of the asset()
helper to fetch the palette. A good place for doing this would be in setup.php
with the other add_theme_support()
options.
/**
* Enable theme color palette support
* @link https://developer.wordpress.org/block-editor/developers/themes/theme-support/#block-color-palettes
*/
add_theme_support('editor-color-palette', json_decode(asset('palette.json')->contents(), true));
Output Example
$black: '#111';
$colors: (
'red': '#f54242',
'black': $black,
'not-actually-black': '#42f596',
'random-gray': '#858c89',
'white': '#fff',
'blue': '#4287f5',
'orange': '#f5b342',
);
would be transformed to:
[
{ "name": "Blue", "slug": "blue", "color": "#4287f5" },
{
"name": "Not Actually Black",
"slug": "not-actually-black",
"color": "#42f596"
},
{ "name": "Orange", "slug": "orange", "color": "#f5b342" },
{ "name": "Red", "slug": "red", "color": "#f54242" },
{ "name": "Black", "slug": "black", "color": "#111" },
{ "name": "Random Gray", "slug": "random-gray", "color": "#858c89" },
{ "name": "White", "slug": "white", "color": "#fff" }
]
Contributing
Contributions are welcome from everyone. We have contributing guidelines to help you get started.
Todo
- Add tests.
- Split into components.
- Convert to TypeScript?
Community
Keep track of development and community news.
- Participate on the Roots Discourse
- Follow @rootswp on Twitter
- Read and subscribe to the Roots Blog
- Subscribe to the Roots Newsletter
- Listen to the Roots Radio podcast
License
Palette Webpack Plugin is provided under the MIT License.