Setup and operations
Deploying a White Page from a ZIP Archive
A ZIP is a deployment artifact, not proof that its page is safe, complete, or suitable for the campaign.
Inspect the archive before upload
List files, confirm the intended entry document, and reject absolute paths, parent traversal, unexpected executables, symlinks, or secrets. Ensure file names work on the target hosting environment, including case sensitivity.
Validate a self-contained build
Open the extracted page in an isolated preview and check scripts, styles, images, fonts, navigation, and forms. Replace development-only URLs and confirm required assets are included rather than loaded from a private workstation.
Review the published page itself
Check title, language, responsive layout, disclosures, destination links, and any collection of user input. Page review remains an editorial and security responsibility even when an automated builder produced the files.
Publish with version identity
Associate the archive with a known White Page record and deployment target, then preserve its build or version identifier. Avoid overwriting the only working artifact without a recoverable previous deployment.
Verify from the public flow
Load the hosted page over HTTPS on mobile and desktop, inspect every asset request, test unknown paths, and trigger the flow outcome that selects it. Confirm rollback restores the earlier public version and event behavior.