Christopher Chiche ChrisJamesC

Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.

My 3 developers team has just developed React.js application with 7668 lines of CSS (and just 2 !important). During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.

Here are main principles we use to write CSS for modern (IE11+) browsers:

SUIT CSS naming conventions + SUIT CSS design principles;
PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
Flexbox is awesome. No need for grid framework;
Normalize.css, base styles and variables are solid foundation for all components;

	/*
	* This script will download a package (and all of its dependencies) from the
	* online NPM registry, then create a gzip'd tarball containing that package
	* and all of its dependencies. This archive can then be copied to a machine
	* without internet access and installed using npm.
	*
	* The idea is pretty simple:
	* - npm install [package]
	* - rewrite [package]/package.json to copy dependencies to bundleDependencies
	* - npm pack [package]

	#!/bin/bash
	file=$1
	test -z $file && echo "file required." 1>&2 && exit 1
	git filter-branch -f --index-filter "git rm -r --cached $file --ignore-unmatch" --prune-empty --tag-name-filter cat -- --all
	git ignore $file
	git add .gitignore
	git commit -m "Add $file to .gitignore"