scaffold post types, taxonomies etc code generation
Discussion
Should all Blueprint steps become just plugins to wp-cli?
No, simple steps like cp, mv etc don't warrant loading the entire wp-cli machinery and could be handled higher up in the stack.
Should all wp-cli commands be available as Blueprint steps?
It seems like a bad idea. This would inflate the scope, tightly couple the Blueprint library to wp-cli, and require inventing ways to express shell commands as JSON.
Let's handle all downloads outside of WP-CLI. WP-CLI is sequential in nature (download plugin X, then download plugin Y), and Blueprints need to parallelize the downloads (download plugins X and Y at the same time).
How many of WP-CLI commands could Blueprints reuse instead of reinventing the same logic?
Discussion
cc @schlessera @swissspidy @danielbachhuber