.gitignore

@@ -18,4 +18,3 @@ notebooks/
 /Makefile
 
 data/
-archive/

DESIGN.md

@@ -1,43 +1,40 @@
 # Theme constraints
-The following general constraints are followed as palette options are mapped
-onto concrete themes:
+The following general constraints are followed as palette options are mapped onto
+concrete themes:
 
 + Harshness levels have monotone differences of a single shade. 
-+ "Hard" themes anchor their background to the most extreme shade appropriate
-  for the scheme (i.e., lightest shade for "light," darkest shade for "dark"),
-  ensuring the palette's "monotone width" is fully spanned by the theme
-  options.
-+ App-specific monotone settings have differences of a single shade compared to
-  the system monotone settings.
-+ Shade differences between corresponding background/foreground settings should
-  be constant (e.g., between `bg0` and `fg3`, `bg1` and `fg2`, etc)
++ "Hard" themes anchor their background to the most extreme shade appropriate for the
+  scheme (i.e., lightest shade for "light," darkest shade for "dark"), ensuring the
+  palette's "monotone width" is fully spanned by the theme options.
++ App-specific monotone settings have differences of a single shade compared to the
+  system monotone settings.
++ Shade differences between corresponding background/foreground settings should be
+  constant (e.g., between `bg0` and `fg3`, `bg1` and `fg2`, etc)
 
-The primary goal of these constraints is to ensure each theme in a collection
-defined around a single palette is 1) sufficiently _distinct_, 2) attains
-sufficient _breadth_ under the palette, and 3) upholds _relative invariance_
-under key properties (e.g., lightness differences).
+The primary goal of these constraints is to ensure each theme in a collection defined
+around a single palette is 1) sufficiently _distinct_, 2) attains sufficient _breadth_
+under the palette, and 3) upholds _relative invariance_ under key properties (e.g.,
+lightness differences).
 
 ![How themes are created](images/theme_creation.png)
 
 ## Example
-The following is a natural solution to these constraints, demonstrated on a
-general example setting: a possible useful analogy is a sliding window that, on
-its own spans a given theme's `bg0-fg0` settings, while globally sliding across
-all available values in the palette. If associating integers `0-10` to indices
-in a list of monotone shades, and `bg-fg` is the syntax used to indicate that
-theme's shade range, we might have the following for dark mode themes across
-harshness levels:
+The following is a natural solution to these constraints, demonstrated on a general
+example setting: a possible useful analogy is a sliding window that, on its own spans a
+given theme's `bg0-fg0` settings, while globally sliding across all available values
+in the palette. If associating integers `0-10` to indices in a list of monotone shades, and
+`bg-fg` is the syntax used to indicate that theme's shade range, we might have the
+following for dark mode themes across harshness levels:
 
 ```
 Dark (system) 0-7 ; 1-8 ; 2-9
 Dark (app)    1-8 ; 2-9 ; 3-10
 ```
 
-There are sliding windows at both the system-app level *and* the
-harshness-level, in a sense. Constraints are followed:
+There are sliding windows at both the system-app level *and* the harshness-level, in a
+sense. Constraints are followed:
 
-+ Harshness levels, separated by semicolon, differ by a single shade from hard
-  to soft.
++ Harshness levels, separated by semicolon, differ by a single shade from hard to soft.
 + The hard theme anchors its background to the darkest available shade.
 + Monotones between system and app differ by a single shade.
 + Differences between bg/fg (value of 7) remains constant across all themes.
