I think the OP meant something more monthly-newsletter-like “hey, we have added this and this service to the recommended, while this service lost out trust (linking blog). Over than that there is a new guide for X Y Z, check them out”
The releases page and associated RSS feed is indeed the best way to stay up to date with changes to the website.
I don’t know about the sections thing. Currently the release notes are automatically generated, which saves us a good amount of time and keeps things at least consistent. Manually writing notes just so they’re a bit cleaner is pretty low priority for us at the moment. We do try to bold the biggest changes in each release if applicable.
The world is constantly changing. For example, one of our recommended gift card marketplaces, Cake Pay, shut down yesterday out of the blue. Adjusting that recommendation doesn’t lower the quality of Privacy Guides, and we don’t have a crystal ball to predict the future of the privacy landscape.
It is not surprising that Cake Pay, a service that is less than a year old, has shut down. The question arises as to why such a new service was recommended initially, considering that it had not proven its reliability over time.
It might not lower the quality but it does impact the accuracy and reliability of the site. After all, what’s the point of receiving recommendations if they cannot be relied upon for 5+ years?
Privacy Guides is a living document and the recommendations change often over time, because the best tools at any given moment change over time. There is no perfect setup that never changes.
This being said, I did want to use the blog to post things like news about other projects, big changes to recommendations, etc., but the rest of the @team was strongly against posting things like that for various reasons