Brage Sekse Aarset

Interestingly, there is a div element there containing the correct label, but it's not being rendered as text by the browser. 

In [this example theme](https://indivorg.github.io/theme/), the labels work correctly. The reproduction of the issue lies in the difference between how these two projects are set up. **Some differences** - The Indiv...

I've managed to find a clue: The fontSize of the text is `0` when inspecting in chrome. If I change that to something else the labels show up correctly. ![Screenshot...

Removing `0` from the `fontSizes` array in the theme fixes the issue!

Perhaps we want to change the current behaviour, so that if you have a fontSizes array that starts with the value `0` you can still see the labels. One approach...

I'm working on setting up some unit testing in `style-guide`, and my test outputs this:  Here's the source code: ```ts /** @jsx jsx */...

I have still not managed to pinpoint why this goes wrong, but I have found a fix that works. If I use `getColor` from `@theme-ui/color` instead of `get` from `theme-ui`...

Are there any maintainers who could comment on whether adding the import (`import { getColor } from '../../color/src'`) to `ColorSwatch.tsx` is okay or not? Would the `style-guide` still work if...

In that case I suppose I could write a PR with the fix I described? Or should we rather take this opportunity to investigate why exactly `get()` fails when `getColor()`...

This issue contains two different problems, one of which has been fixed. The other problem that is still unsolved is that when you hoved the color swatches, you see `undefined`,...