Another update - documentation!I've done a first big round of overhaul primarily of our main wiki: https://github.com/MovingBlocks/Terasology/wiki Many pages were culled with no survivors, not even the children were spared. Oh the humanity. My condolences to the families, and to any contributors whose work was affected in the massacre. Some pages that faced the axe didn't really have any problems themselves, they might even have been useful, they were just out of place since comparable pages didn't exist for many similar topics, yet writing them all up would make the wiki way too bloated.We went from 73 pages to 34 and there is more to go. Idea is much as with the engine itself - tear everything out that could go into a module, or in this case alternatively in an appropriate library repo instead. We shouldn't necessarily dig deep into how assets work in the engine wiki - that's a better job for gestalt-asset's repo/wiki. Behavior trees, pathfinding, old crafting system etc - all exiled to an appropriate alternative repo/wiki. Plenty of links and Google results are now broken, but this is the time to do it before officially going v1.0.0 with the engine.Another great option here is to do more tutorial repos like TutorialWorldGeneration . I consider that really the gold standard for how to do it - kudos again to @Josharias for starting it and @msteiger for adding in. We should do that for more topics like registering a new asset type, creating and importing a creature model from Blender, and so on. Much better than just having a random few pages in the engine wiki. The Sample repo could also use a few more basics. And a bunch of simple tutorials could probably live in the same place. Best part: Eventually we can involve automated testing to make sure the tutorials are up to date, or their tests will break.The engine should just be about the engine, and really most of that is getting extracted too (mainly Gestalt). Other than that we should do some general intro and link everywhere. That's the main bit left - overhauling some of the central pages, cutting them down in size, and making better detail pages elsewhere. Or ideally use third party guides since we shouldn't really need to explain how to use Markdown or the finer details of Git, there are great guides on GitHub for both of those.Other topics included stuff that's global to our organization entirely, like coding conventions, how to do unit testing / JavaDoc, and so on. Those don't really have a home at present, but I'm thinking they should, somewhere they can be referenced in brief from other repos. This counts for some plain repo files like the CONTRIBUTING file (now also available in the engine repo) as well - that could easily bloat yet duplicate many other versions from other repos. Instead we should have a really brief one that links to a central location.In the end the engine wiki will probably be pretty minimal. It'll also be easy to maintain rather than a mess of different topics at different levels of quality and completeness.I also merged in a code of conduct - thanks to @MaloJaffre for pushing it along after I mentioned it as an idea in the past. I don't think there's anything particularly controversial in it, pretty much all is common sense / political correctness we just want to cover so it has been said somewhere. If anybody disagrees or has issues with it please let me knowI made a new abuse@terasology.org forward to make complaints but don't really expect we'll ever get any. For now it just points to me and does a quick auto-respond. Let me know if anybody else wants a forward from there too, just in case.I'm still planning for the automated documentation types (JavaDoc, Modding API, etc) and thinking about where to best put it all. Am thinking a gh-pages branch per repo to hold generated doc per release on top of a very thin foundation. I tested the size impact on a repo from repeatedly dumps of automated documentation (even images!) and it is surprisingly small. Second I might try an Iota sort of comprehensive index repo to browse documentation from many different places in one clean structure + the general pages like code conventions that don't go in a single functional repo.Edit: Oh, I made a copy of the old wiki in a new repo: https://github.com/MovingBlocks/TempDoc - just in case. Also to see how pushing a wiki repo to a normal repo would work.