Further notes on WordPress
As hinted at in my last post, I have been fairly active in exploring WordPress recently. In particular, my excursions into the blogosphere have, until recently, mostly consisted of stumbling onto various blogs during researches, often followed by just reading that blog from beginning to end (skipping entries that turned out to be uninteresting, obviously): This way, I have built up a great mass of read blog entries, but without any continuity, little “compare and contrast”, and no view of the writers side (apart from the very different platform of OpenDiary)—and my recent activities here have given me much deeper insights into WordPress, how different blogs come across, how the writers side works, etc.
A few observations (with a tendency towards griping) on the more technical side:
The whole “theme” thing is done the wrong way around: The themes should not be applied by the authors to their own blogs, but by the readers. This would make for greater consistency, make life easier for the readers, and avoid many annoyances. An article on my website on Separation of content and layout can provide a bit more information about what I mean.
As an aside, OpenDiary has the same problem—and there I usually used Opera’s UserCSS functionality to just override anything the diarists had concocted. (Note that the themes there are not professionally ready made, like here, but entirely the work of the individual diarists. The result is a high frequency of truly abhorrent designs, with extremely bright and contrasting colors, red text on black backgrounds, and other variations that make the readers eyes hurt.)
The administrative area is abysmally slow—a price to be paid for the extensive functionality. In the weighing of costs and benefits, I am the opinion that WordPress should have been content with less. (Reservation: My time here is sufficiently short that this could conceivably be a temporary shortage in band-width or server capacity. If so, I may have to revise this statement. Under no circumstances, however, would I like to deal with WordPress over a cell phone or a dial-up connection.)
For some reason, HTML text entered with line-breaks is distorted by the artificial addition of paragraphs according to these line-breaks. Really unprofessional: The point of HTML (as opposed to Rich-Text or WYSIWYG editors) is that the actual HTML code can be entered (typically pasted from elsewhere) and be interpreted in the same manner as if it had been written in a plain HTML document.
The Snap previews of links are evil. Compare a discussion on another bloge. I urge my fellow bloggers to follow the advice of that post and turn Snap off. Further, I re-iterate my comment on that post that this is a functionality that should be provided and configurable on the browser level, not on the blog/website level (similar to themes above).