The document discusses optimizing development and content workflows by working in harmony. It covers setting up local development environments, using tools like MAMP, Vagrant, and Docker. Development workflows are suggested using Git-flow, branches, and deployment to tiers like development, staging, and production. Content workflows also utilize tiers and tools for exporting, importing, and deploying content between environments. Best practices are outlined for separating code and content changes across environments.

1. Working in Harmony
Optimize development and content workflows

2. Agenda
• Your team
• Working in Harmony
• Development tools
• Development workflow
• Deployment
• Content workflow

3. Who’s On Your Team
Dev Content
PM AM QA

4. Working Together
• No one works alone
• Development Workflow/Best Practices
• Content Workflow

5. Local Dev Environment

6. Local Dev Environment
• MAMP/XAMPP
• Local Server
• Vagrant
• Docker
Dev

7. MAMP/XAMPP
• Installs a web server on your machine
• Relies on OS
• May conflict with apps already installed
Dev

8. Vagrant
• Creates virtual machine
• Automated install
• Quick and simple to setup
• All devs working with the same system
Dev

9. Docker
• Uses containers
• Many containers on one VM
• Automated install
Dev

10. Developer Tools

11. Dev Starting Point
• The same tools/plugins
• The same environment
• The same workflow
Dev

12. Plugins
• Dev/Debug tools
• Environment Indicators
• Demo Content Creator
• User Switching
Dev

13. Local Dev Tools
• Git-flow
• WP-CLI
• Scheduled local backup
• Copy production content to local
Dev

14. Automation
• When tasks become repetitive
• SASS Compiling
• Minification
Dev

15. Task Automation
SASS Compile Minify ReloadCSS
Front end developer automation workflow
Dev

16. Code Management
• Central repository for code
• Branching workflow
Dev

17. Git Branches
Dev
Stage Feature Master

18. Git-Flow
Dev
DevelopFeature Release Master Hotfix

19. Dependency Management
Dev
Plugin
Theme
Plugin
WP Core

20. Dependency Management
• Composer
• Keep versions in sync for team
• Manage plugin, themes
Dev

21. WordPress Packagist
• Mirror of WordPress Plugins, Themes and Core
• Composer repository
• Not all plugins/themes available on wpackigist

22. Development Workflow

23. Why Use Tiers?
•Do not work on live production environment
•Schedule releases, features, bug fixes
•Limit access
•Code changes won’t interfere with content staging

24. Tiers for development
.local
.dev
.stage
.prod
.qa
.test
Dev
production
local
stage

25. Production Tier
Dev

26. Staging Tier
Dev

27. Development Tier
Dev

28. Deployment

29. Central Repo
• Manage code for a group of developers
• Set access control
• Merge pull requests
• Push to multiple servers
Dev

30. Deployment
Origin Production
Staging
Dev

31. Deployment
Dev

32. Content Workflow

33. Tiers for content creators
• qa
• staging
• production
Content
production
local
stage

34. How Can I Stage Content?
• Export/import via WordPress core functionality
• Raw database export
• Database management plugins
Content

35. Content Staging Systems
• Content Deployment Plugins/Systems
• Backup Plugins
• Platform/Host Based Solutions
Content

36. Content Staging Plugin
• Batch Deploy Content
• Preflight Check
• Push custom posts, media
Content

37. Content Wishlist
• History/Audit Trail
• Two way sync/merging changes for conflict resolution
• Multi tier deploy
• push to staging, QA
• pull new content to dev
Content

38. Content Best Practices
• No content changes on production!
• Use staging for review, approval process
• Push content live when ready
Content

39. Questions
edmund.turbin@wpengine.com
@spicecadet
www.edmundturbin.com
Content