Talk: 10 Things All WordPress Plugin Developers Should Avoid
Help the Feature Notifications Team
If you use WordPress, whether you are engaged in the WordPress community or not (e.g. non-technical site editors), the Feature Notifications team would love to hear from you.
Looking for feedback on the current system of notices within the WordPress dashboard, answering the survey (below) would go a great way towards helping steer the future direction of the project, which involves improving all forms of notifications (both admin notices and emails).
If you want to know more you can join the #feature-notifications channel in the Making WordPress Slack or find out more about the project.
An incredible talk by David Artiss
📽️: View the Slides
▶️: Video of the talk (coming soon)
It was fun and informative. Easy to understand. I really liked it
Samuel Mente
The following are the things discussed during the talk, plus the additional items. There were additional suggestions from the audience which will be added once the video is available.
Once I publish a post on any of the subjects (one is due to written, over the coming months, for each), then a link will be added below. Alternatively, follow the WCEU2023 tag feed.
- Aggressive Promotion
- Inconsistent and confusing menus
- Don’t take over the user process
- Avoid creating your own UI
- Lack of data validation
- Loading unnecessary content
- Leaving content behind
- Forgetting Accessibility Standards
- Ignoring code quality checking
- Flooding users with too many updates
- Deactivation surveys. Just don’t.
- Over-use of
!importantin CSS - Pushing forum support off of .org
- Ignoring the WordPress APIs
- Not providing hooks or filters in your code
- Creating new database tables
- Abandoning your plugin (or, if you have to, how to do it properly)
tl;dr – “Enemy of the (business) people“