Skip to content

Commit b6ed687

Browse files
fredvdstevepiercy
andauthored
Update docs/overview/index.md
Co-authored-by: Steve Piercy <[email protected]>
1 parent 9a349df commit b6ed687

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

docs/overview/index.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,8 @@ Additionally, Plone's use of a component architecture makes it easy to extend an
8080
With the release of Plone 6, you now have the option to choose from two different out-of-the-box supported configurations when setting up a new Plone website.
8181
The Python-based backend server in Plone can still be used alone to render content server-side and deliver HTML to the browser, a setup that is referred to in the Plone documentation as "Classic UI".
8282
This configuration has been supported by Plone since its initial release and is still available in the latest version of the platform.
83-
For container-based deployment, only the `plone-backend` image is required, or a derivative image with customizations added.
83+
For container-based deployment, only the `plone-backend` image is required.
84+
It may be used as a base image, adding customizations, to make a derivative image.
8485

8586
The default and recommended configuration for new websites in Plone is the new React-based JavaScript frontend called "Volto".
8687
For this setup you still need to run the Python-based backend server, as well as enable the REST API, and update the configuration profile.

0 commit comments

Comments
 (0)