@@ -67,53 +64,45 @@ App, light
 ```
 
 # Accent contrast
-Each group of biome monotones have nearly identical (WCAG 2) contrast ratios
-against white/black for all lightness levels (ratios identical between biomes).
-These are selected in a heavily constrained OKLCH context, and given the
-perceptual uniformity attached to lightness, we can expect very similar
-contrast ratios for each accent under a given biome lightness (e.g., the `l65`
-red tone will have the same ratio under the grassland, tundra, and savanna
-monotones).
+Each group of biome monotones have nearly identical (WCAG 2) contrast ratios against
+white/black for all lightness levels (ratios identical between biomes). These are
+selected in a heavily constrained OKLCH context, and given the perceptual uniformity
+attached to lightness, we can expect very similar contrast ratios for each accent under
+a given biome lightness (e.g., the `l65` red tone will have the same ratio under the
+grassland, tundra, and savanna monotones).
 
-In terms of selecting accents for themes (by harshness and scheme), what
-matters is at what lightness level all accent colors meet/exceed a particular
-contrast threshold. Again, the ratios themselves are effectively constant
-across biome monotones, and thus dependent entirely on the monotone lightness
-being used. This of course is determined primarily by whether the theme is a
-light or dark one, and what level of harshness is being used. The following are
-the relevant values for making a decision. We want to ensure all accents can
-reach >4.5 WCAG 2 contrast ratio (the standard requirement for small text on
-the web) against all biome monotones for each theme:
+In terms of selecting accents for themes (by harshness and scheme), what matters is
+at what lightness level all accent colors meet/exceed a particular contrast threshold.
+Again, the ratios themselves are effectively constant across biome monotones, and thus
+dependent entirely on the monotone lightness being used. This of course is determined
+primarily by whether the theme is a light or dark one, and what level of harshness is
+being used. The following are the relevant values for making a decision. We want to
+ensure all accents can reach >4.5 WCAG 2 contrast ratio (the standard requirement for
+small text on the web) against all biome monotones for each theme:
 
-+ For BG l20 (harsh, dark) -> l65 is min lightness where all accents have CR
-  >=4.5
-+ For BG l25 (regular, dark) -> l65 is min lightness where all accents have CR
-  >=4.5
-+ For BG l30 (soft, dark) -> l70 is min lightness where all accents have CR
-  >=4.5
++ For BG l20 (harsh, dark) -> l65 is min lightness where all accents have CR >=4.5
++ For BG l25 (regular, dark) -> l65 is min lightness where all accents have CR >=4.5
++ For BG l30 (soft, dark) -> l70 is min lightness where all accents have CR >=4.5
 
-+ For BG l90 (harsh, dark) -> l45 is max lightness where all accents have CR
-  >=4.5
-+ For BG l85 (regular, dark) -> l45 is min lightness where all accents have CR
-  >=4.5
-+ For BG l80 (soft, dark) -> l40 is min lightness where all accents have CR
-  >=4.5
++ For BG l90 (harsh, dark) -> l45 is max lightness where all accents have CR >=4.5
++ For BG l85 (regular, dark) -> l45 is min lightness where all accents have CR >=4.5
++ For BG l80 (soft, dark) -> l40 is min lightness where all accents have CR >=4.5
 
-For the monotone boundaries (l15 and l95, neither of which are possible
-backgrounds for terminal or nvim in the current theme definitions), the
-relevant lightness levels are l60 and l50, respectively.
+For the monotone boundaries (l15 and l95, neither of which are possible backgrounds for
+terminal or nvim in the current theme definitions), the relevant lightness levels are
+l60 and l50, respectively.
+
+While not necessary, it feels intuitive for us to shift the accent colors up/down by the
+relative change in monotones across harshness levels. This has led to the choice of l60
+accents for the harsh-dark theme, l65 for regular-dark, and l70 for soft-dark. This
+technically breaks the 4.5 ratio requirement, though, for the harsh theme, so you
+ultimately need to pick one: either soften the contrast constraint, or allow different
+harshness levels to use the same accent lightness. I think either is acceptable, but for
+now I've gone with the former, loosening the contrast to a ratio of >4.0 with respect to
+the background. This allows for the slightly tighter group of accent lightnesses:
+l45-l50-l55 for light, l60-l65-l70 for dark. Note that the "center shade" of the l15-l95
+shade group is l55, meaning these groups are very central (the light triplet could move
+down by one shade step, but we want these accents to be as bright as we can get away
+with; otherwise, they are extremely dull in the light modes, and we thus don't mind bias
+toward a brighter lightness).
 
-While not necessary, it feels intuitive for us to shift the accent colors
-up/down by the relative change in monotones across harshness levels. This has
-led to the choice of l60 accents for the harsh-dark theme, l65 for
-regular-dark, and l70 for soft-dark. This technically breaks the 4.5 ratio
-requirement, though, for the harsh theme, so you ultimately need to pick one:
-either soften the contrast constraint, or allow different harshness levels to
-use the same accent lightness. I think either is acceptable, but for now I've
-gone with the former, loosening the contrast to a ratio of >4.0 with respect to
-the background. This allows for the slightly tighter group of accent
-lightnesses: l45-l50-l55 for light, l60-l65-l70 for dark. Note that the "center
-shade" of the l15-l95 shade group is l55, meaning these groups are very central
-(the light triplet could move down by one shade step, but we want these accents
-to be as bright as we can get away with; otherwise, they are extremely dull in
-the light modes, and we thus don't mind bias toward a brighter lightness).

FIREFOX.md

@@ -0,0 +1,47 @@
+# Firefox themes
+
+## Default (grays)
+![Monobiome dark](images/firefox/monobiome-dark.png)
+
+[_Monobiome dark_][4]
+
+![Monobiome light](images/firefox/monobiome-light.png)
+
+[_Monobiome light_][5]
+
+## Grassland biome
+![Grassland monobiome dark](images/firefox/grassland-monobiome-dark.png)
+
+[_Grassland monobiome dark_][6]
+
+![Grassland monobiome light](images/firefox/grassland-monobiome-light.png)
+
+[_Grassland monobiome light_][6]
+
+## Tundra biome
+![Tundra monobiome dark](images/firefox/tundra-monobiome-dark.png)
+
+[_Tundra monobiome dark_][8]
+
+![Tundra monobiome light](images/firefox/tundra-monobiome-light.png)
+
+[_Tundra monobiome light_][9]
+
+## Savanna biome
+![Savanna monobiome dark](images/firefox/savanna-monobiome-dark.png)
+
+[_Savanna monobiome dark_][10]
+
+![Savanna monobiome light](images/firefox/savanna-monobiome-light.png)
+
+[_Savanna monobiome light_][11]
+
+
+[4]: https://addons.mozilla.org/en-US/firefox/addon/monobiome-dark/ 
+[5]: https://addons.mozilla.org/en-US/firefox/addon/monobiome-light/ 
+[6]: https://addons.mozilla.org/en-US/firefox/addon/grassland-monobiome-dark/ 
+[7]: https://addons.mozilla.org/en-US/firefox/addon/grassland-monobiome-light/ 
+[8]: https://addons.mozilla.org/en-US/firefox/addon/tundra-monobiome-dark/ 
+[9]: https://addons.mozilla.org/en-US/firefox/addon/tundra-monobiome-light/ 
+[10]: https://addons.mozilla.org/en-US/firefox/addon/savanna-monobiome-dark/ 
+[11]: https://addons.mozilla.org/en-US/firefox/addon/savanna-monobiome-light/ 

README.md

@@ -2,13 +2,13 @@
 `monobiome` is a minimal, balanced color palette for use in terminals and text
 editors. It was designed in OKLCH space to achieve perceptual uniformity across
 all hues at various levels of luminance, and does so for _five_ monotone bases
-and _five_ accent colors (plus one gray "default"). Each of the monotone base
+and _five_ accent colors (plus one grey "default"). Each of the monotone base
 colors (named according to a natural biome whose colors they loosely resemble)
 are designed to achieve identical contrast with the accents, and thus any one
-of the options can be selected to change the feeling of the palette without
+of the four can be selected to change the feeling of the palette without
 sacrificing readability.
 
-![Theme preview](images/repo_preview_four_split.png)
+![Theme preview](images/repo_preview_minimal.png)
 _(Preview of default light and dark theme variants)_
 
 See screenshots for the full set of theme variants in [THEMES](THEMES.md) (also
@@ -43,19 +43,20 @@ monotone, not its hue. *(Note that this is not generally the case; at a fixed
 lightness level, the contrast between two colors depends on their hue.)*
 
 ## Concrete themes
+![Light biomes](images/light_code_caps.png)
+*(Default light theme variants)*
 
-![Split view of Alpine and Tundra biomes](images/theme-split-view.png)
-
-*(Light and dark theme splits of Alpine and Tundra biomes)*
+![Dark biomes](images/dark_code_caps.png)
+*(Default dark theme variants)*
 
 Themes are derived from the `monobiome` palette by varying both the monotone
 hue (the "biome") and the extent of the background/foreground lightness (the
 "harshness"). This is done for both light and dark schemes, and in each case
 accent colors are selected at a lightness level that ensures each meet a
 minimum contrast relative to the primary background. The following diagram
-shows each of the 36 resulting combinations:
+shows each of the 24 resulting combinations:
 
-![Diagram of the 36 available concrete theme options](images/themes.png)
+![Diagram of the 24 available concrete theme options](images/themes.png)
 
 The "soft" harshness level uses monotone shades closer to the mid-shade
 (lightness level 55), whereas "hard" harshness uses shades further from it.
@@ -73,10 +74,10 @@ Note how theme elements are mapped onto the general identifiers `bg0-bg3` for
 backgrounds, `fg0-fg3` for foregrounds, and `gray` for a central gray tone. The
 relative properties (lightness differences, contrast ratios) between colors
 assigned to these identifiers are preserved regardless of biome or harshness
-(e.g., `bg3` and `gray` are _always_ separated by 20 lightness points in any
+(e.g., `bg3` and `grey` are _always_ separated by 20 lightness points in any
 theme). As a result, applying `monobiome` themes to specific applications can
 effectively boil down to defining a single "relative template" that uses these
-identifiers, after which any of the 36 theme options can applied immediately.
+identifiers, after which any of the 24 theme options can applied immediately.
 
 Read more about how themes are created in [DESIGN](DESIGN.md).
 
@@ -89,67 +90,69 @@ applications.
 Each of the files in the `app-config/` directory are named according to
 
 ```sh
