April 10, 2026
Build fights, privacy nights
Zero-build privacy policies with Astro
Zero‑build or build? Astro privacy tool triggers eye‑rolls and memes
TLDR: OpenPolicy now builds privacy/terms pages directly in Astro without extra plugins, producing static HTML with no browser code. Commenters roasted the “zero‑build” slogan as misleading, questioned whether sites even need a library for rarely changing policies, and demanded real output examples instead of just configuration code.
OpenPolicy just announced a simpler way to generate privacy, terms, and cookie pages inside Astro. No plugin, no generated files, and still no browser JavaScript. The catch? The feature proudly says “zero‑build”… then immediately says “everything runs at build time.” Cue the community side‑eye.
The hottest take was pure semantics warfare. One commenter mocked the tagline with a deadpan: “‘Zero‑build privacy policies’: ‘Everything runs at build time’, what?” Another camp asked the bigger question: do we even need this? As one skeptic put it, if privacy pages rarely change, why add a library when a plain static page works? Meanwhile, confused shoppers opened the “examples” hoping to see an actual policy and found only config code. “Show us the output!” became the rallying cry, with jokes about a Schrödinger’s policy that exists only in config.
Not everyone was mad. A few devs applauded the cleanup—fewer packages, no weird generated folders, and one config for multiple legal pages. But the vibe swung between marketing wordplay outrage and demo‑or‑it‑didn’t‑happen impatience. Bottom line: the tech is neat—compile legal pages at publish time, ship zero client code—but the community wants less slogan, more screenshots, and a clearer pitch on who actually needs this.
Key Points
- •OpenPolicy replaces its Astro plugin with direct in-page compilation of policies, eliminating generated files and the @openpolicy/astro package.
- •Developers define a single, deterministic config using @openpolicy/sdk, covering privacy, cookie, and terms policies.
- •Pages use expandOpenPolicyConfig, compile (from @openpolicy/core), and renderHTML (from @openpolicy/renderers) to produce static HTML at build time.
- •No Astro integration or Vite plugin is required; no client-side JavaScript is shipped.
- •A working example is provided in the repo’s examples/astro directory, and OpenPolicy+ is available for capabilities beyond static generation.