In Slater, staging and production environments are designed to help manage and streamline your code deployment process, particularly when working with Webflow integrations.
Staging Environment
- Purpose: Safely test and validate code changes before they affect your live site.
- How It Works: When publishing to staging in Slater, scripts are served directly from the server to your
webflow.io domain. This method delivers code quickly and is ideal for rapid iteration and testing. - Recommended Actions:
- Test all new features, check for errors, and confirm third-party integrations.
- Use browser DevTools to monitor network requests and console feedback.
- Validate changes without impacting your customer-facing site.
Production Environment
- Purpose: Hosts the live version of your site that end users see on your custom domain.
- How It Works: Publishing to production in Slater serves a static file to your custom domain (e.g.,
yourcompany.com). This approach is more resilient, ensuring your site remains stable and reliable for all visitors. - Recommended Actions:
- Only promote thoroughly tested and finalized code to production.
- Monitor the live site after deployment for any unexpected issues.
- Reserve production for stable, public-ready code.
Typical Workflow
- Develop and test in staging on your
webflow.io domain. - Verify everything works—ensure there are no errors and all features function correctly.
- Promote to production to make changes live on your custom domain.
Troubleshooting Tip
If something appears incorrect on your production site but not in staging, double-check which environment you are viewing and ensure that the correct environment has been published in both Slater and Webflow.
For further guidance, including step-by-step video tutorials and documentation, consult the following resources:
