I agree with your overall sentiment, insofar as that the ratio of suggestions that are approved and rejected to that which has been unattended (as in unlocked and unsolved posts with no tags) is alarming to me. If these were GitHub issues or PRs, I would be concerned. Maybe this is why the website moved to the forum here? I’m not too sure on its history.
Anyway, from the looks of it, Privacy Guides has changed focus from being a guide/tool listing website to being a media/news outlet. Because of this, their work definitely goes beyond what you simply called reviewing HTML contributions. Their employees seem to be hired for their content creation (@em being a writer, @jordan and @nateb being video creators). Blog articles, news articles and videos are part of their work, as well as weekly livestreams. And for those who are not employed by Privacy Guides, they have their own work, personal, and possibly educational lives to attend to. Such is life in the world of open source. This also does not include the work being done on existing approved changes. It would make sense that they would have difficulty in reviewing community suggestions and implementing them. Comparing a small online project like Privacy Guides with Red Hat, which has thousands of employees, is unfounded. While I agree with your overall concern, I don’t think you or anyone should abandon the project. Don’t throw out the baby with the bathwater.
Outdated and misinformation goes a long way, unfortunately (see: Avoiding the next Skiff), which is precisely why vetting information is important.
I hope it does not seem like I am dismissing your criticism. I am in fact for it. If so much work is being done elsewhere as I have described, new and dedicated staff should be hired to review and implement community suggested changes to the website. Either this, or there must be a change in the process for how community suggestions are reviewed and implemented. At the end of the day, community suggestions will keep piling on and on. The more it does, the more difficult it will be for the team to review them all (and the more smaller yet valid suggestions there will be that go under the radar).
Unfortunately I don’t think it will be possible in the near future to hire any new staff, let alone a dedicated staff. The staff writer @em has recently confirmed that they were laid off due to lack of the project’s funding. Without a good flow of cash, the Privacy Guides team will slowly diminish back into volunteers only. And as we know with open source projects, volunteer-only is unfortunately evermore slow.