Several years ago, WordPress introduced a feature called The Customizer. The Customer is a panel that theme develoopers can implement to make controlling how a theme looks and acts easier. It’s a great idea. Sort of.
The way you use WordPress is personal and once you do it long enough you develop habits to match your WordPress Environment. If moving WordPress Admin Menu items around seems important to you, there’s a new plug-in that makes it easy
When WordPress announced forced automatic plug-in activations in WordPress 4.2, The WordPress Helpers had your back; we helped get a huge WordPress Plug-in problem reversed. But a feature snuck into WordPress 4.2 that’s way worse. When you create a link in WordPress 4.2 you don’t control the title tag of the link.
The best rationale for the WordPress 4.2 Problem with input-field repurposing was that changing the user interface from a two-field input scenario to a three-field one was a bad decision. But if that’s so, it’s an even worse idea for a dialog box to sometimes have two fields to fill in and other times have only one.
“Making it Rain” is one of those phrases that you’d think everyone would grok naturally. But while making it rain is shorthand in most businesses for “selling a lot”, it has a slightly more abstract definition, too. Making rain really just means “getting it done”, and it can be almost anything.
The WordPress REST API could be the death of WordPress.
Replicating your web site all over the world will speed up content delivery under some geographically-oriented circumstances. And at least in theory a CDN creates redundancy to cover against down-time on a single server.
The WordPress Media Library is a terrible tool; it isn’t as though it helps you back up images very well, after all, and as an integral part of The WordPress Ecosystem the WordPress media library should be more useful than its poor design renders it.
WordPress Security is far from broken. We didn’t need a WordPress Security White Paper. But with constant hole-patching like WordPress itself locking down security in Jetpack, and releasing WordPress 4.21 just a couple of days after 4.2, building better WordPress security sure seems like a solid idea.?
