The document discusses automating WordPress development processes. It outlines setting up a development environment using Vagrant and VVV2 to quickly add new sites. It proposes using WP Make to scaffold WordPress plugins and themes. It also suggests using tools like DeployBot or Jenkins to automate deployments to staging and production environments. The goal is to save significant time by reducing repetitive tasks and enabling one-click deployments through automated processes.

1. AUTOMATING WORDPRESS
Daine Mawer / WordCamp Cape Town 2017

2. “Ultimate automation…will make our modern industry
as primitive and outdated as the stone age
man looks to us today”
- Albert Einstein

3. WHO AM I
WHO I’VE WORKED WITH
TODAY’S WORKSHOP
ASSUMPTIONS
GOALS
SETUP
DEVELOPMENT
DEPLOYMENTS
FUTURE
THANK YOU
Front End Engineer at 10up (http://10up.com)
Lecturer, Corporate Trainer, Envato Author
BA in Creative Brand Communications
@dainemawer
https://dainelindleymawer.me

4. WHO AM I
WHO I’VE WORKED WITH
TODAY’S WORKSHOP
ASSUMPTIONS
GOALS
SETUP
DEVELOPMENT
DEPLOYMENTS
FUTURE
THANK YOU

5. WHO AM I
WHO I’VE WORKED WITH
TODAY’S WORKSHOP
ASSUMPTIONS
GOALS
SETUP
DEVELOPMENT
DEPLOYMENTS
FUTURE
THANK YOU
SETUP
DEV
DEPLOY
FUTURE
Optimize and Automate starting new projects
Automate and Scaffold redundant development
Push, Build, Compile and Test source code
One-click, Voice Controlled, API Services

6. WHO AM I
WHO I’VE WORKED WITH
TODAY’S WORKSHOP
ASSUMPTIONS
GOALS
SETUP
DEVELOPMENT
DEPLOYMENTS
FUTURE
THANK YOU
• You have a fairly good command and understanding of bash, Linux
environment and servers.
• You want to keep things DRY and have the OS perform common tasks for
you, faster than you can.
• You work on one or more client projects simultaneously with varying degrees
of development for themes and plugins.
• You hate FTP. You want one-click deploys to a staging server or production.
• Im assuming that your code has no fatal errors or performance problems.
We’ll make the following assumptions:

7. WHO AM I
WHO I’VE WORKED WITH
TODAY’S WORKSHOP
ASSUMPTIONS
GOALS
SETUP
DEVELOPMENT
DEPLOYMENTS
FUTURE
THANK YOU
• ReduceTTL (Time to Live) deploys by 50%
• Focus on development of features, and let technology figure out the rest
• A one-time setup that we can iterate over and improve for each project that
we work on.
• Peace of mind and living and working close to our DRY values.
• To better ourselves, our processes and at the end of the day, be able to take
on more clients and provide better value and service.
And we’ll strive for the following goals:

8. WHO AM I
WHO I’VE WORKED WITH
TODAY’S WORKSHOP
ASSUMPTIONS
GOALS
SETUP
DEVELOPMENT
DEPLOYMENTS
FUTURE
THANK YOU
WHAT WE WANT
A one time setup that will allow us to quickly add new sites
setup a database and install WordPress by running one command
WHAT WE WILL USE
VVV2 - Vagrant
WHY WE WILL USE IT
VVV has had some bad raps in the past. But, for the sake of removing redundant and
DO REPEAT YOURSELF tasks, its latest version (2.0) is stable and robust enough to allow us to create
new projects with ease. No need for complicated stack configurations, we’re developers and we want
peace of mind and continuity.
View my vvv-custom.yml
VVV2 on Github
HOURS SAVED: 1-2 in total per project.

9. WHO AM I
WHO I’VE WORKED WITH
TODAY’S WORKSHOP
ASSUMPTIONS
GOALS
SETUP
DEVELOPMENT
DEPLOYMENTS
FUTURE
THANK YOU
WHAT WE WANT
A tool to scaffold and initialize new project builds within the WordPress environment.
This could be a plugin or theme.
WHAT WE WILL USE
10up’s WP Make - Yeoman Generator.
WHY WE WILL USE IT
In under 5 minutes we can create a theme along with a child theme, with Grunt, Sass and Composer
all ready to go. Whats more is that we can easily create a plugin or WordPress library by running a similar
command on the terminal. This saves us from creating the same files and functions over and over again,
as well as aligning our work to best practices.
WP Make on Github
HOURS SAVED: 3-4 in total per project.

10. WHO AM I
WHO I’VE WORKED WITH
TODAY’S WORKSHOP
ASSUMPTIONS
GOALS
SETUP
DEVELOPMENT
DEPLOYMENTS
FUTURE
THANK YOU
WHAT WE WANT
We want automated deployments of stable code to development environments that take the pain out of
difficult or complex deploys.
WHAT WE WILL USE
DeployBot or Jenkins
WHY WE WILL USE IT
We don't want to manually log into the server, change directories and pull git branches, we don't want to
manually update databases either. We want peace of mind and a little bit of time to sacrifice during setup
that will allow us to push stable, reviewed code to a server, either through a git-hook or via some other
custom tool or command that makes deployments ready to go in under a minute.
DeployBot / Jenkins
HOURS SAVED: 5-10 in total per project.

11. WHO AM I
WHO I’VE WORKED WITH
TODAY’S WORKSHOP
ASSUMPTIONS
GOALS
SETUP
DEVELOPMENT
DEPLOYMENTS
FUTURE
THANK YOU
The future is already here:
https://github.com/dainemawer/voice-control-wp

12. WHO AM I
WHO I’VE WORKED WITH
TODAY’S WORKSHOP
ASSUMPTIONS
GOALS
SETUP
DEVELOPMENT
DEPLOYMENTS
FUTURE
THANK YOU
For questions, feedback, consultations or discussion please get in touch:
THANK YOU
@dainemawer
https://dainelindleymawer.me
daine27
dainelmawer@gmail.com