> Ideally, someone compiles a numbered list from this thread with actionable > issues or action items and we create an issue/documentation roadmap from this.
What I'd suggest is a #docs (and a #bugs) room in discord. Even if everyone's not there, it serves as an easily searchable appendix for the first complaints that people have with documentation, and discussion about that, with more serious complaints naturally resulting in action (issues, PRs) after there's agreement on them, and other complaints still findable to be kept in mind as docs are revised. Compared to a wiki: similar low barrier of entry _on raising issues_ , but you don't have to worry about the documentation degrading due to haphazard edits. Compared to issues: 1) it has a much lower barrier of entry. You can say "hey isn't this confusing? ... oh you're right, I missed that part. Thanks." and feel better than having an issue closed, and you can say "hey isn't this confusing?" without feeling obliged to explain precisely what you would prefer to the current language. 2) it's less provocative. An issue wants to be responded to by someone who will fix the problem. Complaints in a chat can start as complaints. And of course, PRs have an even higher barrier as they have to come with a solution, when someone who can easily solve a problem might not see a problem to begin with. And you can hang the divio link there.
