As this project grows, we're going to need to support seeding new sites and deploying updates to existing sites.
The goal of this project is to support a Sanders theme, as well as support a Multisite installation of many instances of the site. With this comes some challenges:
Spinning up a new site seeded with default/required posts. Pages should be initialized and assigned to their respective templates. Menus should be initialized. Custom fields should be added. Etc
Deploying changes should be as autonomous as possible. If we need to add a new page, custom field, etc. we should be able to do this across many instances at once.
I think in the end we'll also have a handful of scripts that will make this process easier. I'd imagine this would end up being similar to how certain frameworks handle DB migrations, except our implementation would only support forward migrations. I could picture a directory of migration scripts that could be run against any multisite instance to bring its backend up to date.
As this project grows, we're going to need to support seeding new sites and deploying updates to existing sites.
The goal of this project is to support a Sanders theme, as well as support a Multisite installation of many instances of the site. With this comes some challenges:
https://github.com/wp-cli/wp-cli could be useful here. It has a lot of utility that could be easier to write a bash script to seed new sites, rather than some WP script files. It also has utility for multisite.
I think in the end we'll also have a handful of scripts that will make this process easier. I'd imagine this would end up being similar to how certain frameworks handle DB migrations, except our implementation would only support forward migrations. I could picture a directory of migration scripts that could be run against any multisite instance to bring its backend up to date.