There is already a FAQ area on the developer’s website:
Trouble is, it’s hard to find, hard to use, and the information is pretty sparse and out-of-date.
I think that’s just because the website design is poor. The website needs to be fixed!
And, as I’ve often said, that should be clearly documented in the “mainstream” documentation - not buried in a FAQ.
I do think that a FAQ is a good idea - but it mustn’t be used as an excuse for not fixing “mainstream” documentation…