Skip to content
Launch Sites
Open the repo

Internal tool · KVSocial

Describe the page. Merge it. It's live.

Launch Sites turns one message to Claude into a reviewed product landing page on its own domain: designed, built from shared components, previewed on the pull request and deployed to Cloudflare.

For the KVSocial team. No Cloudflare account needed.

claude

Make a landing page for Meetvio on meetvio.launchkv.com

Read CLAUDE.md and the new-site skill

npm run new-site -- meetvio --domain meetvio.launchkv.com

ui-ux-pro-max → style, palette, type, layout

Built from @launch/ui: Hero, Steps, FeatureGrid, FAQ, CTA

npm run validate ✓ npm run build

gh pr create → "Add meetvio landing page"

Preview link lands on the PR. Merge to go live.

Example: asking Claude Code for a landing page, from request to pull request.

How it works

From request to live page in four steps

  1. Step 1: Ask

    Tell Claude the product, the domain and where the main button goes. It asks for anything missing.

  2. Step 2: Claude builds

    It scaffolds the site, picks a design system with ui-ux-pro-max and builds the page from shared sections.

  3. Step 3: Review the preview

    Claude opens a pull request. A teammate checks the preview link and asks for changes in plain words.

  4. Step 4: Merge, it's live

    Merging deploys to Cloudflare Pages and sets up the domain and DNS for a new site automatically.

Features

Built for shipping many launches

One system for every product page, so each new launch is faster than the last.

  • One repo, every product

    Each product is a folder. Sites build and deploy independently, so one can't break another.

  • Shared sections

    Hero, steps, features, FAQ and CTA sections are ready to use. A new site mostly sets its brand.

  • Preview every change

    Every pull request gets a preview link before anything reaches a real domain.

  • Domains handled

    The project, custom domain and DNS record are created on first deploy. Existing records are never overwritten.

  • Fast by default

    Static HTML, optimised images and almost no JavaScript. Pages load quickly on any connection.

  • No keys on laptops

    Only GitHub Actions talks to Cloudflare. Teammates never handle credentials.

Stack

Boring, fast, and easy to change

Every site is a plain Astro project with a tiny config file. No servers to run, nothing to patch.

  • Astro with static output and Tailwind CSS v4 design tokens
  • Cloudflare Pages hosting, one project per site
  • GitHub Actions for checks, previews and deploys
  • Claude Code with the ui-ux-pro-max design skill
Read the docs
sites/meetvio/site.json
{
  "domains": ["meetvio.launchkv.com"]
}
That's the whole deploy config. Project, domain and DNS are set up on first deploy.

Frequently asked questions

Do I need a Cloudflare account?

No. You need GitHub access to the repo and Claude Code. Deploys run in GitHub Actions with a token only admins manage.

Can I change a page after it's live?

Yes. Ask Claude for the change; it opens a new pull request with a fresh preview, and merging updates the live page.

What if the domain already points somewhere else?

The deploy stops instead of overwriting the existing DNS record. An admin moves the domain over deliberately.

Can a page have interactive parts?

Yes. Small interactions use plain HTML and scripts; bigger widgets can use a React island when really needed.

Your next launch page is one message away.

Open the repo in Claude Code and describe the product.