-
Notifications
You must be signed in to change notification settings - Fork 253
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
CloudFest Hackathon overview issue #124
Comments
Thanks for putting together these issues, @adamziel ! I haven't touched the codebase at all, so I'll spend some time with it in the next couple of weeks and report my findings on the various issues. |
That's a solid list of tasks to hack on 🔥 I'm wondering why you included #14 (setup code linters in the repo) on the most relevant list. It doesn't seem to be something that would appeal to folks watching the demo at the end of hackathon 😄 |
@gziolo that particular one I meant more as a pre-work – I'd love folk to clone the repo and have the linter already there, I remember it took us a while to get there last year. |
There is another exciting idea we could attack. I know @adamziel started exploring possibilities for using WordPress Playground for testing pull requests from the Gutenberg repository. At the moment a different solution exists gutenberg.run available at http://gutenberg.run that uses a much more complex stack that could be replaced with WordPress Playground that only needs a copy of the plugin with changes applied in PR that is prepared for usage in the browser. Finally, it could become a general-purpose solution for any WordPress plugin or theme, as outlined by @fabiankaegy in https://github.com/fabiankaegy/wp-wasm-deploy-preview-example. |
I got Proof of Concept of the Gutenberg previewer to work in #126
The biggest technical limitation is the incomplete SQLite support. What we could explore in Rust:
|
Here's a classic WP-CLI contributor workflow gap I'd love to see solved (wp-cli/i18n-command#351 (comment)) Essentially, the contributor was able to grok the codebase well enough to submit their change, but including tests has the appearance of being too daunting. It would be really cool if WordPress Playground could provide them an environment and user experience for adding the tests:
|
@danielbachhuber I don't see any technical blockers 🎉 putting these pieces together will take work, but technically everything is already supported. |
Closing this since the Hackaton is now over. Thank you everyone! |
This issue lists ideas relevant to the In-browser WordPress development environment project that will be pursued at CloudFest Hackaton 2023.
Most relevant:
Less relevant:
Let's use it to coordinate any ideas, required pre-work, and the project itself.
cc @schlessera @swissspidy @gziolo @danielbachhuber
The text was updated successfully, but these errors were encountered: