Yeah, I consider it just as much as community responsibility to document the various features of Armory engine, especially considering that it actually is open source and everyone is free to have a look at the source code. - In any case, at least for my own part, I've been spending some time looking at documenting the various screen effects (bloom, grain, motion blur, tonemapping etc.) and providing examples, making a personal roadmap to shader/filter improvements - my biggest problem is my own annoyances with the gitbook editor (not to mention getting my account banned on gitbook after 2 minutes ).
If you feel like needing some help documenting the nodes, I'm also willing to help
In general, if anyone wants to feel helping out documenting:
- 1. Make a GitHub account and fork https://github.com/armory3d/armory_docs
- 2. Clone the fork down to your local drive (I'm using GitHub for Windows)
- 3. Open the fork/clone folder using Gitbook Editor https://www.gitbook.com/editor
- 4. Begin editing WYSIWYG instead of editing manual markup code that I wasted a lot of time on
- 5. Profit??? (by helping the community)