public/
Static HTML, CSS, JavaScript, and assets.
Cloudflare Pages example
kodeklaus .dk
A small static site with the full path left visible: source files, a Pages project, a production deploy, and DNS on Cloudflare.
Deployment flow
Four plain pieces, wired together.
npm run deploy
Wrangler uploads the static folder.
Cloudflare Pages
The `kodeklaus` project serves the files.
kodeklaus.dk
A proxied CNAME points the domain at Pages.
Project shape
Nothing hidden behind a framework.
Write the static files
Edit `public/index.html`, `public/styles.css`, and `public/script.js`.
public/
Check the output
The check script confirms that the files Cloudflare serves are present.
npm run check
Preview like Pages
Wrangler serves the same `public/` folder locally before deploy.
npm run dev
Deploy production
Cloudflare receives the static folder and serves it from the Pages edge.
npm run deploy
Cloudflare settings
The production setup is deliberately small.
These are the values needed to recreate this deployment from the repo. The DNS record points `kodeklaus.dk` at the Pages project.
- Repository
- fhestvang/kodeklaus
- Production branch
- main
- Build command
- npm run check
- Build output directory
- public
- DNS record
- CNAME kodeklaus.dk -> kodeklaus.pages.dev