Tim Kelty

@ganey hadn't considered that bit yet – good point

I have some I just need to publish. I know https://github.com/trunkclub has a few as well.

https://github.com/trunkclub/suitcss-components-form https://github.com/trunkclub/suitcss-components-table https://github.com/tgfjt/suitcss-components-starratings

It seems a component should always stand alone, so to me, consistency between component's variables isn't that important. I usually end up something like: ``` :root { --App-gutter-size: 20px; }...

@simonsmith Yeah independent would be most analogous to how we've been doing things. I only suggested fixed because its easier to manage. Your `Grid`/`Button` example is a perfect example of...

> I presume Lerna makes this easy too? Good question. Haven't done that yet. Seems like we might want to have branches for majors (4.x, 5.x), so you can jump...

If we go with fixed - I think we'll prob want to do what babel did when they converged - take the highest version of any of the independent packages...

No I think they do hold back changes that would be breaking, to keep a sane major release history, so that's another drawback. Ya know, talking this over theres probably...

Sounds like monorepo is unanimous! The biggest decision is deciding if we want to do fixed/locked versioning or independent: https://github.com/lerna/lerna/#fixedlocked-mode-default Lets work here; https://github.com/suitcss/suit/issues/151

@simonsmith: > PostCSS ecosystem Yeah…I guess what I was envisioning was using it more for a development > Media prefixing for components Yep, I agree solutions like react-media are better,...