Keep a live site fast and its builder content under control across environments. Pick the row that matches the job in front of you.
| I want to ... | Use | Needs |
|---|---|---|
| see which assets load for visitors and what to measure | Performance | Nothing extra |
| know what to clear after a change | Caching | Drush |
| run several sites from one codebase | Multisite installations | A Drupal multisite setup |
| move builder content between environments | Content staging | Access to each environment |
| decide what goes in git and what stays in the database | Version control | Nothing extra |
| build, test and deploy the module in a pipeline | CI/CD integration | A CI service |
Which should I use
Builder pages live in the database, while settings live in configuration and code. Version control and content staging explain that split; read them before your first deployment. Performance and caching matter once the site is live.
What's next?
Access control for managing who can edit to continue exploring DXPR Builder.