> So finally, please help our 3rd party libraries with their documentation! I > bet no matter if it's a UI library or an ORM or scientific computing -- they > could all need serious help for their documentation.
I agree with this sentiment! I'd say Nim docs are pretty solid now and a good starting point for somebody knowing atleast 1 programming language. But currently I find the docs pretty average in "discoverability"/UX, Rust does this very well with <https://docs.rs>/ , it's an unified experience or something like hexdocs: <https://hexdocs.pm/phoenix/overview.html> where it's easy to distinguish content from navigational elements. So I'd say the content is there and people are working hard on improving it, but maybe some better visual cues for the docs could make for a better doc experience too. Blogposts / write-ups / This Month in Nim all add to better discoverability too. So I like those ideas too, it's just...lack of manpower, how we coordinate blogposts could be something like how F# does it: <https://sergeytihon.com/2020/10/22/f-advent-calendar-in-english-2020>/ a small window where we ask people to write up what cool stuff they do in Nim and then publish it on the website. We don't have to pick a month and publish 30 days in a row, a better balance can be found.
