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.

Having seen this from the other side, you have to be aware that this will only help with prioritization.

If the provider has a hard time delivering because of internal issues, they will still have a hard time delivering with dedicated development resources.

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?

Yep we're going to send that out in next week's email too, but as a 'bonus' lead (as we make sure that for normal leads, no more than 3 people max receive the same lead).

Glad someone spotted that heh!

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.

There is nothing preventing you from using (React) CSS modules & state/props. Use the allowMultiple option if you need more than one classname (base classname + modifier).

You write CSS files and import them in your component. By using Webpack you would do something like this in your component:

    import CSSModules from 'react-css-modules';
    import styles from './styles'; // This is a styles.css file in the same dir
    
    const Component = () => <p styleName="welcome">Hello, world!</p>;

    export default CSSModules(Component, styles);

The stylesheet import is just Webpack doing its thing, using css-loader. Example config: https://github.com/hph/kit/blob/master/webpack.config.js

Sorry if I misunderstood your question.

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?

Yes, exactly - it also produces smaller file sizes and in our experience it's faster.

It's also nice to be able to use classes and integrate with CSS seamlessly when you need to.

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?