Reorganize's project structure in order to ease the integration process 

Hi Bradvin,

Awesome project! I love that you are using data attributes to semantically add behaviour to HTML structures. I think this is a very good start and I have no doubts that once more plugins appear this is going to replace Datatables in many projects :)

I am going to use Footable for a new project and I am going to be using Ruby on Rails. In RoR we usually package our assets, like FooTable, in Gems. This makes installing and updating assets something very seamless and pretty much automatic. I will be packaging FooTable in a gem at [this repo](https://github.com/Nerian/FooTable-rails).

Rails expects things to be organized in a specific way. A convention. This pull request structures your assets following that convention. It would be awesome if you could merge these changes, since this will save me countless hours each time I want to update the Gem with your code changes :sweat_smile:

I changed the url of assets in the demo HTML files to point to the new locations of said assets. The icons url doesn't match, because I set the url to be relative from the 'assets' folder. We can fix that if you use [Jekyll](https://github.com/mojombo/jekyll) to build these pages.

Let me know what you think.

Thanks!