- 993000800 - Adventure Express Exit
- 993000700 - Adventure Training Camp
- 889100000 - Entrance - Snow Man's Land
- 889100010 - Entrance - Snow Man's Land
- 889100020 - Entrance - Snow Man's Land
- 820000000 - Event Hall
- 889100002 - Exit - Snow Man's Land
- 889100012 - Exit - Snow Man's Land
- 889100022 - Exit - Snow Man's Land
- 889100100 - Path to Snow Man's Land
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 6561
lines of CSS (and just 5 !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;
- No DRY. It does not scale with CSS, just focus on better components;
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
### Keybase proof | |
I hereby claim: | |
* I am inumedia on github. | |
* I am inumedia (https://keybase.io/inumedia) on keybase. | |
* I have a public key whose fingerprint is 7CD0 D8F2 9AF0 1A8C 50A8 3266 A631 12CA 4198 25E5 | |
To claim this, I am signing this object: |