Cloudflare Pages app path

What this demonstrates

The /app/ route is a Cloudflare Pages-hosted application page. It shows how a customer can publish an application landing page as a static frontend asset without running a traditional web server.

The related API endpoint, /api/info, is powered by a Pages Function. Together, these show the Lab 3 pattern: static frontend delivery plus lightweight dynamic behavior running on Cloudflare's network.

Why we built it

This route gives the lab a realistic application destination for the Lab 2 redirect. Users who visit app.ybarra-cflab.com are redirected to this canonical application page.

It also supports the Lab 3 story: Cloudflare Pages can host the frontend, while Pages Functions can add API behavior without requiring the customer to provision, patch, scale, or operate separate server infrastructure.

Demonstrable content

curl -I https://www.ybarra-cflab.com/app/

curl https://www.ybarra-cflab.com/api/info

curl -IL https://app.ybarra-cflab.com

Expected behavior

• /app/ returns this Cloudflare Pages-hosted application page.
• /api/info returns dynamic JSON from a Pages Function.
• app.ybarra-cflab.com redirects to www.ybarra-cflab.com/app/.
• The page supports the Lab 3 architecture of static frontend plus dynamic edge API.

Technical summary

This page is served from the Cloudflare Pages project as a static route under /app/. It acts as the canonical destination for the application hostname redirect configured in Lab 2. It also pairs with the /api/info Pages Function from Lab 3 to demonstrate how frontend content and dynamic API logic can live in the same Pages project.

Customer-facing summary

This page shows how a customer can publish an application landing page globally through Cloudflare Pages and pair it with lightweight backend functionality using Pages Functions. The customer gets a simple, fast, globally delivered application experience without having to manage traditional server infrastructure for this use case.