create separate vendor directory for 3rd party assets

[yanne]

I started to play around with some enhancements to search. This means writing own javascript, which I think should be separated from 3rd party files. With flask, it's easiest to put the own js sources under static also. Thus put the vendor files under vendor/ dir.

[yanne]

I actually first missed the possibility to have blueprint specific static files under the blueprints themselves. However, there might still be reason to have application wide helper code under rfhub/static/

[boakley]

Thanks, Yanne!

I need to think about this. While I like the idea of separating out vendor-specific stuff, I almost think it makes more sense to have a slightly different layout. For example, instead of static/vendor/css/bootstrap... and static/vendor/js/jquery/..., we eliminate the css and js folders. For example, have /static/vendor/jquery, /static/vendor/bootstrap, etc. This makes it easier to upgrade because we can just dump vendor code in one place without having to separate it all out into javascript and css.

Thoughts?

[yanne]

that might also make sense, although it makes it a bit more cumbersome to add js libraries that are distributed as a single minified js file. One additional option would be to use a tool like browserify to manage the dependencies, although that might be overkill at this point.

[yanne]

Actually, I will close this issue and do a separate PR for the last two commits (which are useful on their own)

We can decide on rfhub/static structure later when the decision is actually needed.