Update gh-pages with master changes & create some pages.

[sudodoki]

This PR update gh-pages branch with latest commits + adds basic index page for root & docs folders, setups jekyll to exclude submodule *markdown files.
Checked this only locally with jekyll 1.5.1, assume gh-pages aren't being generated for fork projects.

Partially related with reactjs/react-art#3.

[sudodoki]

Just received gh-pages fail note, will troubleshoot this.

[sudodoki]

Did update submodules' paths, no effect, will be contacting github support for this. Sorry for rushing things around.

[sudodoki]

It's working, you can see it on http://sudodoki.github.io/art/ (not very pretty at this moment, but still).
Due to issue with submodules depending recursively on submodules that use git:// links for submodules, ran into forking hell (working on straigthening this out) and decided to settle on removing submodules for now.

[sebmarkbage]

Ideally this would be the same branch as master so that they can be remain consistent and easy to update.

What issues are you running into with the submodules? Are you forking anything in the submodules?

[sudodoki]

Two issues:

1. if you're using gh-pages, your submodules should be using read-only https:// links (I did few forks to bypass that, but it leads to changes in:

• art itself
• slick
• benchmark.js this one seems to be fixed in latest master, so update might just work
• moo-tools runner

2. labeled-modules-spec submodule doesn't exist anymore link.js#8 one of the modules is gone but still dependent.
   Which results in jekyll fail.

[sudodoki]

Maybe you can use bower/npm just to pull files needed & commit them into vendor folder? That will make this so much easier to keep same structure & avoid this problems.

[sebmarkbage]

These projects don't have npm equivalents so there would still be upstream work to be done. Ideally we could switch these out to more modern dependencies.

Could you submit a PR to master with the submodules intact and then an equivalent PR with the submodules commited into their location for gh-pages? At least that allow us to easily track upstream in master and just inline them in the gh-pages branch.

The links on the index page seems to be link to the wrong subfolder since they're not relative...?

[sudodoki]

Okay, I will fix links and do 2 PRs to master & gh-pages branches.

[sudodoki]

They're out in #3 & #2