WordPress plugin development
-
Who Asked for This Setting? The YAGNI Principle in WordPress on 4wp.dev
Who asked for this setting? YAGNI, “You Aren’t Gonna Need It”, is the principle behind every option you deleted because nobody ever used it. Where YAGNI comes from…
-
WordPress REST API: Schema & Validation
In the WordPress REST API, args do the checking for you. Mark a param as required and core answers 400 restmissingcallbackparam before your callback runs. Give it a…
-
12 Classes for One Shortcode: the KISS Principle in WordPress on 4wp.dev
12 classes. For one shortcode. KISS, “Keep It Simple, Stupid”, sounds obvious until you review a plugin that needs a container, a factory and an interface to print…
-
You Copied It Again: the DRY Principle in WordPress, Explained on 4wp.dev
You copied it. Again. DRY, “Don’t Repeat Yourself”, is one of the first principles every developer hears, and one of the most misunderstood. What DRY really says The…
-
Can DRY, KISS, YAGNI and SOLID Live Together? Essential Principles on 4wp.dev
Coding principles you think you know: YAGNI, KISS, DRY and SOLID. OOP is not one of them. It is the tool underneath that you use to apply them.…
-
WordPress Abilities API: what is this?
The Abilities API is the list of what your WordPress site can do and what it allows. Core, your theme and your plugins each add their own abilities.…
-
Custom REST Endpoints in WordPress
wp/v2 belongs to WordPress core. Your plugin needs its own namespace. Real code from our plugins on wordpress.org: Go deeper
-
PluginDocumentSettingPanel: 0 Clicks, Already There
AI writes the code. You make the right choice for the user. 🧩 PluginDocumentSettingPanel puts your setting right in the Page / Post tab of the WordPress block…
-
PluginSidebar: When Your WordPress Plugin Needs Its Own Panel
AI writes the code. You make the right choice for the user. 🧩 PluginSidebar gives your plugin (or theme) its own panel in the WordPress block editor, next…