How do we create a "prototype" component set

[JedWatson]

Would be good to get a prototype implementation in place first with the simplest / easiest-to-replace solution we can think of.

Not sure if there's a way realistically to extend it in the framework examples, but ideally each implementation concentrates on just the styling differences and is otherwise equivalent.

[mxstbr]

I was thinking of structuring it like this:

comparisons
- examples         # examples of specific methodologies
  - aphrodite
    - common       # same files for all methodologies, maybe slightly different build process
      - components
      - config
    - components   # components that'll have differences
      - NavBar.js
      - NavItem.js
  - jss
    - common
    - components
  - css-modules
  - etc

[mxstbr]

@MicheleBertoli totally took care of that and made it a great setup in #10, will now factor out all the common stuff (babelrc, eslintrc, utils) to a shared folder for all examples to use!