A modern approach on WordPress development, where our beloved CMS is used as a framework for a rock-solid web application ready to be securely and consistently deployed.

1. aka how you should develop wp apps right now
Meetup WordPress di Roma - 26/08/2016
Enrico Deleo
CTO @ VERTICOMICS
fb.com/therealenricodeleo
github.com/enricodeleo

2. traditional wp dev
flow is for kiddies
From the famous 5-Minute Install on,
WordPress seems the paradise of cowboy
coders, exploitable environments, cheap
hostings and everything in between.
Since you're a gentleman, you stand out
from this inaccuracy.

3. anatomy of a good php app
• DRY
• Clean
• Consistent
• Easy to deploy and manage

5. Git
Git is the Linus Torvalds’ distributed
version control system.
Git keeps track of the code and makes
easy to collaborate or work in parallel
with others during development.
It has tools for reviewing and versioning
code, which is very useful during
deployment.

6. PHP
(duh)
Our beloved CMS is written with it.
There are a lot of great tools written in
php out there, and it can even run a local
webserver for you.
So why don’t try to keep php the only
prerequisite for a php app?

7. SQLite
SQLite is an embedded database for
local storage, built in php.
SQLite implements most of the SQL
standard.

8. Composer
Composer is a php dependency
manager, that enforce the use of php
recommendations (PSR).
With composer you can:
• separate your own code from
commodities
• track 3d parties versions
• automatically install and load
packages in your app

9. phpdotenv
You should never store sensitive
credentials in your code.
Storing configuration in the environment
is a best practice and this library loads
environment variables from .env to
getenv(), $_ENV and $_SERVER
automagically.

10. wp-cli
wp-cli is a php command line tool for
WordPress.
With wp-cli you can speed a lot of
management tasks, export data,
automate. Both locally and remotely.

12. github.com/enricodeleo/wpacked

13. structure

14. structure

15. exposed to the web
third parties php packages
structure

16. extends wordpress
structure
default wp package
configure wp, define
constants from .env and
loads composer packages

17. boostrap locally
copy the .env.example file to .env and put configurations in it, then

19. Packagist
Packagist is the main Composer repository.
Here you find php packages that will be automatically required
within your app.

20. WordPress Packagist
This site mirrors the WordPress plugin and theme directories as
a Composer repository.

21. Your code

23. • set up an environment or use a PaaS
(e.g. elastic beanstalk)
• set up environment variables
• implement blue-green deployment

24. deployment flow
During deployment the platform should:
• clone the most updated <environment> branch
• perform composer install within it
• if everything is fine, expose the new deployed app

25. Questions? Keep in touch!
hello@enricodeleo.com
github.com/enricodeleo
fb.com/therealenricodeleo