Docs

Ok, lets document what's going on.

• Components are registered with the site with a github url
• The logic for adding a new component seems to be in this file
• There's also something to do with github api hooks
• The github repo for the component is supposed to contain a package.json file documented at the above link
• The site keeps a list of all registered components -- I think it uses github hooks to know when components are updated. But you can also manually tell it to look at your repo for a new version.
• Crafty has a special function that lets you request a component from the site -- the backend has to know how to respond to these
• Looking at Crafty.modules, the backend just needs to respond with a .js file with a name based on the component and the version you request -- if you tell modules() you want {"Shape":"RELEASE"}, it just requests shape-release.js from the server.