wprig
Using WPRig as parent for a child theme
The scenario: I really would like to use WPRig as a parent theme that could be auto updated a few times a year from here at Github (or the WP repo). As it would make it a lot easier for me to just relate to creating child themes instead of having to think about maintaining the parent theme.
I could just focus on the layout/design and functions to be included in the child theme for the specific site.
I do believe this will help a lot of non developers who are perhaps like myself mini devs, mini designers etc. We could then leave it up to Core devs for WPRig to maintain and update the parent theme and myself and others could just be sure to have a good working child theme.
https://github.com/wprig/wprig/issues/282
I believe this can mostly be accomplished using the recommended git workflow. You can create a "parent" theme using WP Rig following the instructions in that tutorial, then create child themes off the bundled production theme. Looks like that tutorial was published after this issue was created, but wanted to close the loop.
When you want to make updates to the "parent" theme, make the changes in your development repo, then re-bundle and redistribute "parent". Then, a few times a year (or as needed), you can pull in updates from this repository into your development repo for the "parent", re-bundle, and redistribute. So the full hierarchy would look something like this:
WP Rig is upstream of your Parent development repo (aka clone of WP Rig), which bundles the"parent" theme, which is extended by many child themes.
Or, going the other way,
child themes extend a parent theme, which is output by your clone of wp rig, which is downstream of this repo.
That said, using WP Rig in this way might eliminate the need for child themes in this case. When you create a clone of WP Rig that you customize to be your starting place for all your theme development (let's say you call it custom-rig), then whenever you need to build a new theme, you can create a clone of custom-rig. Then, when there's an update to WP Rig you'd like to incorporate, you can pull that from WP Rig into your custom-rig, then from your custom-rig into each affected theme you've developed.
Thanks Jack @jacklowrie
It has been a while since I posted. What you are sharing sounds like a good blog post and a doc.
It would be helpful if someone can create a blog post on the main web site and perhaps add a comment to the Advanced WordPress Facebook group https://www.facebook.com/groups/advancedwp . Just to get a headsup on what is going on these days with WPRig. Thanks!
WP Rig is still alive and kicking! We're a small crew, but looking for more contributors (I just joined last week). We're still getting ourselves organized, but will post an update to the blog etc. soon (I unfortunately can't post in facebook groups as I'm not on facebook). We're currently working on consolidating the WP Rig docs (that's how I found this issue), so this will definitely be a part of that. The plan is to leave this issue open until we've published the docs for this workflow.
Let me know when a blog post is up, and I can post it to the Advanced Facebook group. Movement creates additional movement...:)
I am a designer, tester, tutorial, user focused kind of guy (just tested the FSE call for testing a moment ago). When you got the first version of some of the new docs in place (hopefully fairly simple to follow for a non developer person). Let me know and I can test them out. I have not tested WPRig in a couple of years, so I can use the docs to get WPRig theme up and running.
~~Having a Slack channel for WPRig can be helpful. As a simple way to motivate each other and keep on top of various things that need to be done. In addition to the Github repo.~~ I just noticed another issue where Heather mentioned the Slack channel.