WordPress Best Practices for Enterprise
summary
10up’s open‑source Best Practices (published late 2014) list concrete choices for enterprise WordPress: use Redis with the WP Redis drop‑in and Batcache for full‑page caching, fragment‑cache WP_Query results (use no_found_rows, fields=ids, update_post_meta_cache=false, cap posts_per_page), make long remote calls non‑blocking or cache them, avoid admin-ajax.php for public endpoints (use the JSON REST API), set wp_options autoload=false when appropriate, run PHPUnit/WP‑Mock and Codeception acceptance tests, sanitize/escape everywhere and review every third‑party plugin before deployment.
AI-written summary · about
chapters (27)
- 0:00Introduction and speaker background
- 0:42Defining enterprise WordPress sites
- 2:12WordPress as an enterprise framework
- 3:36Caching strategies with Redis
- 5:28Fragment caching and remote calls
- 7:19Asynchronous cache priming
- 8:01Admin Ajax and REST API tips
- 9:08Off-the-shelf caching plugins
- 9:30Database reads and writes optimization
- 10:52WP Query performance parameters
- 11:35Autoloading and performance
- 12:18Browser performance and CDNs
- 13:23Maintainable and stable code
- 14:28Modern PHP design patterns
- 15:33Avoiding MVC obsession in WordPress
- 16:37JavaScript design patterns
- 17:22Documentation importance
- 18:23Avoiding wrapper classes
- 19:04Automated testing frameworks
- 20:49Security best practices
- 23:26Nonces and login security
- 24:35Third-party code review process
- 25:58Workflow and code history
- 26:50Q&A: Balancing QA and deadlines
- 28:15Q&A: Selling unit testing to clients
- 29:06Q&A: Favorite linting tools
- 29:48Q&A: Scaling admin-heavy sites
