Some feedback from a new user:
The lack of documentation in some places has been the most frustrating part of using Discourse so far. If there were a way for the community to contribute to a simple documentation site (like sphinx/readthedocs), I’d help write some of documentation as I figure things out. The documentation could be updated to point to the most relevant and current forum threads here for those tasks.
It would be useful to have one canonical entry point for learning how to build more complex plugins (not just “hello world”). A list of where to start looking for answers to common tasks would be useful. The sidebar for the API docs is a good example. At the moment, information is scattered over many different forum posts, and it’s difficult to find. Asking people who are new to Ruby, Rails, and Ember to “just read the code” creates a significant barrier to entry for many.
Example: I want to override the log out functionality on Discourse (to add a POST request to another URL on-logout) but don’t know where to look. I searched Github for Ruby files that handle log out and only found this, and it isn’t clear how I would override the functionality there. I’m too new to Ruby, Rails, and Ember to understand how it’s all wired together, so something that would only take a few hours with documentation ends up taking up days of time. It’s not just reading the information that takes time – it’s mostly figuring where to even find it among years of scattered forum posts for various different versions and configurations of the software.