Blueprints: Transition from a TypeScript library to a PHP library #1025
Labels
[Focus] Developer Tools
[Package][@wp-playground] Blueprints
[Type] Developer Experience
[Type] Enhancement
New feature or request
Let’s pivot Blueprints from a TypeScript library to a PHP library. I started the explorations in this repo:
https://github.com/WordPress/blueprints/
Motivation
PHP Blueprints would unite all the Blueprint runtime environments, use-cases, and developers. Single library and documentation unlocking multiple ecosystems.
PHP-powered Blueprints would:
Blueprints would become the lingua franca of WordPress. All the runtimes would rely on the same orchestration library:
Here's a few specific use-cases I have in mind
Technical steps to get there
Here's the big picture of what we'll need to do:
@wp-playground/blueprints
library a thin wrapper that delegates all the tasks to the PHP implementationRelated and known PHP.wasm limitations
Other notes
wp-cli
could handle complex steps likesetWpConfigConstant
(wp config set
),enableMultisite
(wp core multisite-convert
),runWpInstallationWizard
(wp core install
). Same forwp-now
features like downloading and installing WordPress core or the SQLite integration plugin.cc @bgrgicak @dmsnell @mtias @youknowriad @eliot-akira @sejas @danielbachhuber
The text was updated successfully, but these errors were encountered: