Skip to content

Conversation

@pbking
Copy link
Contributor

@pbking pbking commented Apr 15, 2025

Update wp-env configuration to use 'development mode' and to store themes in an accessible place for development.

with these environment variables set:

"WP_ENVIRONMENT_TYPE": "development",
"WP_DEVELOPMENT_MODE": "all"

Things like patterns are not cached and other improvements that make sure the WordPress environment provided by wp-env is the best to develop in.

Additionally the /themes folder is mapped to a local folder so that themes created and saved in the development environment can be easily observed.

@pbking pbking requested a review from t-hamano April 15, 2025 11:40
Copy link
Contributor

@t-hamano t-hamano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additionally the /themes folder is mapped to a local folder so that themes created and saved in the development environment can be easily observed.

Does this mean that in developing CBT, a custom theme may be necessary? Will the default theme not suffice?

@pbking
Copy link
Contributor Author

pbking commented Apr 15, 2025

A default theme is fine to start with, however observing the themes that CBT creates/exports is important for development and this change allows for those themes to be easily observed (be that default themes, installed, created, etc).

For example, create a new blank theme called "Blankey" in the dev environment, make changes to it and save it and you will see that changes in the new folder.

Previous to this change I have to load the CBT plugin into another environment in order to see the files it's manipulating when saving/creating themes.

@pbking pbking merged commit 6ac2f73 into trunk Apr 16, 2025
2 checks passed
@pbking pbking deleted the improve/dev-env branch April 16, 2025 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants