Publishing — Taking a Site Live

Lesson 8 · taught by Pip

We have files, a server to hold them, and a name pointing at that server. The last step is the one with the drumroll: moving the files onto the server and opening the doors. This is called publishing, or deploying, a site. Today, what really happens when a website goes live.

The plain idea: publishing is copying your finished files from your machine up to the always-on server, so that from that moment, anyone who visits gets the new version.

Moving into the shop

Imagine you've decorated a shop's interior in your garage — shelves, signage, the whole layout — and now it's ready. Going live is moving all of it into the actual storefront on Main Street and flipping the sign to "Open." Until you move it in, no customer can see your work. The moment you do, they all can.

Deploying is that move. Your files travel from your computer up to the server. The instant they land and the server starts handing them out, the site is live — your garage work is now on Main Street for the whole world.

A careful swap, not a gap

Here's a worry people have: if you're replacing an old version with a new one, is the shop closed during the swap? Done well, no. Good publishing puts the new files in place and then switches visitors over all at once, cleanly — like rolling out a finished display behind a curtain, then pulling the curtain. Nobody sees a half-built mess.

And if the new version has a problem, you can usually roll back — switch the curtain back to the previous version in moments, because the old files were kept. That safety net is why publishing modern sites feels less like a leap and more like a reversible step.

Updating is just publishing again

A website is never truly "finished." You fix a typo, add a page, change a price. Each change means publishing again — copying the updated files up, swapping them in cleanly. A busy site might go live with new versions many times a day, each one a quiet, careful swap that visitors never feel.

This is the seam where everything in this course meets: structure, looks, and behavior, bundled into files, carried to an always-on server, reachable by a friendly name, opened to the world. When Portmint delivers a site or a branded assistant, this final step — taking it live, and being able to update or roll it back safely — is exactly what "we host and deliver it" means.

Your turn

Think of a site you've seen change — a shop that added a sale banner, a page that fixed a wrong phone number. Each change was a publish: new files, carried up, swapped in. You've been watching deployments your whole life without a name for them.

We've gone from a single typed file all the way to a live site. Next, the last stop: we walk the whole journey end to end, one clean voyage. 🔦