Skip to content

Commit 8250445

Browse files
committed
Proofread
1 parent 8d87fcb commit 8250445

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

CONTRIBUTING.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -69,16 +69,15 @@ If you would like to work on a new core feature or improvement, first create a [
6969

7070
## Control Panel Front End
7171

72-
In order to work on the control panel front end, you'll want to spin up two terminal windows. Run `npm run dev` in one, and `npm run dev:cp` in the other. That will start the main Vite process as well as the Vite process for the `@craftcms/cp` package.
72+
In order to work on the control panel front end, we recommend opening two terminal windows. Run `npm run dev` in one, and `npm run dev:cp` in the other. That will start the main Vite process as well as the Vite process for the `@craftcms/cp` package.
7373

7474
With both running, you'll be able to work on most aspects of the control panel.
7575

7676
If getting into the weeds is your thing, more detail on these pieces is provided below.
7777

7878
### CP assets
7979

80-
The assets specific to the CP live in the `resources` folder. Those are built using a fairly typical Vite setup. To develop assets for the CP there are two commands:
81-
80+
The assets specific to the CP live in the `resources` folder. Those are built using a fairly typical Vite setup. To develop assets for the CP, there are two commands:
8281
```shell
8382
# Run the vite development server
8483
npm run dev
@@ -90,7 +89,6 @@ npm run build
9089
### `@craftcms/cp` package
9190

9291
The CP is largely backed by web components that live in the `@craftcms/cp` package within the `packages/craftcms-cp` directory. Like other packages, it has its own build process that can be run independently of the CP.
93-
9492
```shell
9593
# Run the build in watch mode. Assets will be rebuilt on every change
9694
npm run dev:cp
@@ -106,8 +104,7 @@ In practice, you rarely work on one without the other, so we recommend having tw
106104
> [!NOTE]
107105
> Updating the legacy bundles should be a rare occurrence. Avoid when possible.
108106
109-
ALl of the styles and scripts used to support the CP up until Craft 5 live in the [yii2-adapter](https://github.com/craftcms/yii2-adapter) package. That package has its own NPM dependencies and build process, but because it's common to have that package symlinked into your Craft 6 project you're able to run the build scripts via the `build:bundles` command.
110-
107+
All of the styles and scripts used to support the CP up until Craft 5 live in the [yii2-adapter](https://github.com/craftcms/yii2-adapter) package. That package has its own NPM dependencies and build process, but because it's common to have that package symlinked into your Craft 6 project, you're able to run the build scripts via the `build:bundles` command.
111108
```sh
112109
# Build assets for production
113110
npm run build:bundles

0 commit comments

Comments
 (0)