Support astroturf

[kettanaito]

What:

I suggest to consider support of astroturf.

Why:

• It's a promising zero runtime CSS-in-JS solution, that a lot of developers can benefit from
• It has a Component API, just as the one that atomic-layout operates internally

How:

1. Release stable pluggable styling API
2. Ship astroturf as one of the possible styles producers:

import styled from 'astroturf'
import Layout from 'atomic-layout'

Layout.configure({
  produceStyles: styled, // api is experimental and subjected to change
})

3. Write integration test suit for astroturf

[kettanaito]

Beware of the downsides when thinking about integrating Astroturf:

It also means we sacrifice:

- A fine-grained style mapping to props. Props map to classes, its all very BEM-y but automated
- Dynamism in sharing values between js and css
- A unified JS-only headspace, you still need to think in terms of JS and CSS

[kettanaito]

Although the library's core is not dependent on neither rendering nor styling solution, I will postpone any style/rendering-agnostic ideas for now. There are other features to prioritize rather than allowing different CSS-in-JS solution.

styled-components is one of the most commonly used styling libraries, so I don't feel an immediate urge to switch from it, or allow a different solution.