DNS, Cloudflare proxy, and origin reachability
Established the foundational hostname and Cloudflare DNS/proxy configuration so the site could be reached through Cloudflare rather than directly through the origin.
Open Lab 1Cloudflare hosted project
Edge, DNS, routing, Pages, Functions, and cache behavior in one clean lab site.
This project demonstrates a progressively built Cloudflare lab environment for validating DNS, proxy behavior, redirects, Cloudflare Pages, Pages Functions, static assets, response headers, diagnostics, and cache-related behavior.
4
Completed labs
3
Utility pages
1
Cloudflare Pages site
Edge
Cloudflare delivery model
Completed Lab Summaries
Each lab has its own dedicated page with demonstrable content where applicable, plus both a technical summary and a customer-facing explanation.
Redirect behavior and hostname consolidation
Implemented and validated redirect behavior so traffic could be routed cleanly from the app hostname to the canonical web hostname and path.
Open Lab 2Cloudflare Pages and Pages Functions
Added Cloudflare Pages hosting and validated static routing, application paths, and serverless Pages Function responses.
Open Lab 3Cache, headers, static assets, and diagnostics
Isolated cache and diagnostic content into a dedicated lab so cache testing does not sprawl across unrelated landing, app, or previous lab pages.
Open Lab 4Static asset check
This verifies that the static asset link is clean. There should be no trailing backslash after
/static/logo.txt.