Edit & publish — the daily rhythm

In Zero to a live website you shipped a site. The real skill is what comes after: changing it whenever you like and putting the change online yourself, in under a minute, no one in the loop. Once this loop is second nature, the whole thing finally feels like yours.

The mental model: git is the deploy trigger

Here's the one idea that makes it all click. You don't "upload" a website. You make your change locally, then push it to git — and that push is the signal. Cloudflare is watching the repo; the moment a new version lands, it rebuilds the site and the change goes live on its own.

Push to git = publish. Nothing else to remember.

The loop, step by step

Every edit you'll ever make follows the same four beats:

1. Edit — change the text, swap an image, fix a typo (or ask your agent to).
2. Commit — save the change as a labelled snapshot, with a short message saying what you did.
3. Push — send that snapshot up to GitHub.
4. Cloudflare rebuilds — within a minute or two, your site is live with the change. Refresh and see it.

Two ways to do steps 2–3: GUI and terminal

Commit and push are the same action whichever tool you use. Pick whatever feels comfortable — you can switch any time.

git add -A
git commit -m "Update the homepage text"
git pushCopy

The one-command publish habit

Once the terminal feels fine, you'll notice steps 2–3 are always the same three lines. So bundle them into one. Many people keep a tiny shortcut — a single word that adds, commits and pushes in one go:

# a little helper you set up once, then just run:
publish "Update the homepage text"Copy

That's the whole idea behind a publish skill. We run one ourselves to push our own work — a single instruction that commits and pushes, and the site rebuilds. You don't need to build the tool today; the point is the shape: the more you do the loop, the more you'll want to collapse it into one move. (Curious what a "skill" is? See What is a skill.)

Finishing touches when you publish

When a site goes out into the world it wants a few finishing files — favicon, robots.txt, llms.txt, sitemap, the share preview. Those live in Publishing & discoverability, and your agent can add them all with one instruction (the web-launch skill).

Where next