Here's the deck from my talk on 10/10/2015 at WordCamp Manchester where I spoke about content staging and things that you can do to make it easier to get content live on your site while working in a team environment.

1. Working in Harmony
Optimize development and content workflows

2. Agenda
• Your team & working together
• Development workflow
• Content workflow
• Development tools
• Deployment

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. Development Workflow

6. Why Use Tiers?
•Avoid working on live production site
•Test scheduled releases, features, bug fixes
•Limit access by team or role
•Maintain a stable environment for other teams

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

8. Production Tier
Dev

9. Staging Tier
Dev

10. Development Tier
Dev

11. Content Workflow

12. Tiers for content creators
• qa
• staging
• production
Content
production
Google Docs / Word
stage Review, Approve, Schedule

13. How Can I Deploy Content?
• Export/import via WordPress core functionality
• Database export/import via MySQL
• Export/import via database management plugins
Content

14. Content Staging Systems
•Content Deployment Plugins
✴Content Staging
✴RAMP
✴Version Press
•Backup Plugins
•Platform & Host Based Solutions
✴Copy staging to live
Content
live
staging

15. Content Staging Plugin
• Batch Deploy Content
• Preflight Check
• Push custom posts, media
Content
live
staging

16. Content Staging Wishlist
•History & Audit Trail
•Multi-tier deploy
✴ push to staging & production
✴ pull new content to dev - DB
•Rollback
•Settings, menus, config
Content
live
staging

17. Local Development
Environment

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

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

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

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

22. Developer Tools

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

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

25. Dependency Management
Dev
Plugin
Theme
Plugin
WP Core

26. Composer
• Dependency Manager for PHP
• Keep versions in sync for team
• Manage plugin, themes, core
• Always use current versions
Dev

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

28. Local Dev Tools
• WP-CLI
• Scheduled local backup
• Copy production content to local
Dev

29. Task Automation - Gulp
• When tasks become repetitive:
• SASS Compiling
• Minification/Uglify
• CSS Post Processing
• Reload
Dev

30. Task Automation
Compile
SASS
Minify
Uglify
Concat
Reload
Browser
Compress
Images
Front end developer automation workflow
Dev

31. Code Management
• Central repository for code
• Manage code for a group of developers
• Set access control
• Merge pull requests
• Branching workflow
Dev

32. Git Branches
Dev
Stage Feature Master

33. Git-Flow
Dev
DevelopFeature Release Master Hotfix

34. Deployment

35. Deployment
Origin Production
Staging
Dev

36. Deployment
Dev

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

38. Development Best
Practices
• Use the same workflow for all dev
• Automate to reduce risk
• Test on a separate environment
Content

39. Resources
edmundturbin.com/presentations/wordcamp-manchester/

40. Questions
email: edmund.turbin@wpengine.com
twitter: @spicecadet
blog: www.edmundturbin.com