docs

Getting started

Quick start

The shortest path from blank folder to live URL.

Buckle up — five minutes from now you'll have a website on the internet, sitting on a real URL you can text to your friends. No dashboards to click through, no build pipelines to configure, no hosting to set up — just your folder, your email, and one command.

And the editing part is yours to drive: open the folder in VS Code, Cursor, Sublime, or vim — or point Claude Code, Codex, or any AI coding agent at it and tell it what to build. Div doesn't care how the HTML got there. Vibe-code your site locally, then ship it with one command.

#1. Scaffold a project

div new mysite

Boom — mysite/ exists, with a starter index.html, a div.json manifest, a .divignore, and a dev server already running.

You'll see something like:

http://localhost:3000

Pop that into a browser. Your starter page is right there waiting for you.

#2. Edit the page

Open mysite/index.html in your favorite editor. Change the headline. Save.

The browser tab reloads itself — no refresh button required. That's div start watching your folder and shouting "something changed!" to the browser.

Prefer to let an AI do the typing? Open the folder in Claude Code, Cursor, Codex, or whatever you build with, and ask it to redesign the page, add a section, or scaffold a whole new layout. Since the project is just static files on disk, anything that writes HTML, CSS, or JS works out of the box — and the live-reload picks up the changes the moment they're saved.

#3. Deploy

In a fresh terminal:

cd mysite
div deploy

Div asks for your email:

What email should we send your link to: you@example.com
✓ Sent! Check your inbox to deploy mysite-a4f9d2.div.so

Open your inbox, click the link in the email, and your website is live at the URL the CLI printed. That's the wow moment.

#4. Update the website

Edit index.html again — by hand, or have your AI assistant of choice rework it — then:

div deploy

This time Div skips the email prompt — it remembers your project and pushes the new files straight to the same URL:

✓ Updated mysite-a4f9d2.div.so

That's the whole loop. Edit, save, deploy, repeat.

#What just happened

  • div new made a folder, dropped a starter file in it, and fired up a local dev server.
  • div start (which div new runs for you automatically) served the folder on localhost and watched for changes.
  • div deploy reserved your slug, uploaded every file, and emailed you a one-click claim link.
  • The verification email proved the email was really yours. Click the link → website goes public.
  • The second div deploy reused saved credentials so you didn't have to repeat yourself.

#Next