Cloudflare Pages + Wrangler: deploy & point the domain
Deploy to Cloudflare Pages from the terminal with Wrangler: a least-privilege token, the www + apex DNS, the apex→www 301, and keeping www the one canonical home.
Field notes on shipping AI you can trust — evals, RAG, agents, and the engineering discipline around them.
Deploy to Cloudflare Pages from the terminal with Wrangler: a least-privilege token, the www + apex DNS, the apex→www 301, and keeping www the one canonical home.
A static site has no backend, so the /book lead form POSTs straight to Web3Forms. The flow, why the access key is public, the honeypot, and cookieless attribution.
We ran Emil Kowalski's design-engineering skill over the site and added the micro-interaction it was missing — press feedback. The before/after, plus why we drew it in SVG, not Remotion.
What GEO is, why answer engines must corroborate your brand as a real entity, and the step-by-step setup: Wikidata, Crunchbase, Clutch, a bidirectional sameAs.
Type pangaea.id, press Enter — and a global relay starts: DNS, anycast, a TLS handshake, a static page from the edge. The whole trip, in plain English.
The technical walkthrough: move pangaea.id's nameservers from Hostinger to Cloudflare without dropping email — the steps, the records to carry, and the dig check.
The technical setup: GitHub Actions → Cloudflare Pages — the project, a least-privilege token, two secrets, and the one-push-to-main release (with the gotchas).
Pick one canonical address: we 301 the bare pangaea.id to www.pangaea.id so all SEO credit lands on one URL — the Cloudflare Redirect Rule, step by step.
The free, layered Cloudflare security baseline — Always Use HTTPS, TLS Full strict, HSTS, CAA records that protect auto-renewal, strict CSP, WAF, Turnstile.
Plain DNS trusts any answer — so it can be forged. DNSSEC signs every record and chains trust from the root to your domain. What it is, how forging works, and how to switch it on.