Serving web content.
WHAT IT PROVIDES
Static content served from a delivery network Automatic certificates Custom domains Rewrites to server-side functions or containers Preview channels for testing
WHAT IT SUITS
Single-page applications Static sites Web applications with server-side rendering through rewrites
WHAT PREVIEW CHANNELS PROVIDE
A temporary address serving a build, for review before release.
WHY THAT IS USEFUL
Reviewers see the actual thing, not a description.
WHAT TO CONFIGURE
Caching headers appropriate to each file type Rewrites, so client-routed paths resolve Redirects, for moved content Security headers
WHY THAT SECOND POINT
Without it, entering a deep address directly returns not found.
WHAT TO SET FOR ASSETS
Long cache durations, with versioned filenames.
WHAT TO SET FOR THE ENTRY DOCUMENT
Short or no caching.
WHY
So a new release is picked up.
WHAT TO VERIFY AFTER DEPLOYING
Deep addresses work Assets load with current versions Certificates are valid
WHAT TO MONITOR
Bandwidth, which is billed.
