Cloudflare Handbook

Deploy cb-website with Cloudflare Pages

Connects the private cloudberrie-studio/cb-website repository to Cloudflare Pages, tests the pages.dev deployment, and prepares the custom domain.

Document: INF-205Type: RunbookStatus: ApprovedOwner: Cloud EngineeringVersion: 4.2.0Updated: 2026-07-17

Approved deployment values

Setting	Value
GitHub organization	`cloudberrie-studio`
Repository	`cb-website`
Production branch	`main`
Project name	`cb-website`
Initial URL	`cb-website.pages.dev` or available equivalent
Custom domain	`cloudberrie.com` after validation

Determine the build type first

Current repository observation: the committed site includes root-level index.html, additional HTML pages, assets, robots.txt, and sitemap.xml. Treat it as a static site unless a package.json and build process are present.

Project type	Build command	Output directory
Static HTML at repository root	Leave blank	`/` or the Cloudflare field’s root/default option
Next.js static export	`npm run build`	Usually `out`, based on project configuration

Procedure

Cloudflare dashboard → Workers & Pages.
Create an application / Pages project and connect to Git.
Authorize the Cloudflare GitHub application for the cloudberrie-studio organization and the selected repository.
Select cb-website and main.
Enter the correct build values from the table above.
Deploy.
Open the generated pages.dev URL.
Validate every page, image, navigation link, robots.txt, sitemap.xml, privacy, and terms pages.
Only then add the custom domain.

Production validation

Homepage and mobile layout work. EventLumi and Needle Needs pages work. No development secrets or .env files are deployed. HTTPS is active. A new GitHub push triggers a deployment. Custom domain is added only after pages.dev approval.