-
Notifications
You must be signed in to change notification settings - Fork 0
Home
As we develop this custom theme, we will need to exchange theme files, settings, and content. This is managed using different tools.
Changes to the child theme are versioned in this Git repository. This repo is deployed to WP Engine when production or staging needs updated. Whenever changes are ready you should follow the standard process to add changes, make a commit, and push the changes to origin.
Normally tasks should be completed in task-specific branches, and those task branches should be pushed and turned into Pull Requests for code review.
On the rare occasions when large amounts of new content are required to move to staging or production (such as early in the life of the site, or in developing large new sections), the Wordpress Export tool should be used to export content. (Please export the smallest slice of content possible.) The resulting XML file should be compressed into a ZIP file and attached to relevant Issue on Github so that it can be accessed by other team members reviewing work and updating sites.
For updated content, images and media created and used for local development will need to be replaced. After importing content into the Staging site, be sure to repair any broken image or media links.
Tracking down settings changes is probably the most difficult part of new builds. Later on, settings tend to change rarely, so they are not as much of a pain to manage. But at first we change settings a lot to create the site, and those settings must be translated from local dev environments into the sites.
Be sure to check in each individual plugin. For example, individual sliders must be exported and updated by hand, and settings for things like static homepages are often missed on setting up a new site deployment.
TODO: Figure out if there is a WP Plugin that could help us manage these details.