Managing 50+ Custom Enterprise Plugins in the Age of Gutenberg
summary
Manages 50+ custom plugins by enforcing concrete standards: Git repos with org ownership, branching (dev/QA/prod), and CI/CD with Jenkins that rejects invalid PRs. Creates a readme + plugin boilerplate (file headers, ESLint, PHP-CS, demo GIFs) and a Gutenberg block pattern using WP Scripts single-dependency to collapse hundreds of npm deps. Builds a headless workflow (editor JSON → proprietary API), a chart block that saves flattened images to the DB, and an autocomplete byline tied to an external API; the setup reduces maintenance overhead and vendor hours.
AI-written summary · about
chapters (17)
- 0:00Start
- 3:27Standardization
- 4:33Continuous Integration and Deployment
- 10:54Trust but Verify
- 11:22The E-Myth
- 11:59Define the Standards
- 12:25Internally Define Standards
- 14:02Definition of Done for a Plugin
- 17:18Maintaining Dependencies
- 24:03Tools and Assets
- 24:46Readme Boilerplate
- 26:10Cms Handbook
- 29:27Qa
- 42:02What Do You Do if the Api Is No Longer Available or the Api Changes
- 42:51Chart Api
- 45:05State Management
- 49:10Personalization
