How do you keep your website in shape?

When AI lets you build websites faster, you also want to try ideas faster. But faster experimentation does not mean every experiment should immediately appear in front of customers. That is why a simple separation between live and work in progress is so useful.

Main and dev in plain language

GitHub can keep multiple versions of the same project side by side. A parallel version is called a branch. You do not need to remember the word; the idea matters more.

main = what you treat as real.

This is the approved version of the website. You can configure your live publishing so this version goes to yourdomain.com or www.yourdomain.com.

dev = where you work ahead.

Your Hand can build new pages, change copy, try designs and fix problems here without visitors immediately seeing those changes on the live site.

One important detail: GitHub does not automatically make main live. You configure the publishing path. A service such as Cloudflare can connect the GitHub version you choose to a live or preview environment.

Give dev its own website you can actually inspect

The separation becomes much more useful when you can simply open the dev version in your browser. Alongside www.yourdomain.com, you can use something like dev.yourdomain.com.

That gives you two clear windows into the same project:

01devThis is where your Hand builds and experiments.

02dev.yourdomain.comThe real preview you can inspect.

03✓You reviewMobile, copy, behaviour and details.

04main → liveOnly the approved version moves forward.

Customers see only what you approved on the live site. On the dev site you can click around, test mobile, review copy and ask for more changes without affecting the public version.

The simple workflow

1. You give the request. A new page, different positioning, a design change or another experiment.
2. Your Hand works on dev. The current live version on main stays untouched.
3. Cloudflare publishes the dev version as a preview. For example on dev.yourdomain.com.
4. You review the real result. Ask for as many changes as you need.
5. Only after approval does dev move to main. Then the approved version is published live.

Why this works so well with AI

AI makes ideas cheap to try. A different hero, a new landing page, a new navigation or even a completely different look can be created much faster than before. That makes a safe experimentation space more important, not less.

The combination of GitHub + Cloudflare + your Hand gives you that structure:

• GitHub keeps main, dev and the history of the project.
• Your Hand can do the work and iterate within the permissions you set.
• Cloudflare can publish the chosen versions to separate web addresses.
• You keep the decision point: only work you approve reaches live.

This is a fundamentally different way to build from putting everything inside one closed website platform. You can own the domain, the source and the publishing layer yourself while AI does the execution. Large all-in-one platforms are not disappearing tomorrow, but for more simple websites they are no longer the only practical path.

A good foundation does not need to be complicated

For many websites, the essentials are small: one GitHub project, one main version, one dev version, a live domain and a dev subdomain. Add extra services only when the site genuinely needs forms, data, login or other application features.

If you want the wider picture, continue with the guide to GitHub + Cloudflare and optional website building blocks.