Update example apps

[damassi]

Adds a few more examples to the repo:

• Basic: Excludes all SSR functionality. How one would use the lib in an everyday client-side app. (I've updated the main README with simple and SSR examples so the different emphases come across.)
• Server-side Rendering: Bare-bones SSR example.
• Gatsby: For folks using Gatsby, figured -- why not?
• Kitchen Sink: Renamed the old /example folder. I think we should try to steer people to the the basic and bare bones SSR examples first and then the kitchen sink example after. For people who are already familiar with the lib this is the perfect reference doc for whatever they may need but I worry about less advanced users becoming overwhelmed / confused.

Todo

• Once Make interactions optional #82 is merged, publish new version of fresnel without interactions requirement and then update examples with pointers to lib rather than ../ relative references to code -- babel + ts doesn't like it.

(As an aside, I fell in a serious babel / compiler worm hole trying to figure out ^... When using babel-node, or node -r @babel/register, it's not easy to compile code below the root location where process.cwd() lives (where node booted up). Things just don't want to work and there is a lot of ambiguity around how to address the issue online... Easier to steer clear 😓 and install from the package when needing to compile stuff server-side.)

[alloy]

Excellent stuff, @damassi! 👏 🙌

(As an aside, I fell in a serious babel / compiler worm hole trying to figure out ^... When using babel-node, or node -r @babel/register, it's not easy to compile code below the root location where process.cwd() lives (where node booted up). Things just don't want to work and there is a lot of ambiguity around how to address the issue online... Easier to steer clear 😓 and install from the package when needing to compile stuff server-side.)

Perhaps this should be using yarn workspaces? Because I do think examples should use local code, not published out-of-sync [with local lib] code.

[damassi]

Perhaps this should be using yarn workspaces

Agree; can set this up in a follow-up PR.

[pepopowitz]

🙏 These are great!!! They helped me understand the usage a lot.

I left a few very minor suggestions.

[alloy]

There’s a broken link here /~https://github.com/artsy/react-responsive-media/pull/81/files#diff-04c6e90faac2675aa89e2176d2eec7d8R317

[damassi]

Alright, one more look when y'all get a sec 😄 Addressed remainder of feedback.

[alloy]

Almost there!!

Additionally, I noticed this sentence in the README:

However, this approach suffers from a few flaws when used in conjunction with server-side rendering (SSR)

And would like to replace ‘flaws’ with something less loaded. Perhaps something like:

However, this approach has some limitations for what we wanted to get out of server-side rendering:

?

[alloy]

I took the liberty to address my own feedback, so that I could start the rename work.

[damassi]

Thanks for the review everyone!