Except for @Arkinn s work, documentation is literally very much not taken into consideration. In professional environments documentation would pop up in a Definition of Done list, this list would give requirements before any task is marked completed and would include things like time tracking, testing.
Now I know that documentation would ask a lot of time from the core team and with lots of changes planned for the stable version this is not likely something that makes sense to commit to with such a fluctuant code base. Especially when their responsibility at this point is to continue their recently rediscovered pace of development towards a stable release.
Perhaps it makes sense for community driven extension development guides. In fact this was something that the original Flagrow team planned to do but never really got to.
