wp-plugin-creativecommons
wp-plugin-creativecommons copied to clipboard
[RFC] deprecate `create-guten-block` scripts; use `@wordpress/scripts` instead
When this project was started, we used the create-guten-block
scripts to scaffold the code. Since that time, the @wordpress/scripts
project has become the de facto standard for managing Gutenberg block projects/code. As such, we should consider the implications of adopting @wordpress/scripts
for this project and deprecating create-guten-block
.
@hugosolar have you worked on any projects that use @wordpress/scripts
? What might be some concerns with porting the project structure from create-guten-block
to use @wordpress/scripts
?
@brylie I support this decision! there are no concerns from my side cause the block content is the same the only variation would be the structure, so you'll need to
- Change the standard
@wordpress/scripts
to match the current structure - Change the current structure to match with the default
@wordpress/scripts
structure
I favor the latter, where we adjust this repository to follow the structure of @wordpress/scripts
.
Closing this issue since a number of things have shifted in context since it was originally opened. In several cases it won't be a simple 1:1, and as such a strategy to scope out the depth and breadth of this migration is needed first. That will be tracked here: #211