Just adding some thoughts about what should be in the wiki and what should be in the user/developer documentation.
The FAQ contains some basic factual information (weight, dimensions, specification of the phone) that should really be in the documentation, though it hasn’t always been easy to keep it up-to-date. For these things the wiki works well as a way of quickly updating known information. Solid, fixed, factual information belongs in the documentation and in the wiki. If you think that you would have expected to find the information in the documentation, it probably belongs in the documentation somewhere.
Having said that, some things are probably better placed on the wiki: the cellular providers page is always going to be subject to change. There are some questions related to use cases (using Bluetooth devices, convergence, Android apps) that the documentation probably should cover but are outside the core experience – these are either essential or just nice-to-have depending on your perspective. Some of these things can’t go in the documentation if they promote non-Free solutions, so that’s also a factor.
Some items in the FAQ are more like advocacy: things like the reasoning behind a decision, or how good something is. These are more opinion-based and are probably a bit borderline for an FAQ. You will collectively have to decide what you think is appropriate. I wouldn’t put those things in the official documentation, and that’s one of the reasons why there is a community wiki.
There are also technical bits and pieces that I wrote a long time ago before various features were implemented. Those were supposed to form the basis for developer documentation and were published in the wiki before official interfaces and components were created for those features.
You can always create issues and merge requests for things that should (also) exist in the documentation. The GitLab interface lets you edit files in the browser and anyone with an account on GitLab should be able to create merge requests and issues for the developer documentation and the user guide.