Home

Awesome

Deprecation notice

After forking from the original base16, we tried to decide what we wanted the "next generation" version of base16 to look like. Base17 was one of the early iterations. While we may end up going in this direction in the future, we have (currently) decided against this specific iteration. Over time, we plan to add a number of features to our "common scheme format" which would expand it to work like base17, but building it out iteratively rather than all at once.

All your themes, everywhere. <img alt="Color wheel" src="./color_wheel.png" width="100" align="right" style="padding-top:0.6rem;">

Style systems and smart build tooling for crafting high fidelity color schemes and easily using them in all your favorite apps. Originally based on the amazing work of Chris Kempson and his Base16 system.

Features

Documentation and Specification

The builder and styling specs detail how to compile schemes and templates into application specific configurations.

Scheme

A scheme is a fixed palette of named colors and (optionally) instructions for how those colors should be used by apps.

Style

A style guide provides rules governing how a scheme's palette should be applied within apps. This means each color is used consistently for similar purposes across all your apps. Individual styling guides often support different sized pallets and have different ideas about how those colors should be deployed.

See the individual styling guides for more information on each:

A scheme is defined using a YAML file. The file specification is in the Builder Guidelines.

Builder

A builder is a build tool used by various template repositories to generate files based on scheme file and template file.

Template

A template describes how a scheme should be transformed to support a specific application. A template repository defines a template file, then uses a builder to generate application specific files using the template.

Templates often include ready-to-use pre-built versions of every scheme. These are typically installed directly by end users to use the schemes in different applications.

Supported Applications

Supported applications are applications for which a template exists.

Official Templates

We maintain a number of templates. Each has been sponsored by at least one project member who is committed to maintaining that template.

We are open to accepting new projects, though they must still be sponsored by a project member and have some level of activity.

Terminals:

Contrib Templates

In order to prevent ownership issues, we're introducing the concept of contrib templates. These are templates which have been transferred to the organization, but either aren't sponsored by an org member or don't have enough usage to warrent inclusion with our official templates.

Submitting a repository to base16-project-contrib and continuing to work on it is a great way to get involved and get noticed as a maintainer so you can work towards getting added to the project team.

Unofficial Templates

If you have a template you maintain, but don't want to submit it to the contrib repositories, feel free to add a link to the repository here to add it to this list. These are community maintained templates and may not be updated often.

<details><summary><b>Terminals</b> - terminal and shell related templates</summary> <p> </p> </details> <details><summary><b>Editors</b> - templates for use in code editors and IDEs</summary> <p> </p> </details> <details><summary><b>Window Managers</b> - window managers and related utilities</summary> <p> </p> </details> <details><summary><b>Programming</b> - defaults and utils for use when programming</summary> <p> </p> </details> <details><summary><b>Other</b> - various applications which don't fit in other categories</summary> <p> </p> </details>

Adding Support for a New Application

To add your own template, submit a pull request to this repository to add your repository to the "Unofficial Templates" list below in the relevant category. Recommended repository naming scheme: [style-name]-[template-name] (with dashes as separators).

Schemes

To add a Base16 scheme, simply submit a pull request to the base16-schemes repo and add your scheme.

Builders

Normally end-users should not need to use builders, as they're primarily meant for maintainers - both scheme and template maintainers. These are tools used to build templates with all the currently submitted schemes.

Spec changes will not be released until there is consensus among maintainers and at least one builder with a pull request ready for implementing that spec version.

See the CHANGELOG for more information about changes in the spec.

Scheme and Template Author Resources

The following is a list of useful resources for anyone creating a Base16 scheme and or template:

Tools

If you've written a tool feel free to add it to the list below:

Projects

Non-template Themes

Project Chat

Have something you want to discuss, but you're not sure it warrants an issue? Feel free to stop by the #base16 channel on Libera Chat or the bridged Matrix channel to talk about it.

Credits