Publishing and releasing
On Weblooks hosting a change reaches visitors in two steps: you publish it to the staging link, check it there, then release that version to your own domain.
Publish: the staging link#
Publishing builds the site and puts it on its staging link, an address such as your-project.weblooks.site. That is where you and your client review the site before anyone else sees it. Every publish is kept as a version in the deploy history. Publishing a CMS entry updates the staging site too.
Release: your own domain#
Releasing puts one published version on your custom domain, the address your visitors use. The staging link is not affected, so you can keep publishing and reviewing while visitors see the released version. You can switch your domain to any other version at any time, which is also how you go back if a release was a mistake.
Why two steps#
Keeping the review copy and the public copy apart means a half-finished change never reaches your visitors by accident, and a client can approve exactly the version that goes live.
If you publish to your own hosting account instead (Cloudflare, Netlify, Vercel and others, under Deploy in the editor), your host deploys from GitHub on its own, and the release step does not apply.