Security Headers and Event Routes Hardened Public Sites

As the first production sites came online, they needed a safer, more predictable baseline. Public sites now gain stronger security headers, event-instance route improvements, compressed responses, and sorting fixes for search and event endpoints, so early production sites load more predictably and carry a safer default security posture while the custom-theme architecture continues to evolve.

Operational work with tangible outcomes

For customer launches, these are improvements with direct effects: pages load more predictably, event routes are easier to wire, and public responses carry safer default headers. These are the changes that matter most once real traffic arrives on a production site.

A safer baseline before launch

Security header defaults mean teams approaching their first launch do not need to audit each page individually. The baseline is set correctly from the start, and teams can focus on content and editorial work rather than infrastructure concerns.