I guess this is kind of the goal, actually, the idea would be that people would start by contributing to this community wiki, and then team members can look through the community wiki and re-post some content on the website if it is really good and broadly applicable.
One of the reasons for this is that articles on the website need to be formatted in a very particular way, and should be highly polished for consistency. There is just a level of quality people inherently expect when reading anything published on privacyguides.org.
Frankly, this means that with many community PRs, they need to be (nearly entirely) rewritten before we feel comfortable posting it. Which is fine! It is still insanely useful for us to receive community PRs that are researched, and we just have to rewrite it to make sure it is clear to all audiences and consistently formatted, it does save us a lot of time.
Unfortunately, it does also still take us a lot of time to do these edits and rewrites, and I feel bad when some PR authors have to wait (sometimes very long) periods of time for their PR to be merged, because the information is usually good and just sitting there (so obviously they are excited to get it merged and read), but just not in a state where we feel comfortable with putting it in front of everybody and expecting them to understand it well.
This would allow people to immediately publish good privacy-related information quickly and in a format they prefer, for the benefit of people in the community who really need information on a pretty niche topic; and also give us time to go through and rewrite community wiki guides into articles that are at the level expected by readers of the website.
Can you elaborate on what you see the downsides of this approach to be?