Training & onboarding your team

Environment spaces allow you to create safe, isolated environments where new team members can learn and experiment without affecting live projects. These environments are perfect for onboarding new developers, editors, and designers — they can explore real project setups, test workflows, and understand best practices hands-on, all without the risk of breaking production.

Testing multiple variants without changing production

With environment spaces, you can spin up separate testing environments to experiment with multiple variants of content, layouts, or integrations. This enables true A/B or multivariate testing before rolling out to end users. You can safely validate which version performs better, collect feedback internally, and deploy only the winning version to production.

Enabling new components

When introducing new components, you can first enable and test them within a development or staging environment. This ensures that component behavior, styling, and data structure are validated before being made available in production. It allows developers and content teams to align on usage guidelines and best practices in a controlled space.

Versioning components and the whole component library

Each environment can maintain different versions of components or the entire component library. This version control ensures that teams can safely iterate on new designs or functionalities without breaking existing setups. You can track, test, and gradually roll out updates to ensure backward compatibility and a smooth upgrade process.

Sync frontend releases with new components

Environment spaces make it easier to synchronize front-end code releases with corresponding component updates. Developers can test the full integration (front-end + CMS components) within staging before syncing with production, ensuring consistency across deployments and reducing the risk of mismatched versions or missing functionality.

Transform content from the old structure to a new structure

When migrating or refactoring content models, environment spaces let you transform and test your new structure in parallel. You can safely map old content to new schemas, validate how it displays, and fix any discrepancies — all before pushing it live. This prevents downtime and ensures smooth transitions between content architectures.

Parallel development and controlled promotion

Multiple developers or teams can work on different features in parallel within separate development environments. Once a feature is ready, you can selectively promote it to staging for validation and then to production once approved by content editors. This workflow maximizes development velocity while maintaining strict control over what reaches production.

Added layer of security and testing

Beyond the standard Dev → Staging → Production pipeline, environment spaces allow you to create nested sub-environments under any stage. For example, multiple “Dev” subspaces for feature branches or training, or additional “Staging” subspaces for QA and UAT. This adds another layer of security, experimentation, and flexibility — ensuring that every change is tested and approved before it can impact end users.