New organization of project resources

[icarofonseca]

I want to propose a new organization for the project's online resources. It will be as follows:

• This repo will be used only for development of the Vessel.js build files.
• A second repo will host the Vessel.js website with all other library resources (examples, ship specifications, STL files, research papers).

Advantages as perceived by me:

• More organization in the resources: the examples folder in this repo is becoming crowded and will become heavier as we aim for more detailed STL models.
• Less entanglement in the development of examples: we will be able to carry development of the main library without being concerned whether it maintains supports to all the examples we developed so far. The examples will be stored in the second repo with the builds used to develop them by the time.
• Better support to the development of our website: the second repo can be used to host the Vessel.js website with GitHub's own "pages" feature, making the current server unnecessary, at least for now (see it in action here). It also provides version control (something our current solution Cyberduck does not, as far as I know) and supports assigning our custom domain (i.e., vesseljs.org) to the page hosted in the repo.

Additionally, @DiogoKramel and I have been working on a script that will allow users to download a .zip with the source files of an example. You can test a prototype here.

[EliasHasle]

The second point is a good one. And so is the proposed solution, I think. But again, there is a lot of reuse in the examples too. Reuse of code for generating ship models and ocean environment. Should that be duplicated for each example too? I suppose it would have to, for unmaintained examples. But there should still be a "canonical" version of each script.

[icarofonseca]

Yes, you are right, there is much interdependence between examples and the snippets such as Ship3D, oceans, etc. In practice what is happening now is that they are being duplicated inside the examples folder. In the future, we may find a better solution to handle this.