You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by ndiego May 31, 2024
This article will detail how you can set up a low-code (or virtually no-low) development workflow for block themes using WordPress Playground and the Create Block Theme plugin. So long as the theme has a repository on GitHub, you can let contributors submit PRs to modify the theme without touching a line of code. Here’s how it works:
The contributor clicks on a link, presumably in the readme of the repo
A Playground instance is opened up containing the main branch of the theme
The contributor can then make changes to the theme in the Site Editor
Once changes are complete, they write those changes to the theme using the Create Block Theme plugin
Then, using a preset configuration set by the Playground blueprint and the Query API, the contributor can create a PR from within Playground for their changes
Then the PR is open in the GitHub repo where they can make any additional changes (modify the title, add labels, etc.)
The goal of this article is to show what is currently possible with Playground and inspire readers to both use Playground and explore how it can be used in novel workflows.
This article's publication will need to wait for the GitHub proxy to be moved to an official location, which is in the works.
Linking to request for links and added info on GitHub, as well as to relevant places on LearnWP for playground in the final piece. Thanks #266 (comment)
Discussed in #266
Originally posted by ndiego May 31, 2024
This article will detail how you can set up a low-code (or virtually no-low) development workflow for block themes using WordPress Playground and the Create Block Theme plugin. So long as the theme has a repository on GitHub, you can let contributors submit PRs to modify the theme without touching a line of code. Here’s how it works:
The goal of this article is to show what is currently possible with Playground and inspire readers to both use Playground and explore how it can be used in novel workflows.
This article's publication will need to wait for the GitHub proxy to be moved to an official location, which is in the works.
cc @adamziel
The text was updated successfully, but these errors were encountered: