Resource
WP-CLI
Everything I do is scripted in WP-CLI before it's a plugin. Database search-replace, user provisioning, content migration, plugin audits.
Everything I do is scripted in WP-CLI before it’s a plugin. Database search-replace, user management, post imports, theme + plugin activation.
Why scripts beat plugins
A plugin is a long-lived dependency with an update cycle and a security surface. A WP-CLI script runs once, leaves the codebase clean, and lives in version control. For 80% of “I need to do X to WordPress” tasks, a script is the right answer.
Example uses
- Database search-replace across a multisite (the GUI version chokes; CLI handles 50M rows fine).
- Bulk user creation from a CSV (one line of bash).
- Post import + meta + taxonomy linking (the seeder for this site is WP-CLI).
- Theme + plugin activation in CI (no manual click-through after deploy).
License
MIT.