edit.scrivito.com is the ideal starting point for editing the content of a Scrivito-based website, especially if one often switches between several sites.
Configuring an existing application so that it uses edit.scrivito.com is easy and requires just a few simple changes. You can try out the result in your local development environment and deploy the app to a staging server before taking it into production.
You require the SDK version 1.15 or later, so please first upgrade your app if you are using an older version.
For edit.scrivito.com and your website to be able to interact, your Content Security Policy needs to be adjusted. If you are using _headersCsp.json, add "https://*.scrivito.com" to the frame-ancestors list. See how it’s done in the Scrivito Example App.
That’s it: Your application is now ready for edit.scrivito.com. You can try it out by visiting edit.scrivito.com. Just put the URL of your application into the path. For example,
https://edit.scrivito.com/www.mystagingserver.comWith a local development server, you may need to handle ‘‘mixed content’’ errors.
Once you’ve tried out edit.scrivito.com and everything works fine, it is recommendable to configure your application so that it always uses this URL for editing content. You can do this by adding the adoptUi: true configuration option to Scrivito.configure (Example).
This creates a redirect from the original /scrivito URL to the new edit.scrivito.com URL, ensuring that no user inadvertently continues to use the previous user interface.
Your application probably includes a few configuration settings that pertain to the previous source of the editing interface. As these are no longer needed, you can simplify your application by removing them. As a nice side effect, the redirect mentioned is also performed faster, once these legacy configuration settings have been removed.
scrivito/index.html (Example)scrivito/* paths (Example)scrivito/* paths (Example)That was it! You’ve now fully migrated your Scrivito app to edit.scrivito.com. Enjoy!