First off, I am going to start off with saying, that YES, I know we can just go to source and find pretty much anything we want, 95% of the time it’s decently commented. On the flip side, most new devs or even veterans that are using Blueprints don’t have Visual Studio installed. Meh, that’s fine. We have API docs, but they aren’t that great. We do have github though! But, let’s say some devs don’t have access, don’t want it, or just have no clue how to get it.
Epic leans on the community quite a bit for a lot of things, especially fixing broken code or exposing things to Blueprints via plugins. (I am writing specifically for BP because most C++ devs can just look at source at will).
So why aren’t you leaning on us for your official documentation?! Let us **crowdsource **this thing! Yes, we have the wiki, but that’s not what I am getting at. So, with crowdsourcing, anyone OR a selected few in the community would be able to write drafts for official documentation on practically anything. It would go through a review through the Doc Team which will then, after possible revision requests or edits themselves, be posted while crediting the author(s).
An addition to this, I propose a "Needs Update!" button found on each page. If any dev finds a mistake in the documentation, it will get flagged in some queue that either the official doc team or the community doc team can look at.
Let us help you help us.