Publishing, pending changes, and versions

Saving a change in Web Studio and publishing it are not always the same action. CreaRápido maintains an editable version and a public version of the site.

First publish

When a site has never been published, use Publish site. Publishing creates/updates the public files and makes the site available on its CreaRápido subdomain.

On the Free plan, an account can keep 1 free site published at a time. PRO is managed per site and can change the capabilities available to that site.

Updating an already published site

After editing a published site, the interface can show unpublished changes. Use Update site/Publish (according to the current UI label) to push visual changes to the public site.

Saving in the editor should not automatically be interpreted as “visitors can already see this change.”

Published versions

CreaRápido keeps information related to published versions and provides backup/restore mechanisms for administrative operations. If a restored state requires republishing, publish again before expecting public files to change.

Blog and dynamic content

Some modules can update content through their own workflow. Blog posts, for example, have draft and published states. Do not assume every module behaves exactly like a visual Web Studio edit.

Custom domains and publishing

Connecting a domain does not replace publishing the website. If a custom domain is connected to a site that was never published, the visitor may see an unavailable page or 404. Publish the site first, then complete the domain connection.

If changes are not visible

confirm you are viewing the correct site;
check whether Web Studio shows unpublished changes;
use Update/Publish;
wait for the publish job to finish;
reload the public site;
when using a custom domain, also test the CreaRápido subdomain to separate publishing issues from DNS/SSL issues.