-<harshness>-<biome>-monobiome-<mode>.<ext>
+<harshness>-<biome>-monobiome-<mode>.<config>
 ```
 
-For example, `monobiome-tundra-dark-soft.vim` is the Vim theme file for the
+For example, `soft-tundra-monobiome-dark.vim` is the Vim theme file for the
 dark `tundra` variant with the soft harshness level.
 
-## Applications
-- `kitty`
+## `kitty`
+Find `kitty` themes in `apps/kitty`. Themes can be activated in your
+`kitty.conf` with
 
-  Find `kitty` themes in `app-config/kitty`. Themes can be activated in your
-  `kitty.conf` with
-  
-  ```sh
-  include <theme-file>
-  ```
+```sh
+include <theme-file>
+```
 
-  Themes are generated using the [`kitty` theme
-  template](templates/apps/kitty/templates/active.theme).
+## `vim`/`neovim`
+Find `vim`/`neovim` themes in `apps/nvim`. Themes can be activated by placing a
+theme file on Vim's runtime path and setting it in your `.vimrc`/`init.vim`
+with
 
-- `vim`/`neovim`
+```sh
+colorscheme <theme-name>
+```
 
-  Find `vim`/`neovim` themes in `app-config/nvim`. Themes can be activated by placing a
-  theme file on Vim's runtime path and setting it in your `.vimrc`/`init.vim`
-  with
-  
-  ```sh
-  colorscheme <theme-name>
-  ```
+## `vim-airline`
+If you use [`vim-airline`][2], you can find statusline themes in
+`apps/vim-airline`. Place a theme file in the `airline` theme folder, and
+activate it in your `.vimrc`/`init.vim` with
 
-  Themes are generated using the [`vim` theme
-  template](templates/apps/nvim/templates/theme.vim).
+```sh
+let g:airline_theme='<theme-name>'
+```
 
-- `fzf`
+## `fzf`
+In `apps/fzf`, you can find scripts that can be ran to export FZF theme
+variables. In your shell config (e.g., `.bashrc` or `.zshrc`), you can source
+these files to apply them in your terminal:
 
-  In `app-config/fzf`, you can find scripts that can be ran to export FZF theme
-  variables. In your shell config (e.g., `.bashrc` or `.zshrc`), you can source
-  these files to apply them in your terminal:
-  
-  ```sh
-  source <theme-file>
-  ```
+```sh
+source <theme-file>
+```
 
-  Themes are generated using the [`fzf` theme
-  template](templates/apps/fzf/templates/active.theme).
+## Firefox
+Find links to install available light/dark Firefox themes for each biome in
+[FIREFOX](/FIREFOX.md). You can also download raw XPI files for each theme in
+`apps/firefox/`.
 
-- Firefox
+![Default monobiome](images/firefox/default-split.png)
+*Default monobiome*
 
-  Firefox themes for all monotone backgrounds are publicly listed as [Mozilla
-  add-ons][2], and switch between light/dark schemes based on system settings.
-  You can also download raw XPI files for each theme in `app-config/firefox/`,
-  each of which is generated using the [Firefox `manifest.json`
-  template](templates/apps/firefox/templates/none-dark.manifest.json).
+![Grassland monobiome](images/firefox/grassland-split.png)
+*Grassland monobiome*
 
-  ![Firefox theme previews](images/firefox/themes.png)
+![Tundra monobiome](images/firefox/tundra-split.png)
+*Tundra monobiome*
+
+![Savanna monobiome](images/firefox/savanna-split.png)
+*Savanna monobiome*
 
 # Switching themes
 [`symconf`][3] is a general-purpose application config manager that can be used
 to generate all `monobiome` variants from a single palette file, and set themes
-for all apps at once. You can find example theme templates in
-`templates/groups/theme`, which provide general theme variables you can use in
-your own config templates.
+for all apps at once. You can find example theme templates in `apps/symconf`
+which provide general theme variables you can use in your own config templates.
 
 For instance, in an app like `kitty`, you can define a template like
 
@@ -202,5 +205,4 @@ biome/harshness/mode. This can be done for any app config file.
 
 
 [1]: https://github.com/isa/TextMate-Themes/blob/master/monoindustrial.tmTheme
-[2]: https://addons.mozilla.org/en-US/firefox/collections/18495484/monobiome/
 [3]: https://github.com/ologio/symconf

THEMES.md

@@ -1,11 +1,10 @@
 # Themes
-The currently available theme variants across biomes (`default`, `grassland`,
-`tundra`, `savanna`), harshness (`hard`, `default`, `soft`), and scheme
-(`light`, `dark`) are shown below, displaying a few lines from a Python file in
-Neovim.
+The currently available theme variants across biomes (`default`, `grassland`, `tundra`,
+`savanna`), harshness (`hard`, `default`, `soft`), and scheme (`light`, `dark`) are shown
+below, displaying a few lines from a Python file in Neovim.
 
-You can find the 24 raw screenshots for each theme in `images/theme_caps` under
-the repository root (with filenames `<harshness>-<biome>-<scheme>.png`).
+You can find the 24 raw screenshots for each theme in `images/theme_caps` under the
+repository root (with filenames `<harshness>-<biome>-<scheme>.png`).
 
 ## Default (gray) variants
 ![Default light and dark variants](images/biome_variants/default_variants.png)

colors/monobiome.toml

@@ -0,0 +1,219 @@
+[default]
+l15 = "#0b0b0b"
+l20 = "#161616"
+l25 = "#222222"
+l30 = "#2e2e2e"
+l35 = "#3a3a3a"
+l40 = "#484848"
+l45 = "#555555"
+l50 = "#636363"
+l55 = "#717171"
+l60 = "#808080"
+l65 = "#8f8f8f"
+l70 = "#9e9e9e"
+l75 = "#aeaeae"
+l80 = "#bebebe"
+l85 = "#cecece"
+l90 = "#dedede"
+l95 = "#eeeeee"
+l98 = "#f7f7f7"
+
+[badlands]
+l15 = "#0f0909"
+l20 = "#1b1413"
+l25 = "#27201f"
+l30 = "#332c2b"
+l35 = "#403837"
+l40 = "#4d4644"
+l45 = "#5b5352"
+l50 = "#696160"
+l55 = "#786f6e"
+l60 = "#877e7c"
+l65 = "#968d8b"
+l70 = "#a59c9a"
+l75 = "#b5abaa"
+l80 = "#c5bbba"
+l85 = "#d5cbca"
+l90 = "#e5dbda"
+l95 = "#f6ecea"
+l98 = "#fef4f2"
+
+[chaparral]
+l15 = "#0f0a07"
+l20 = "#1a1511"
+l25 = "#26211c"
+l30 = "#322d28"
+l35 = "#3f3935"
+l40 = "#4c4642"
+l45 = "#5a544f"
+l50 = "#68625d"
+l55 = "#76706b"
+l60 = "#857f7a"
+l65 = "#948e88"
+l70 = "#a49d98"
+l75 = "#b3ada7"
+l80 = "#c3bcb7"
+l85 = "#d3ccc7"
+l90 = "#e4ddd7"
+l95 = "#f4ede7"
+l98 = "#fcf5ef"
+
+[savanna]
+l15 = "#0c0b06"
+l20 = "#171611"
+l25 = "#22221c"
+l30 = "#2f2e28"
+l35 = "#3b3b34"
+l40 = "#484841"
+l45 = "#56564f"
+l50 = "#64645d"
+l55 = "#72726b"
+l60 = "#818179"
+l65 = "#909088"
+l70 = "#9f9f97"
+l75 = "#afaea7"
+l80 = "#bfbeb6"
+l85 = "#cfcec6"
+l90 = "#dfded6"
+l95 = "#efefe7"
+l98 = "#f8f7ef"
+
+[grassland]
+l15 = "#080c09"
+l20 = "#131713"
+l25 = "#1e231f"
+l30 = "#2a2f2b"
+l35 = "#373c37"
+l40 = "#444944"
+l45 = "#515752"
+l50 = "#5f6560"
+l55 = "#6d736e"
+l60 = "#7c827d"
+l65 = "#8b918b"
+l70 = "#9aa09b"
+l75 = "#a9b0aa"
+l80 = "#b9c0ba"
+l85 = "#c9d0ca"
+l90 = "#d9e0da"
+l95 = "#eaf1ea"
+l98 = "#f2f9f3"
+
+[tundra]
+l15 = "#090b10"
+l20 = "#13161b"
+l25 = "#1f2227"
+l30 = "#2b2e33"
+l35 = "#373b40"
+l40 = "#44484e"
+l45 = "#52555c"
+l50 = "#60636a"
+l55 = "#6e7278"
+l60 = "#7d8087"
+l65 = "#8b8f96"
+l70 = "#9b9fa5"
+l75 = "#aaaeb5"
+l80 = "#babec5"
+l85 = "#caced5"
+l90 = "#dadee6"
+l95 = "#eaeff6"
+l98 = "#f3f7fe"
+
+[red]
+l15 = "#1e0100"
+l20 = "#300302"
+l25 = "#440604"
+l30 = "#590b07"
+l35 = "#6e110b"
+l40 = "#85160f"
+l45 = "#9d1a13"
+l50 = "#b42219"
+l55 = "#ca2f24"
+l60 = "#dc4234"
+l65 = "#e95949"
+l70 = "#f37060"
+l75 = "#fa897a"
+l80 = "#fea294"
+l85 = "#febab0"
+l90 = "#ffd2ca"
+l95 = "#fee9e5"
+l98 = "#fff4f2"
+
+[orange]
+l15 = "#140801"
+l20 = "#221203"
+l25 = "#311c08"
+l30 = "#42260a"
+l35 = "#54310d"
+l40 = "#673c0c"
+l45 = "#7c4706"
+l50 = "#905201"
+l55 = "#a45e03"
+l60 = "#b76b0c"
+l65 = "#c97920"
+l70 = "#d98937"
+l75 = "#e79a51"
+l80 = "#f1ad6f"
+l85 = "#fac18f"
+l90 = "#fed5b3"
+l95 = "#ffead9"
+l98 = "#fbf6f1"
+
+[yellow]
+l15 = "#0c0c03"
+l20 = "#181709"
+l25 = "#242211"
+l30 = "#312f19"
+l35 = "#3e3c20"
+l40 = "#4c4928"
+l45 = "#5b572e"
+l50 = "#6a6535"
+l55 = "#79743d"
+l60 = "#888346"
+l65 = "#989250"
+l70 = "#a7a15f"
+l75 = "#b7b170"
+l80 = "#c6c182"
+l85 = "#d5d19a"
+l90 = "#e4e1b4"
+l95 = "#f2f0d2"
+l98 = "#f8f8eb"
+
+[green]
+l15 = "#010f03"
+l20 = "#041c09"
+l25 = "#0b2911"
+l30 = "#14361a"
+l35 = "#1c4524"
+l40 = "#25532e"
+l45 = "#2e6337"
+l50 = "#377242"
+l55 = "#42824e"
+l60 = "#4f925a"
+l65 = "#5da268"
+l70 = "#6eb178"
+l75 = "#80c089"
+l80 = "#94cf9c"
+l85 = "#a9ddaf"
+l90 = "#beecc4"
+l95 = "#d9f8dc"
+l98 = "#edfcee"
+
+[blue]
+l15 = "#010924"
+l20 = "#041336"
+l25 = "#091f49"
+l30 = "#112b5d"
+l35 = "#1a3771"
+l40 = "#234485"
+l45 = "#2d5299"
+l50 = "#3860ac"
+l55 = "#456fbe"
+l60 = "#557ecc"
+l65 = "#658ed9"
+l70 = "#799ee3"
+l75 = "#8daeeb"
+l80 = "#a2bef2"
+l85 = "#b7cff9"
+l90 = "#cedffc"
+l95 = "#e6efff"
+l98 = "#f3f7fe"

generate.sh

@@ -1,17 +1 @@
-rm -rf app-config/*
 symconf -c templates/ generate -o app-config
-
-cd app-config/firefox
-shopt -s nullglob
-for f in *; do
-  [[ -f $f ]] || continue
-  name=${f##*/}; name=${name%.*}
-  bsdtar -cf "$name.xpi" --format zip -s ':^.*$:manifest.json:' -- "$f"
-done
-
-# consolidate firefox artifacts
-rm *.manifest.json
-rm hard-* soft-*
-rm *-light.*
-perl-rename 's/^([^-.]+)-([^-.]+)-([^-.]+)-([^-.]+)\..*\.xpi/$2-$3.xpi/' *
-