Website

Close #102
Close #103
Close #113

Author: MoOx

.babelrc

@@ -0,0 +1,3 @@
+{
+  "stage": 0
+}

.eslintrc

@@ -1,12 +1,30 @@
 ---
+# babel support more syntax stuff than eslint for now
+parser: babel-eslint
+
 ecmaFeatures:
   modules: true
+  jsx: true
 
 env:
   es6: true
   browser: true
   node: true
 
+globals:
+  # for docs
+  __DEV__: true
+  __PROD__: true
+  __SERVER_PROTOCOL__: true
+  __SERVER_HOSTNAME__: true
+  __SERVER_PORT__: true
+  __SERVER_HOST__: true
+  __SERVER_URL__: true
+  __LR_SERVER_PORT__: true
+
+plugins:
+  - react
+
 # 0: off, 1: warning, 2: error
 rules:
   # max 80 chars per line
@@ -50,3 +68,17 @@ rules:
 
   # enforce comma at eol (never before)
   comma-style: [2, "last"]
+
+  # see globals
+  no-underscore-dangle: 0
+
+  # eslint-plugin-react rules
+  react/no-multi-comp: 2
+  react/prop-types: 2
+  react/display-name: 2
+  react/wrap-multilines: 2
+  react/self-closing-comp: 2
+  react/no-did-mount-set-state: 2
+  react/no-did-update-set-state: 2
+  react/jsx-uses-react: 2
+  react/jsx-uses-vars: 2

.gitignore

@@ -2,6 +2,7 @@ node_modules
 
 # standalone build
 dist
+docs/dist
 
 # fixtures
 test/**/*.actual.css

.travis.yml

@@ -14,3 +14,7 @@ notifications:
     on_failure: always
     use_notice: true
     skip_join: true
+
+script:
+  - npm run test
+  - npm run docs-test

CONTRIBUTING.md

@@ -0,0 +1,29 @@
+## Contributing
+
+_cssnext uses a lot of [postcss](https://github.com/postcss) plugins,
+so you might need to take a look at them if you find an issue or want to create
+or enhance a feature._
+
+Otherwise, fork, work on a branch, install dev-dependencies,
+respect coding style & run tests before submitting a bug fix or a feature.
+
+```console
+$ git clone https://github.com/YOU/cssnext.git
+$ npm install
+$ npm test
+$ git checkout -b fix.bug423
+```
+
+### Add a feature
+
+1. Add test files (input + expected output) in [`test/fixtures/features`](test/features)
+- If the feature can affect some others, update [`test/fixtures/cases/example.css`](test/cases/example.css) to test integration with other features
+- Run test, & check tests are broken (otherwise feature is useless)
+- Choose a pretty simple and clear name (that match the specs)
+- Add the feature in the [README features list](#features) (title, link to spec, link of the plugin, short desc)
+- Add the feature in the [README node.js options list](#features-default-all-features) (camelCaseName)
+- Add the dependency in the [`package.json`](package.json)
+- Add the feature in the source (in [`index.js`](index.js)), in the appropriate place (order matter)
+- Run test and be happy
+- Add feature in [the docs](docs/content)
+- Add feature on [the playground](https://github.com/cssnext/playground) example