Modernizing a Stagnant Toolbox
summary
A WordPress build and repo overhaul modernizes tooling without breaking existing SVN workflows by introducing a develop source repo plus synced core.svn and Git mirrors, adopting Grunt as a task runner, adding grunt-patch-wordpress and grunt-cssjanus, and integrating JSHint, QUnit, Travis CI and Autoprefixer. JS style cleanup is community-driven and fixes nearly 1,000 initial JSHint errors; test visibility more than doubles yearly additions (382 new tests vs 136), Sass is used sparingly for admin color schemes, and builds remain runnable for contributors.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 2:22Problems
- 2:55Hidden Problems
- 3:56Our Goal
- 4:42Tools
- 5:32Ease of Development
- 6:18Better Patches
- 7:04Devsvn
- 7:43Coresvn
- 8:45Grunt
- 10:00Grunt Modules
- 10:43Grunt Patch WordPress
- 11:25Simplifying the Process
- 12:47Sibling Projects
- 14:02JSN
- 15:37WP CLI
- 17:32JavaScript Unit Tests
- 19:31Editor Config
- 20:18CSS
- 21:55AutoPrefixER
- 23:14Vagrant
- 24:10Have goals
- 25:06Dont create new problems
- 26:21Questions
related talks
48mModernizing The WordPress Toolbox
51mGrunt JavaScript Automation for the Lazy Developer
56mUsing WordPress as a Modern Web Dev
29mManaging a Large Front-End Project with Automated Build Tools
23mContributing to WordPress Core
36mGrow Up With Grunt
47mTales from the Dev Side: What Went Wrong, What We Fixe & What You Can Steal
38mGetting to Know Grunt By Writing Your Own Plugin
