Better describe the accents and shades, and showcase them better in the web UI
I'll preface this issue by saying i have only used the Web UI so far. Oh, and what a great project!

I am currently having to brute-force my way through when using the web UI to make my theme, which is an indication of a underlying problem: The lack of intention for each shade and accent

Specifically `accent1` has no other description than "syntax", and is not  showcased at all in the code preview in the web UI. It also seems like the literals in the code preview are colored by `accent0`, which have the description "error, vcs deletion" description. Some colors are both used in the foreground and in the background, making it hard to create a cohesive color experience.

I propose the following:

* Add code examples for more languages.
  Of interest are languages with explicit typing
* Add a terminal example more user can easily recreate locally.
  This makes for a better reference.
* Switch around some of the accents for better consistency, more on that below
* The shade colors should not be used as both foreground (text) and background colors, there should be a clearly defined separation. Perhaps reserve shade 0, 1 and 2 for background and the rest for foreground colors?

While at it, I suggest the following descriptions from either what I've observed to be their primary use, or what i think they should changed into:

|     color | current description       | proposed description                | note |
| ---------:| ------------------------- |:----------------------------------- |:----:|
|  `shade0` | background color          | background color                    |      |
|  `shade1` | UI                        | UI shading, borders                 |  1   |
|  `shade2` | UI, text selection        | UI shading, text selection, buttons |  2   |
|  `shade3` | UI, code comments         | code comments                       |      |
|  `shade4` | UI                        | UI hints                            |      |
|  `shade5` | UI                        | UI titles                           |  3   |
|  `shade6` | foreground text           | secondary foreground text           |      |
|  `shade7` | foreground text           | primary foreground text             |      |
| `accent0` | error, vcs deletion       | error, vcs deletion                 |      |
| `accent1` | syntax                    | ???                                 |  4   |
| `accent2` | warning, vcs modification | warning, vcs modification           |      |
| `accent3` | success, vcs success      | literals, success, vcs success      |      |
| `accent4` | syntax                    | success, vcs addition               |      |
| `accent5` | syntax                    | syntax, control flow                |  5   |
| `accent6` | syntax, caret/cursor      | syntax, directives                  |      |
| `accent7` | syntax, special           | syntax, types, constants            |      |

Notes:
1. currently used as the font color in the editor ruler                                                                                                                      
1. borders currently use this, perhaps move borders to `shade1`? The terminal example also use this color alot, which i believe misrepresents the normal terminal experience 
1. currently used as the editor ruler highlight and the color of the unordered list                                                                                          
1. I have seriously no idea where this is used                                                                                                                               
1. is currently the text-selection color in the web UI, even though `shade2` is supposed to be this going by the current description                                         

They should indicate what the colors will be used for in the templates. And also indicate for the template authors where they should use the colors.

This does not have to be the "hard" definition, but perhaps be more like a common guideline. The 'notes' column however is worth noting, since they describe why the current situation confuse me.

I understand a lot of this came as baggage from base16 schemes
