Posted by Whitney on 08/4/08 in
Technical writing
Tom Johnson opened some old wounds with his post last week about WordPress’ biggest mistake — the mistake being the dearth of good documentation for WordPress users. It’s another example of how, in mid-2008, there are still organizations that don’t get the value of having a technical writer on the payroll, either as a staff member or a contractor, to make their products more usable and, therefore, more attractive to users.
Tom wrote: “WordPress documentation is only getting worse. Is there not at least a 100 page manual that you can download (rather than buying a third-party book from Amazon)? … Blogger has much more marketshare because it’s an easier platform. WordPress could be more competitive in the marketplace if they simply hired a full-time technical writer to — I know this is shocking — add an online help file directly inside the application.”
I started a rant in his comments section, some of which I’ll repeat here. There’s a faction out there that insists that WordPress (the one you can host on your own site) is easy to use. So…if WordPress is easy, why is there a huge cottage industry of independent geeks and pros who do nothing but set up, extend, and troubleshoot WordPress for everyone else? If it’s so easy, how come some of these people get away, repeatedly, with charging folks $400 or more just to upgrade someone else’s WordPress blog to 2.5?
Because it’s NOT.
I’m technically competent. I can replace a motherboard, install a second internal hard drive, set up a wireless network, put up a Web site, even do a little JavaScript (even though I hate it). I can do most anything with good documentation. But I find standalone WordPress to be obtuse. The scads of WP plug-ins make it difficult to tell what you really need, at minimum, unless you want to make learning about WordPress your new hobby…which I don’t. The so-called documentation makes it worse
The WP documentation needs to be better, as does the documentation for the plug-ins. The widespread use of WordPress demands better user support — a level that can’t be obtained by volunteers who write when they have the time. It requires a dedicated effort by a dedicated staff that works together to create a uniform documentation set. And if WordPress does, indeed, now have $29 million in funding, they can darn well afford a couple of technical writers.