I recommend the following:

  * Creating a simple wiki server in Nim (possibly backed by 
[Fossil](https://en.wikipedia.org/wiki/Fossil_%28software%29)), in similar 
style and UX as this forum (but Markdown support would be great).
  * Moving all content from [the GitHub 
wiki](https://github.com/nim-lang/Nim/wiki) to the new Nim wiki.
  * Some static nim-lang.org content can be copied to the new wiki for managing 
edit proposals.
  * Auto-creating stub / skeleton wiki pages for all Nim modules (stdlib and 
nimble), and encouraging users to add content.
  * Auto-linking from the generated Nim documentation to wiki for more info.
  * Adding a compiler / linter error / warning / message ID link to the wiki, 
so people can get more info.
  * Importing some useful third party blog posts, How-Tos, etc into the wiki.
  * Enhancing both the new wiki package and this forum with more features, 
integrating the two with complementary features: the wiki is for refined 
neutral-PoV articles and the forum is for subjective conversations.
  * Some especially useful forum posts can be "upgraded" to wiki articles, and 
all wiki pages can have a comments section powered by the forum.
  * Wiki bots can automatically maintain blocks inside wiki pages, like a list 
of other modules that use this module, search results for a given error message 
(ex. on StackExchange and this forum), etc.
  * Creating Nim user [identity provider](https://en.wikipedia.org/wiki/OpenID) 
to share login and profile info between this forum, the wiki, and other future 
Nim-related sites. It can link to profiles on other sites (GitHub, Reddit, 
StackExchange, [etc](https://keybase.io)) to consolidate people's identities.
  * Eventually re-implementing all of GitHub's functionality as more scalable, 
efficient, and genuinely free software written in Nim (including Fossil 
support, etc). ;) 


Reply via email to