Check the final version
In Final version, check the presented version, content and agreed features. Approval is an explicit action, potentially restricted to the owner and subject to identity verification. Do not approve while unresolved questions remain.
Read the publication plan
After approval, open Publication. Check the domain, destination, HTTPS, dependencies and recovery notes. Consent to the launch plan is separate from approval of the result: check both rather than assuming one replaces the other.
Publication is carried out manually
The team manually deploys previews and the final website. The dashboard records the plan, consent, status and link; it is not an automatic deployment service. Your consent does not itself change the public website. Wait for the recorded result and the team’s checks.
Domain, email and client services
When needed, we configure MX records for the client’s email service. The client subscribes to and pays for that email service independently. Tell the team about existing services in advance. DNS records do not contain or store email messages. SHOP plans and external accounts are agreed before connection.
After the site goes live
Use the recorded link and check the main pages and features.
- Check the final address and HTTPS.
- Test navigation, contact details and agreed features.
- Report issues with the page, time and steps to reproduce them.
If something goes wrong
Contact the team. Recovery options and effects depend on the plan and the previous version available. Restoring a website does not automatically undo external operations, sent emails, orders or payments. Do not make parallel domain changes without coordination.