Launch a landing page on your own domain

You bought a domain and you want a page on it. This is one of the most-proven paths in GATE — the walkthrough below follows a real session that went from "I bought the domains" to two live custom domains in about 2 hours 15 minutes, including a mid-build framework change. Your bot handles the technical work; your hands-on steps are describing what you want, picking a mockup, and — if the domain is new to Cloudflare — changing nameservers at your registrar.

Prerequisites

• A bot with the mockups, Cloudflare, and projects skills loaded.
• A GitHub org connected to GATE — same requirements as any project build: the GATE GitHub App installed, and the OAuth App approved if your org restricts OAuth access. See Build & deploy an app for the full checklist.
• A domain — already on Cloudflare, or at a registrar where you can change nameservers.

Three questions your bot should ask first

A good bot settles these before touching a tool. If yours doesn't ask, tell it up front — it saves a rewrite later:

1. Framework? Astro is the default — it covers both static and dynamic pages. Say so up front if you want something specific; otherwise the bot may scaffold a plain static setup and you'll pay for the rewrite once you realize you needed more.
2. New repo or existing? New means the bot creates one; existing means confirm the branch.
3. Is the domain on Cloudflare yet? If yes, it just gets attached to the project. If no, there's a nameserver step at your registrar first (see step 6).

Steps

1. Pitch the page in chat. "I bought wallberg.ai — build me a landing page. Old-money vibe, single screen, no scroll." Style direction up front beats iterating on a finished page.

2. Review mockups before any code ships. Your bot drafts 2–4 visual directions and publishes each one to a shareable mockup URL you can open on any device. Pick the one you want (or mix: "version 2's layout with version 3's colors"). This is the cheapest point in the whole flow to change your mind.

3. The bot sets up the project. Once you've picked a direction, the bot promotes it into a real project: it creates the GitHub repo (or reuses yours), registers the project with GATE, and declares the site's infrastructure in a gate.json file — a single Astro service, in this case. You don't touch any of this; if you're curious what's in that file, see the gate.json reference.

4. First deploy — on a temporary URL. The bot commits the site and deploys it to a GATE-hosted subdomain with TLS handled automatically. Check it there first; it's your staging view before the real domain is attached.

5. Attach your domain. Tell your bot which domains to point at the page ("now put it on wallberg.ai"). The bot attaches each domain to the site and deploys once more — that second deploy is what issues the TLS certificate for the new domain.

6. If the domain isn't on Cloudflare yet, the bot creates the Cloudflare zone and reads back the assigned nameservers — then you set those nameservers at your registrar. That's the one step only you can do.

7. Verify it's actually live. The bot should finish by confirming the domain returns a real page — not just that the deploy "succeeded." Open it yourself on your phone; that's the test that counts.

Troubleshooting

These are the sharp edges hit in real sessions, with the fixes that worked:

• The bot reports the domain is "already linked." Project setup sometimes attaches the domain to the project without tying it to the site. The fix is to detach the domain, re-attach it to the site, and deploy again — tell your bot exactly that and it knows what to do.
• Registrar rejects nameserver changes. Some registrars (Loopia, for some TLDs) fail nameserver edits made through their API, sometimes silently. Change the nameservers manually in the registrar's control panel instead — don't let the bot keep retrying the API.
• One domain serves, another shows a TLS error (HTTP 525). Each domain needs its own attach-plus-redeploy to get a certificate. A domain that's on Cloudflare but was never re-deployed against will show this error — ask the bot to re-deploy with that domain attached.

Going deeper

See Projects & hosting for how deploys and domains fit the bigger picture, and Build & deploy an app when the page grows into a product. When the page is live and the design needs tweaking, edit it live with your bot instead of redeploying blind.