No more emailing files to your developer

Here is how updating an old-fashioned business website usually goes. You email your developer the new text or the new photos. They open a connection to the hosting server and copy the changed files across by hand. Somewhere on that server sits the only copy of your website.

When this works, it is merely slow: a day or two of waiting for a change you described in one sentence. When it breaks, it is worse than slow. Nobody is quite sure which file changed, what the page looked like before, or how to get back to it.

One fragile copy is the real problem

The uploading is not actually the scary part. The scary part is that the live server holds the only authoritative copy of your site.

Overwrite a file, and the previous version is gone. There is no history and no undo. A hosting mishap, a compromised account, or simply a hosting plan that lapses because a card expired can erase the site outright. Many owners discover this only on the day it happens, which is the most expensive possible day to learn it.

A website run this way is not really owned. It is balanced on a shelf, and everyone is hoping nothing bumps the shelf.

A site that lives in a repository

The sites I build live somewhere sturdier: a Git repository. A repository is a folder with a complete memory. Every version of every file is kept permanently, so when a file changes, the old version is not overwritten. It stays in the history, and going back to it is one step.

The repository is stored with the hosting service and also on any computer that keeps a copy. Nothing is ever only in one place, and nothing that has been saved is ever truly lost.

To be clear, none of this is new or exotic, and I did not invent it. This is how essentially all serious software has been built for years, and it is exactly why software teams stopped uploading files to servers by hand. Small business websites are simply late to a standard the rest of the industry settled long ago.

Saving a change publishes the site

The website you are reading is the working example. When I save a change to its repository, the hosting service notices on its own, rebuilds every page from the files, and publishes the result. From save to live takes minutes, and at no point does a human upload anything.

The safety net is built in. If a change contains a mistake serious enough that the site cannot be rebuilt, the build fails and the live site stays on the last good version. A change that breaks the build cannot take the site down. Under the old workflow, a bad upload was live the moment the copy finished, and stayed live until someone noticed.

Every site I set up gets this same pipeline, because there is no cheaper insurance available anywhere.

The part that protects you from me

There is one more consequence, and it points at me.

Because the site is an ordinary repository built with ordinary, widely used tools, any competent developer can take it over at any point. The repository is standard. The hosting is standard. The build service is standard. If I retire, disappear, or simply stop being the right fit, your next developer opens the folder and gets to work. Hiring me does not marry you to me.

Proprietary page-builder platforms work the other way around. Your content and design live inside the platform’s own system, and leaving usually means rebuilding from nothing. That is the difference worth remembering: owning a website does not mean your name is on the invoice. It means you can walk away, with the whole site, whenever you choose.

What this costs

The short answer is nothing new.

Repository hosting is free at this scale on standard plans, and so is the automatic build-and-publish service. These are not trials; they are ordinary plans that a small, fast site fits inside comfortably. This site runs on exactly that setup, and the cost table on the work page lists every line of the bill.

What remains is the domain name, which you already pay for today. The workflow that software teams treat as basic professional practice costs a small business nothing to adopt. The only real change is that you stop emailing files and start owning your website.