Host docs at terasology.io?

[oniatus]

I would propose to host the docs as github page directly on http://www.terasology.io/ before we move to a developer community page where we can then embed the docs together with a devblog or tutorials. The main reason is that i want to use https://oniatus.github.io for different content, e.g. a small blog and move the documentation page to a more visible location.

Proposed tasks (in order):

• [x] 1. Create a new org repo, e.g. terasologydocs.github.com (naming like https://github.com/MovingBlocks/movingblocks.github.com) for the new github page
• [ ] 2. Add a jenkins job to publish TerasologyDocs on master updates to the github page. This requires python (e.g. available via https://wiki.jenkins.io/display/JENKINS/ShiningPanda+Plugin) and the build command from the repo doc (https://github.com/MovingBlocks/TerasologyDocs#build)
• [ ] 3. Add a javadoc job to build the engine develop javadoc and publish the result also to the new github page (see: https://github.com/MovingBlocks/TerasologyDocs#javadoc-location).
• [ ] 4. Map http://www.terasology.io/ to the github page from terasologydocs.github.com
• [ ] 5. Change the javadoc location and the edit-on-github locations in the doc repo to the new page
• [ ] 6. Replace all migrated wiki pages from https://github.com/MovingBlocks/TerasologyDocs/issues/1 with their respective documentation links to avoid double editing
• [ ] 7. Remove the documentation page from https://oniatus.github.io

I can do 1, 5, 6, 7. For 2 ,3, 4 the assistance of someone with jenkins and domain power is needed (waves @Cervator ) :D

[Cervator]

I made https://github.com/MetaTerasology/metaterasology.github.io since I think that'll make an org level page repo we can easily redirect to terasology.io :-)

I figured we'd end up something like this:

• terasology.org -> the org page repo for MovingBlocks, general landing site
• terasology.io -> the org page repo for MetaTerasology, dev specific site
• terasology.net -> the org page repo for Terasology, module specific site (@pollend: ping!)

Made a webteam on MetaTerasology and added you, threw in Owner rights for the org for good measure, that should let you do anything

Python is already installed on the Jenkins master (v2.6.6) would that work?

You're now also a Jenkins admin so about the only thing I might need to do is try and remember where I have terasology.io registered so we can point it somewhere :D