Application and Data / Languages & Frameworks / Languages

Decision at StackShare about Emotion, JavaScript, Glamorous, React, HAML, Sass, Inlinecss

Avatar of ruswerner
Lead Engineer at StackShare ·

When we rebooted our front-end stack earlier this year, we wanted to have a consolidated and friendly developer experience. Up to that point we were using Sass and BEM. There was a mix of HAML views, React components and Angular. Since our ongoing development was going to be exclusively in React, we wanted to shift to an inline styling library so the "wall of classnames" could be eliminated. The ever-shifting landscape of inline CSS libraries for React is sometimes difficult to navigate.

We decided to go with Glamorous for a few reasons:

1) Previous team experience with this library 2) We can write our styles in plain JavaScript (which brings many benefits) 3) It supports server-side rendering 4) It has great composition patterns

As you may or may not know, Glamorous has ceased active development and been mostly superseded by Emotion. We are planning to migrate to either Emotion or @styled-components in the near future, and I'll write another Stack Decision when we get there!


11 upvotes·89K views

Decision at StackShare about React, Bootstrap, HAML

Avatar of jeromedalbert
Senior Backend Engineer at StackShare ·

Our legacy HAML pages use Bootstrap as a basic styling framework.

Love it or hate it, but for full-stack developers, Bootstrap is still one of the quickest ways to hit the ground running. All startup websites had to start somewhere, and we are no exception at StackShare!

These days, our frontend team writes or rewrites all our new pages with React components that each have their own CSS styling.

5 upvotes·1 comment·3.4K views