Skip to content

Commit 046e60c

Browse files
committed
Change occurrences of yarn with pnpm.
1 parent 5fe84a3 commit 046e60c

3 files changed

Lines changed: 14 additions & 18 deletions

File tree

docs/classic-ui/mockup.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -89,16 +89,16 @@ This creates the necessary JavaScript resources and webpack configuration for yo
8989
All your pattern JavaScript code goes into {file}`resources/pat-testpattern/testpattern.js`.
9090
SCSS files can be imported, too, since webpack provides the `sass-loader` module.
9191

92-
Next, install the npm packages using {term}`yarn`.
92+
Next, install the npm packages using {term}`pnpm`.
9393

9494
```shell
95-
yarn install
95+
pnpm install
9696
```
9797

9898
When you finish writing your JavaScript code, you have to build the bundle with the following command.
9999

100100
```shell
101-
yarn build
101+
pnpm build
102102
```
103103

104104
This creates the webpack chunks, the JavaScript bundle files, and a demo browser view in your add-on package.

docs/install/containers/images/frontend.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ chmod 755 entrypoint.sh
6363
```
6464

6565
```{note}
66-
Do not forget to add the `exec "$@"` command at the end of the `entrypoint.sh` file to run the default `yarn start` command.
66+
Do not forget to add the `exec "$@"` command at the end of the `entrypoint.sh` file to run the default `pnpm start` command.
6767
```
6868

6969
In the `Dockerfile` you will need to add two commands to make the Docker container run `entrypoint.sh` on start:
@@ -77,7 +77,7 @@ In the `Dockerfile` you will need to add two commands to make the Docker contain
7777
```
7878

7979
```diff
80-
CMD ["yarn", "start:prod"]
80+
CMD ["pnpm", "start:prod"]
8181
+ ENTRYPOINT ["/entrypoint.sh"]
8282
```
8383

docs/overview/index.md

Lines changed: 9 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -9,15 +9,14 @@ myst:
99

1010
(overview-label)=
1111

12-
1312
# Overview
1413

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.
1716
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.
1817

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.
2120
Additionally, Plone is supported by a strong community of users and developers who contribute to its ongoing success.
2221

2322
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
6564
- **Plone is technology neutral.**
6665
Plone can interoperate with most relational database systems—both open source and commercial—and runs on many platforms, including Linux, Windows, macOS, and BSD.
6766

68-
69-
7067
(overview-high-level-overview-for-developers-label)=
7168

7269
## High level overview for developers
7370

7471
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.
7673
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.
7875
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.
7976

8077
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".
8279
This configuration has been supported by Plone since its initial release and is available in the latest version of the platform.
8380
For container-based deployment, only the `plone-backend` image is required.
8481
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
9794
```{seealso}
9895
You can also read the conceptual guide {doc}`/conceptual-guides/package-dependencies` to get a mental model of the structure of Plone.
9996
```
97+
10098
```{seealso}
10199
https://training.plone.org/mastering-plone/what_is_plone.html
102100
```
103101

104-
105102
(overview-deployment-label)=
106103

107104
## Deployment
@@ -110,7 +107,6 @@ To run a public Plone website in production, you also need to configure and run
110107
This is the domain of systems administrators and modern developer-operations professionals.
111108
Our documentation contains setup examples for these services, yet requires that the reader have some generic experience and knowledge of these domains.
112109

113-
114110
(overview-good-to-know-label)=
115111

116112
## Good to know
@@ -121,7 +117,7 @@ The Plone backend can be run on a local developer machine in a container.
121117
Basic familiarity with programming in Python and managing Python modules and packages using `virtualenv` and `pip` is required to work on the backend code.
122118
We use `venv` and {term}`mxdev` to manage the source installation of packages in Plone 6.
123119

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`.
125121

126122
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).
127123
Our trainings are more verbose and contain extra clarification and examples.

0 commit comments

Comments
 (0)