Sass

Sass Discussions

Discover why developers choose Sass. Read real-world technical decisions and stack choices from the StackShare community.Showing 6 of 10 discussions.

Julien DeFrance

Principal Software Engineer at SmartZip

Feb 24, 2019

Needs adviceon

Bootstrap

Less

Sass

Which #GridFramework to use? My team and I closed on Bootstrap !

On a related note and as far as stylesheets go, we had to chose between #CSS, #SCSS, #Sass , Less Finally opted for Sass

As syntactically awesome as the name announces it.

0 views0

Comments

Zarema Khalilova

Frontend Team Lead at Uploadcare

Dec 4, 2018

Needs adviceon

Sass

Less

PostCSS

We in our #Frontend team prefer to use the modern and clean syntax of #CSS instead of Sass or Less. On bundle step, we use post-processing by PostCSS to add prefixes, minify code, uploading assets and more. PostCSS get CSS more powerful, it‘s a fantastic tool.

0 views0

Comments

Lee Benson

Nov 30, 2018

Needs adviceon

React

GraphQL

Apollo

ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

0 views0

Comments

Russel Werner

Lead Engineer at StackShare

Sep 13, 2018

Needs adviceon

Sass

HAML

React

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!

#inlinecss

0 views0

Comments

glfead

May 1, 2015

Needs adviceon

Sass

I use sass only to @import my components to have a better readability than all stuff put in one page of css Sass

0 views0

Comments

Chesley Brown

Lead Programmer at RentChek

Dec 14, 2014

Needs adviceon

Sass

Makes our CSS very maintainable by allowing for easily creating logical folder structures, variables and reusable mixins. Sass

0 views0

Comments

Sass Discussions

Discover why developers choose Sass. Read real-world technical decisions and stack choices from the StackShare community.Showing 6 of 10 discussions.

Julien DeFrance

Principal Software Engineer at SmartZip

Feb 24, 2019

Needs adviceon

Bootstrap

Less

Sass

Which #GridFramework to use? My team and I closed on Bootstrap !

On a related note and as far as stylesheets go, we had to chose between #CSS, #SCSS, #Sass , Less Finally opted for Sass

As syntactically awesome as the name announces it.

0 views0

Comments

Zarema Khalilova

Frontend Team Lead at Uploadcare

Dec 4, 2018

Needs adviceon

0 views0

Nov 30, 2018

Needs adviceon

0 views0

Lead Engineer at StackShare

Sep 13, 2018

Needs adviceon

Sass

HAML

React

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

#inlinecss

0 views0

Comments

glfead

May 1, 2015

Needs adviceon

Sass

I use sass only to @import my components to have a better readability than all stuff put in one page of css Sass

0 views0

Comments

Chesley Brown

Lead Programmer at RentChek