Last week I did something awful, namely a list post. Luckily it wasn’t one of those linkbaity things that way too many blogs publish to get some extra eyeballs, but still. It was a list and therefore I loathe myself right now.
Get a free WPMU DEV plugin, plus free weekly tips and resources for using WordPress.
And I will continue to do so, because this week we’ll, or more accurately I will, talk about what’s bad with WordPress. Last week was apparantly TDH is being nice week so those of you who thought I was replaced by a doppelgänger at the WPMU.org office (is there one?) can rest easy. Your favorite asshole is back.
Right, so 7 bad things about WordPress then. Here goes.
- The admin interface isn’t user-friendly. I’ve touched this before, while I do think that the WordPress admin interface is one of the better options out there, it still has a long way to go before it will feel intuitive. This is a problem particularly for new users.
- Media management sucks. Well, it doesn’t suck really, but it can certainly be improved. Luckily this is in the works so I hope to cross this from my list in the future.
- There’s no truly useful page tree view. If you work with lots of static pages and are used to more traditional CMS’ then this will bother you. The page list in the admin interface should be tailored to pages hierarchical nature.
- Custom stuff and third-party apps. Sites relying custom post types and custom taxonomies can’t even use the official WordPress app since it can’t handle those (somewhat related). This is a shame, we should be able to solve this some way or the other.
- The admin interface needs to be responsive. Apps are great, but I’d really like the WordPress admin interface to become truly responsive and work on iPhones and Androids. Sure, you can’t upload images, but lots of other stuff will work and since the apps can’t keep up, at least this will let us post on the go if we use custom stuff mentioned in #4 above.
- Cache cache cache. WordPress doesn’t rely on caching plugins as much as it used to, in fact most sites won’t need them. I do think there should be an advanced settings page with extended cache features, something easier to setup than W3 Total Cache, but still there. From this page, help people find more advanced caching alternatives if needed, but get the basic “create flat files” caching stuff in place please.
- Focus less on Automattic’s stuff. Don’t get me wrong, Automattic and the core developers are doing awesome stuff for WordPress and they deserve recognition for it. We’ve talked about this briefly previously, regarding Akismet, but sometimes it gets silly. Like the featured plugins list on wordpress.org right now, featuring six great plugins, all tied to core developers or projects. Not all are Automattic, not at all, but doesn’t it seem a bit one-sided?
It was surprisingly hard writing this list actually. I really love WordPress and are, despite the hard-earned lessons from before, working on a second WordCamp in Sweden this year. WordPress pays my bills and I contribute as much as I can, I write books and I get annoyed when the platform is moving in the wrong direction, or when people are being asshats.
I bitch and I whine and I come across as a negative bastard sometimes, but I do it because I truly believe that WordPress is important. For free speech, for open source, and for making the web a better place.
Seems I got a bit teary-eyed there. Here’s the soap box, I’ll go have a Big Peat and be nostalgic now.
Big Peat? Ralfy knows what I’m talking about:
Rage photo by Thoth, God of Knowledge (CC)