You're 100% right we should make it easy for anyone just checking out the project to see the generated results without running the examples. I will add a CLI example and commit the generated policies to the repo.

Thanks for pointing this out and sorry our docs aren't up to the standard they need to be.

We're building OpenPolicy not necessarily to reduce the risk companies have of litigation, but instead to be more transparent with users and to build trust.

In the next version we'll be releasing auto-instrumentation that tracks data/third parties to always keep things in sync.

The best option until now have been generators found online, which mostly seem to have pivoted to lead generators or demos for paid products now. Considering that in Germany, for example, any website affiliated with a company or pursuing any economic purpose is required to have both a proper imprint and privacy policy, this is something you have to care about. There are even lawyers writing specialised crawlers to find websites with linked Google Fonts but no privacy policy notice, and send automated litigation to the owners. This only became possible after a court decided (as shortsighted as stupidly) loading fonts from Google's servers constituted a privacy violation, given that visitors had no way to consent.

Following these changes and reacting in a timely way is a continuous effort, and a framework to automate this is very welcome IMHO.

This was just a small quality of life improvement for the Astro users so it's a huge surprise to see how many reads it's getting.

Hopefully we get the same response next week when we launch 2 very exciting features.