Iridesceux Site Operations

How to deploy, stage, edit, test, cut over, and verify the corporate site without touching the visual design.

Deploy Iridesceux staging from the monorepo

Create another Pages project

Workers & Pages → Create Pages project

Connect the same private repository used by Command.

Use exact build settings

Build configuration

Root directory

public-site

Framework

None

Build command

exit 0

Output directory

public

Expected: The staging *.pages.dev URL loads.

Test every public route before domain cutover

Staging URL

At minimum open Home, About, Brands, History, Privacy Center, Terms, Accessibility, Copyright, Connect/forms, Help, Newsroom/Blog, Search, and any launch-specific page.

Test forms using disposable data

Staging

Submit creator/advertising/support test entries and verify the server-side route stores/sends them as intended. Do not assume the “Thank you” UI means the backend succeeded.

Verify legal/privacy links

Staging

Every public footer/legal path must resolve. The HVN duplicates should redirect to Iridesceux where designed.

Using Site Studio safely

Open Command → choose Iridesceux in the site selector.
Use Site Studio for approved text/image/link/alt-text changes only.
Preview the change before publishing.
Never paste javascript:, protocol-relative URLs, or unreviewed scripts into content fields.
Publish one small change first, then verify it on the staging/public site.
Record the change in the release/audit workflow.

Use Code Studio only when the change genuinely requires code and the operator is a Technical Admin or Super Admin.

Production-domain cutover

Do not attach/switch the public production domain simply because staging works. Use document 14. Before cutover, freeze nonessential changes, identify the rollback commit/deployment, verify legal pages and forms, and then attach the domain through the Pages Custom domains flow.

If a domain is already serving a coming-soon site, treat the cutover as an intentional launch event. Do not casually replace its DNS record during routine testing.

Official reference: https://developers.cloudflare.com/pages/configuration/custom-domains/

Post-deploy smoke test

Check	Pass condition
Homepage	Loads on desktop/mobile; no broken hero media.
Navigation	All primary links resolve.
Forms	One test submission arrives/records correctly.
Privacy/legal	All linked documents open.
Search	Returns expected indexed pages.
404	Unknown route returns branded 404, not raw platform error.
HTTPS	No certificate warning or mixed-content failure.