Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move wp-now from the main Playground repo #2

Merged
merged 2 commits into from
May 31, 2023
Merged

Move wp-now from the main Playground repo #2

merged 2 commits into from
May 31, 2023

Conversation

adamziel
Copy link
Collaborator

Previous changes to wp-now directory can be browsed at https://github.com/WordPress/wordpress-playground/tree/trunk/packages/wp-now
Previous changes to bin directory can be browsed at https://github.com/WordPress/wordpress-playground/tree/trunk/bin

What?

Moves wp-now from the main WordPress playground repository to a dedicated space.

As outlined in WordPress/wordpress-playground#473, WordPress Playground is re-focusing on WordPress/wordpress-playground#472 and separating the framework from the applications.

@adamziel adamziel merged commit 1ff3a4f into trunk May 31, 2023
@adamziel
Copy link
Collaborator Author

Amended commit: bb00e26

adamziel added a commit that referenced this pull request May 31, 2023
Define 'CONCATENATE_SCRIPTS' as false in `wp-config.php` and removes most static assets from the `wp.data` build script. This makes for an incredible size decrease from 44M to 13M. See #39 and #2 for more details.

Co-authored-by: Adam Zieliński <[email protected]>
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.

1 participant