casesandberg

If you choose to stick with your existing provider, you can negotiate a service contract where the provider hires and manages engineers that work exclusively on your account. We did this in the past with pretty good success. We were planning to exit in 1-2 years and didn't want to invest in an entirely new platform or build it ourselves when we knew the acquiring company would end up rolling up our service into their existing platform/infrastructure.

Not super great that this has Sentry analytics in it...

We are working on a variety of different software solutions, CompanyOS being one of them! Right now our software is only available to our clients.

Why not hire for the 1.0 version through pipeline?

But how does that work if this translates everything to traditional CSS?

Yes! The static version of the site is an in-between, with more complex documentation coming soon!

<span className={css(styles.blue, styles.small)}>

vs

<span style={ styles.button }>

One of the biggest differences between ReactCSS and other solutions is that all of the style merging is done in the style object and not in the HTML. This keeps the markup clean and puts all style and style logic in one place.

React CSS Modules does not allow you to use props or state to style your component. Say you wanted to use a button <Button color="#aeee00" /> you could map the color prop directly to CSS.

Is it possible to use state or props in the CSS though? How does it handle that? Say I wanted the color of a title to be controlled via props, how would I do that with your solution?

IMO it makes it easier for devs that dislike CSS to make sweeping changes due to all of the relevant styles being in one place.

So it translates everything back to CSS, is that how it handles hover and pseudo classes?