Migrate to Volto
Migrate to Volto#
Plone 6 comes with a new default frontend called Volto.
Volto is written in React and uses
plone.restapi to communicate with the backend.
When creating a new Plone 6 site, you may choose between frontends.
Volto - Create a new Plone site, the default option
Classic UI - Create Classic Plone site
This choice is presented because there are some non-trivial differences between their configurations. This document discusses these differences. It also informs administrators and developers of how to migrate their existing Plone 6 site with Classic UI to instead become compatible with Volto for its frontend.
As a pre-requisite, your Plone site must be upgraded to Plone 6 before migrating to Volto for the frontend.
Plone provides a form
/@@migrate_to_volto that allows you to run all the required changes to your existing site to make it compatible with Volto.
You can access this form in the browser when you are logged in as an administrator.
localhost is your hostname,
8080 is the port on which Plone runs, and
Plone is the name of the Plone instance.
Additionally, after upgrading an existing site to Plone 6 (see Upgrading to Plone 6.0), a message will appear, You can prepare your site for Volto, the default frontend of Plone 6!, with a link to that form.
Test all migrations thoroughly before applying them on a production environment!
A site that is made compatible with Volto will be accessible with Plone Classic UI, but it will behave differently. For example, editors can only effectively work with the content using Volto because HTML is no longer editable in the TinyMCE editor used in Classic UI.
The required steps are:
Install the packages
plone.restapiis the RESTful API for Plone that allows the frontend Volto to communicate with the backend.
plone.voltoconfigures Plone to work with Volto, the new default frontend for Plone 6.
Migrate RichText fields to Volto blocks
Volto has a new editor called Slate, whereas Classic UI uses TinyMCE. This step converts the HTML stored in RichText fields to text blocks, allowing you to edit them in Volto. Images, links, and most kinds of HTML formatting are preserved.
For this you need to have
blocks-conversion-toolrunning on an accessible URL. The easiest way to have that running on your machine is to use Docker:
docker run -it -p 5000:5000 plone/blocks-conversion-tool:latest
For more options read https://github.com/plone/blocks-conversion-tool.
Pages, News Items, and Events are made folderish
That means these types can contain other content such as Images or other Pages. When you create a new site in Plone 6, this setting is also applied automatically. But existing content remains non-folderish until this step is run.
Turn folders into folderish pages
In Volto adding Folders is disabled by default. Instead folderish pages are used to create folder structures. This step turns all folders into folderish pages. If the folder shows a listing of the content, an appropriate listing block will be added. If the folder shows a default page, then it will be handled in the next step. You can re-enable Folders by checking the box Implicitly addable? in
Default Pages of Folders are merged with the Folderish Pages that replace the Folder
Volto does not have a concept of default pages. Instead folderish pages can show text, a listing of all the content inside that page, or both. This step takes the content of the default page (such as text or the query of a collection), and adds that to the folderish page that replaces the folder. Metadata (subjects, author, rights, and so on) and relations are moved to the folderish page.
Collections are migrated to Pages with Listing Blocks
In Volto adding Collections is disabled by default. Instead folderish pages with listing blocks are used. This step turns all collections into folderish pages. The criteria of the collection are used to configure a listing block in that page.
It is recommended to use the default settings, but you can choose to skip some migration steps in the form.