"Published" Doesn't Mean "Live" — Why SparkySite Splits Editing From Publishing
On a lot of website tools, setting something to "Published" is the whole ballgame — the moment you flip that toggle, it's live, full stop. SparkySite works differently, and it's worth understanding exactly how, because assuming it works the familiar way is the one mistake that'll actually surprise you.
Editing and publishing an item are two separate states. When you're working on a page, a blog post, or a product, setting its status to Published only marks it eligible to go live — it doesn't touch your actual public site. Getting it in front of visitors takes a second, explicit step: opening Publish from the sidebar and clicking the button there. That action builds your live site from everything currently marked Published across Pages, Blog, and Products — drafts stay hidden, no matter how long ago you last touched them — and pushes the result out to your SparkySite subdomain, or your own custom domain if you've set one up in Settings.
Why bother with two steps instead of one. Think about what a single-step model forces on you: every time you save a Published item, it changes what a visitor sees immediately, mid-edit, typos and all. That's fine if you're making one small tweak to a live post. It's a real problem if you're doing anything bigger — building three new pages, rewriting your home page's blocks, fixing a batch of old typos across your blog — because now every individual save is a small live update, and a visitor could land on your site at any point during that process and see something half-done.
The two-step model removes that pressure entirely. You can mark a brand-new page Published, keep editing it for another hour, add two more pages, go back and fix an old blog post's typo, and none of it touches your live site until you decide the whole batch is ready and click Publish once. Your actual visitors keep seeing whatever was live from the last publish, untouched, the entire time you're working.
What this looks like in practice. Say you're planning a small relaunch — a new home page layout, an updated About page, and two new blog posts to go with it. In a single-step system, you'd either have to do all of that editing in one sitting to avoid a visible in-between state, or accept that your site looks unfinished for however long the work takes. In SparkySite, you build all of it in Draft-or-Published-but-not-yet-live state, across however many sessions you need, checking each page's own preview as you go. When everything's actually ready — new home page, new About copy, both posts — you hit Publish once, and it all goes live together, as a single coherent update instead of a trickle of half-finished changes.
A related habit worth building: use the live preview before you publish, not after. Your home page's block editor shows a live compact preview right next to the editor as you arrange Hero, Highlights, Features, and the rest, plus a "View full site" link that opens the real, full-size public preview. That preview reflects your current draft state, so you can catch a layout problem or an awkward block order before it's ever part of a live publish — not after a visitor has already seen it.
One thing this model doesn't do: it doesn't undo a publish. Once you click Publish, everything currently marked Published goes out together — there's no partial "publish just this one page" action, and no automatic rollback if you publish something you didn't mean to. The safeguard is upstream of that: keep anything not truly ready in Draft, and don't set an item to Published until you actually want it eligible for the next publish run. The two-step model buys you room to prepare; it's still worth treating the Publish button itself as the real, deliberate moment it is.
If you're coming from a tool where "Published" and "live" are the same word, the adjustment is small but genuinely changes how you work: you can be far more relaxed about marking things Published while you're still assembling a bigger update, because that flag alone changes nothing a visitor sees. The actual go-live moment stays entirely in your hands, whenever you decide to hit it.
Take a look at SparkySite's features page for more on how Pages, Blog, and Products all feed into this same publish flow.
A website you can rebuild a piece at a time, in the open, without anyone seeing the scaffolding — that's really what the draft-then-publish split is buying you. It's not extra process for its own sake; it's the difference between working on your site and working in front of your visitors.