10 things that all WordPress plugin developers should avoid
summary
Installs 33 plugins activated on a blank test site and shows the concrete problems: dozens of admin banners (some duplicated across plugins and dismissable banners 12 months), inconsistent menu placements and custom UIs that break theme colors, plugins forcing modal flows or blocking the plugins list, scripts loading everywhere instead of conditionally, transients and DB rows left after uninstall, weak i18n and accessibility, and lack of automated checks like phpcs; also demonstrates a small utility that tidies admin menus.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 3:00Aggressive promotion banners
- 8:15Don't make it all about you
- 11:48Don't take over user process
- 13:57Avoid creating custom UI
- 15:21Sanitize and escape early
- 15:41Load only necessary content
- 16:28Clean up after uninstall
- 17:31Follow accessibility standards
- 18:16Check code quality with phpcs
- 19:19Q&A and final thoughts
