> 10\. Are you willing to help making Nim documentation better? :) This is half the crux of the matter.
Documentation developed by a committee won't work. It needs **leadership** , but with all of us contributing. (Existing standard Nim doco already has leadership by @Dom and @Araq) **Leadership** is needed for: * driving improvements in each category of documentation (Tutorial, How-To guides, Explanation, Reference, etc) * filling in the blanks of a cookbook * adding more Rosettacode examples, * extending Macro/Template doco (because this is THE most difficult thing to document, although @Araq is already leading the way here, it will need a lot of work) * keeping consistency across various documentation mechanism, as well as within the same mechanism (e.g. Standard Library Modules) * identifying where documentation should go, reducing double-ups and providing cross-references (e.g., between Tutorial, How-To guides, Explanation, Reference) I see leadership as including * promoting (asking for help, keeping everyone aware of what is still needed, feedback on progress, etc) * gate-keeping (arbitrating between different contributions and ideas) * maintaining standards
