In order to have a well documented API we need to describe what each class, struct, enum and method responsibilities are and how to use it.

Hi,

Thanks for your effort in maintaining this amazing project. I've recently started playing with it and I would like to know in detail what is the workflow that I should follow in order to extend your project.

The current documentation is really minimal and unfortunately I would like to do something more than just adding a new scene. In particular, I would appreciate to see how I can debu

A new user might presumably do this:

const draggable = new Draggable(pointerEvents);
const spring = new Point2DSpring();
const tossable = new Tossable({ draggable, spring });

and wonder why nothing is happening. Perhaps interactions that take user input should throw warnings if their output isn't being used (at least in a dev mode).

Add examples that test the waters of the usefulness of this so-called "component system".

Ideas for examples:

• Basic posts example on bl.ocks.org
• Spinner
• Stopwatch Example #26
• Counter Example #27
• Todos Example #28
• Scatter Plot with menus for X and Y
• Timer
• Stopwatch + Timer with Redux
• [todomvc](https://github.com/reactjs/redux/

anything network related or that can be different between dev, stage, prod should not be in git because they have to be changed with each move

perhaps move all that stuff to .env or start removing the clevis.json and hiding it from git?

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

**Environment (please