You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/overview/index.md
+9-13Lines changed: 9 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,15 +9,14 @@ myst:
9
9
10
10
(overview-label)=
11
11
12
-
13
12
# Overview
14
13
15
-
Plone is a content management system (CMS) that is well-known for its user-friendly interface and robust security features.
16
-
With Plone, even non-technical users can easily create and manage the content for a public website or intranet using only a web browser.
14
+
Plone is a content management system (CMS) that is well-known for its user-friendly interface and robust security features.
15
+
With Plone, even non-technical users can easily create and manage the content for a public website or intranet using only a web browser.
17
16
Plone's intuitive interface and comprehensive set of features make it a popular choice for businesses, governments, universities, and any organization that needs a reliable and easy-to-use CMS.
18
17
19
-
Plone has a long history and has been trusted by users around the world since its initial release on October 4, 2001.
20
-
Over the years, Plone has undergone many improvements and enhancements, making it a highly mature and stable CMS.
18
+
Plone has a long history and has been trusted by users around the world since its initial release on October 4, 2001.
19
+
Over the years, Plone has undergone many improvements and enhancements, making it a highly mature and stable CMS.
21
20
Additionally, Plone is supported by a strong community of users and developers who contribute to its ongoing success.
22
21
23
22
Plone has the maturity, stability, and reliability of an application maintained by open source developers with decades of experience, while continually evolving and adapting to modern technology.
@@ -65,20 +64,18 @@ Plone is easy to set up compared to other CMSs in its category, extremely flexib
65
64
-**Plone is technology neutral.**
66
65
Plone can interoperate with most relational database systems—both open source and commercial—and runs on many platforms, including Linux, Windows, macOS, and BSD.
Plone is a content management platform with its backend written in Python.
75
-
It is built on top of the open source Zope web application server and development system.
72
+
It is built on top of the open source Zope web application server and development system.
76
73
Plone makes use of the pluggable Zope Component Architecture (ZCA) to provide a highly modular and extensible system.
77
-
Throughout its history, Plone has used {term}`server-side rendering` to generate HTML-based content, with advanced resource management features for adding and bundling CSS and JavaScript.
74
+
Throughout its history, Plone has used {term}`server-side rendering` to generate HTML-based content, with advanced resource management features for adding and bundling CSS and JavaScript.
78
75
Additionally, Plone's use of a component architecture makes it easy to extend and customize, allowing users to create unique, feature rich websites that are tailored to their specific needs.
79
76
80
77
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.
81
-
The Python-based backend server in Plone can 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".
78
+
The Python-based backend server in Plone can 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".
82
79
This configuration has been supported by Plone since its initial release and is available in the latest version of the platform.
83
80
For container-based deployment, only the `plone-backend` image is required.
84
81
It may be used as a base image, adding customizations, to make a derivative image.
@@ -97,11 +94,11 @@ It will take some time until we find and can implement the best structure to exp
97
94
```{seealso}
98
95
You can also read the conceptual guide {doc}`/conceptual-guides/package-dependencies` to get a mental model of the structure of Plone.
@@ -110,7 +107,6 @@ To run a public Plone website in production, you also need to configure and run
110
107
This is the domain of systems administrators and modern developer-operations professionals.
111
108
Our documentation contains setup examples for these services, yet requires that the reader have some generic experience and knowledge of these domains.
112
109
113
-
114
110
(overview-good-to-know-label)=
115
111
116
112
## Good to know
@@ -121,7 +117,7 @@ The Plone backend can be run on a local developer machine in a container.
121
117
Basic familiarity with programming in Python and managing Python modules and packages using `virtualenv` and `pip` is required to work on the backend code.
122
118
We use `venv` and {term}`mxdev` to manage the source installation of packages in Plone 6.
123
119
124
-
Similarly, to develop for the new React frontend, you need to have some experience with setting up Node.js, using a tool like {term}`nvm` to isolate your setup, and familiarity with {term}`Yarn` and {term}`React`.
120
+
Similarly, to develop for the new React frontend, you need to have some experience with setting up Node.js, using a tool like {term}`nvm` to isolate your setup, and familiarity with {term}`pnpm` and {term}`React`.
125
121
126
122
If you are looking for more study material on these technologies beyond the documentation, see and follow one or more [Plone Trainings](https://training.plone.org).
127
123
Our trainings are more verbose and contain extra clarification and examples.
0 commit comments