We live in a world of continuous integration, continuous delivery, version controlled code and configuration. Yet when it comes to delivering content we are relying on doing all publishing straight to the production environment and hoping it works, editing the live document to fix issues we only find once they are in production. I propose there is a better way.
Let’s build our content on our development instances the same way we develop code and configuration. Then using the power of Github, WP-CLI and Automated Testing tools like Behat, lets professionally deploy our content to production will full confidence it works as intended. Let’s give editors better tools to build better content in a word of Gutenberg while saving anyone the need to overwrite the production database ever again.
Topics include:
- WP-CLI for generating content
- Connecting Github and your WordPress site
- Leveraging multiple environment
- Behaviorally testing content
Prerequisites:
WP-CLI would be helpful but not mandatory. Having the ability to create multiple environments for your site is helpful too but local vs production is acceptable setup