Cloud setup overview
The visual editor enables content editors and developers to collaborate on the same site with a containerized visual editing experience.
A container runs the editing application, but also handles staying in sync with your remote repository and running your site (in development).
# Set up visual editor locally
We recommend testing out the visual editor locally to ensure your configuration works, especially as you learn how to customize the visual editor for your team.
Here are some key differences to testing out the visual editor locally:
- You must run and use your own development server
- Any branch can be used when working locally, since the local visual editor application doesn't listen for remote Git changes.
If you're not using local development, then the visual editing container runs your development for you and webhooks pull in changes pushed to the site's working branch. Note
# Next steps
After testing out your initial setup, site templates, and other custom configuration options, we recommend you finish setting up the visual editor so your team can collaboratively edit with some of these guides:
- Set up access control: manage user roles and permissions for using or developing the visual editor
- Set up your visual editing container: environment and setup details for your visual editing container.
- Add site from Git repository: create a new site from am existing Git repository.
- Git branching: understand how your site with visual editing works with branches from your remote Git repository.
- Previewing: see and share changes before they are published to production.
- Publishing: customize the visual editing experience to work with your existing publishing workflows.
Did you find this doc useful?
Your feedback helps us improve our docs.