improve friendliness of developing resources

[ahdinosaur]

right now it's not friendly to develop resources.

when developing from within the 'resources' repo:

• you have to constantly rm -rf the resources cache that pops up, otherwise the resource module will use that cache instead of the repo resouces
• you have to sudo npm link && npm link resources which is confusing

when developing from within an app:

• you lose the ability to version control alongside 'resources' repo
• if you then develop in 'resources' repo, npm link it, you still have to rm -rf the resources you want overridden by the repo every time you make a change, because of the resources cache.

my solution is to focus development on a 'resources' repo

• an app is just a resource in this 'resources' repo
• the big binary should be meant for being run within 'resources' repos
  • creating docs, packaging on resource in repo should be easy using big binary
• running the app should be done by starting the resource, using the big binary
• no more cache, as there is no more difference between app resource and other resources. if you want to make a new app with new resources, fork the 'resources' repo.

[juliankrispel]

:+1:

Wouldn't it be nice if we could just use use with a development resource that isn't inside the node_modules or resources folder as well?