Public
Use public pages for broad campaigns, announcements, and pages meant to be easy to share.
Governed Quickpages
Quickpage gives publishers the controls they need to share pages confidently and see what happens after launch.
quickpage deploy ./site launch "Launch" --access dac --root
Governance is part of the publishing path, not a separate maze. Choose access, add controls when needed, and keep runtime secrets out of page content.
Use public pages for broad campaigns, announcements, and pages meant to be easy to share.
Use unlisted pages for targeted sharing when the URL should work but the page should stay out of anonymous indexes.
Use DAC-only pages when the audience belongs behind organizational access through Easy Auth.
Runtime-safe publishing
Use passwords for limited previews, expiry dates for time-boxed campaigns, and view limits when access should be intentionally constrained.
Controlled publishing flows can use shared admin tokens or scoped publisher tokens for user-prefixed pages.
Runtime secrets belong in Key Vault, not in the page. Campaigns can connect to approved services without exposing credentials.
Quickpage analytics endpoints help teams track traffic, compare page performance, and make follow-up decisions with first-party data.
Access tiers, publisher tokens, runtime secrets, page limits, and analytics all live in one service.