WordPress

Maria Speaks Episode 25: WordPress.

A discussion of the WordPress blogging platform.

Transcript:

Hi, I’m Maria Langer. Welcome to Maria Speaks episode 25: WordPress.

First of all, I have to apologize for not keeping up with the podcasts as promised. Although I have plenty to write about in my blogs, I don’t seem able to get it together for a podcast. I know there are podcast subscribers out there waiting for new content, but none of them have provided any feedback about what they’d like to hear. So I’m just kind of floundering around without guidance, waiting for someone to give me an idea.

To make matters worse, I had a bit of surgery early in May and have been recovering more slowly than I expected. I’m okay — I’m just a little slow — and you can take that any way you like because it probably applies. It’s very frustrating for me. I can’t wait until everything’s healed and I can really get on with my life.

Today I decided to do a podcast about WordPress. Those of you who read my blog know that I use WordPress now to create and maintain not just my blog but my personal Web site and my book support Web site. You also might know that I’m co-authoring a book with Miraz Jordan about using WordPress. The book, which is for Peachpit Press, is called WordPress 2 Visual QuickStart Guide and it should be in stores by June.

WordPress is, on the surface, a blogging platform. With PHP, MySQL, XHTML, and CSS under the hood, it offers an easy-to-use, Web-based interface for adding posts, managing categories, handling comment moderation, and performing other blog-related tasks. A novice user can use WordPress without knowing a thing about what’s under the hood. But a user with some knowledge of HTML and CSS could go nuts customizing the blog’s appearance. Add a little knowledge of PHP and plugins available to WordPress server installations and the sky’s the limit on blog customization.

But WordPress is more than just a blogging tool. It’s a complete content management system. That means you can use it to build an entire Web site, with static pages and navigation. This is what I’ve done with the two sites I recreated with WordPress: aneclecticmind.com (where you can find the transcript for this podcast) and wickenburg-az.com. WordPress is a perfect tool for maintaining a Web site that needs fresh content added regularly because its blog format automatically displays new content on the home page and archives old content so it’s always available. No need to code HTML and manually revise pages. WordPress does it all for you.

When I first started using WordPress last year, I got very excited about it very quickly. Finally, a Web publishing tool that gave me the power to create my own custom solution without knowing XML. (I never did bother to learn XML or JavaScript, both of which are popular programming languages for Web publishing.) I realized that I could customize my sites little by little, tweaking them to meet my needs. It was a dream come true — a Web publishing project that I could work on forever without it ever looking only partially completed.

Best of all, WordPress is open source software built with open source software. That means its free for most uses.

WordPress comes in two versions: WordPress.com and a WordPress server installation. Let me take a moment to explain the differences between the two.

WordPress.com is a Web site built and maintained by the WordPress development team. Users can create a free WordPress.com account and immediately start blogging. There’s no need for a server or a domain name or any knowledge of any programming languages. WordPress.com bloggers have some control over the appearance and navigation options of their blogs, so they can personalize them to some extent. A WordPress.com account is a great, free way for novice bloggers — or bloggers on a budget — to get their words out.

A WordPress server installation requires the blogger to either install WordPress on his own server or on an ISP’s server. This requires a bit of technical know-how, as well as certain versions of MySQL, PHP, and an Apache-compatible Web server to be installed on the server. It isn’t difficult to do — after all, I managed to do it on a spare Macintosh G4 running Mac OS X Tiger server. But you can also set it up on an ISP’s server if the server meets the minimum system requirements. I was able to set it up, for example, on a GoDaddy.com hosting account. A WordPress server installation is a costlier and more complex way to use WordPress, but it does give you complete control over the way your WordPress-based Web site looks and works. Only through a server installation can you fully customize theme files and install WordPress plugins.

No matter how you set up your WordPress blog, it’s easy to create blog entries and static pages. Just use a Web-based form with just about any Web browser — I prefer Firefox — to compose and edit content. The blog’s administrative interface gives you access to all the tools you need to set up categories, moderate comments, add links and blogrolls, and manage user accounts. WordPress.com server installations support multiple blogger accounts for a blog, making it great for a site that’s built and maintained by multiple people. Content appears online immediately, as soon as it’s published.

It’s also easy for blog readers to enter comments about your entries — if you allow commenting. This creates a dialog between you, the blogger, and your readers. (A two-edged sword sometimes!) Both types of WordPress installations have comment spam prevention tools, so you don’t have to worry much about comment spam.

There are millions of blogs out there, millions of bloggers sharing their thoughts with readers. If you’ve always wanted to be one, why wait? Visit WordPress.com to get started.

But if you’re like me and are just looking for that perfect Web publishing tool to make your sites easy to build, customize, and manage, a WordPress server installation may be just what you need.

Short and Sweet

I switch back to the summary option for RSS feeds.

I gave it some thought. Lots of thought. I realized that I was one of the few bloggers out there who was publishing a full-text RSS feed. That’s not a big deal if every post is just 100 or so words. But most of mine are longer — considerably longer. By sending out a full-text feed, RSS feedreader users had no reason to visit my site.

I spend a lot of time on my site. I add features. I tweak appearance. I tweak features. I experiment with WordPress features. I get a great deal of pleasure out of molding my site to meet my needs. It’s as close as I get to programming (and it’s close enough).

I’d like to get comments on what I write. But people who access via RSS feed don’t come by to read the articles so they don’t come by to post comments, either. (Unless they’re pissed, it seems.) So I don’t get as many comments as I’d like to see. (I’m sure this post will generate lots of nasty comments.)

I also don’t like what I’m hearing about other bloggers stealing content from full-text feeds and displaying it as their own on their sites. This will make it just a bit tougher. (At least I think so.)

So I toggled the Syndication Feeds option in the Reading Options administration panel to Summary. And from this point on, only the first bit of content for each article will appear in my feed. If you want to read the article, come on over and read it. Otherwise, be satisfied with the summary.

After all, that’s what everyone else is giving you, isn’t it?

Gravatars Update

I’m having second thoughts about that gravatar feature.

Last Saturday, I added a gravatar feature to this site. As I discussed in this article, the gravatar image for anyone who had one would automatically appear when they wrote a comment on this site. Just a kind of cool and funky way to add more personality to the site. Not that we get so many comments here.

On Saturday, I also submitted my own gravatar for rating and approval. And I’m still waiting for it to be approved.

Now in this day and age, we’re all pretty accustomed to immediate gratification. You apply for something online — a new account to access a Web site, etc. — and you get an e-mail message with approval within minutes. This is commonplace. So the fact that I’ve been waiting five days for a perfectly acceptable photo (G rated, I assure you) to get approved makes me wonder how serious the folks at gravatar.com are about this system they set up.

I was over on the site and it appears to be the work of a single very talented but very busy person. He’s working on Gravatar 2.0 (whatever that is) and asked for volunteers to help him rate and approve new submissions. Over 100 people volunteered, including me. I offered up to an hour a week until he was caught up. I didn’t get any reply.

The forums are a mess of extremely frustrated new users (like me) who have been waiting to use the feature. Some of them claim they’re embarrassed because they set up the feature on their sites and they’re one of the few people who don’t yet have a gravatar. I don’t feel that way. I don’t expect most of the visitors here to have one. But I am anxious to see if I implemented it correctly and the only way to do that is to see a comment from someone — like me — who has a gravatar.

Part of me urges those of you who are interested to go to gravatar.com, apply for a free account, and submit an image. Then kindly remind the management there, in the forums, that you’re waiting. Maybe that’ll put a fire under their butts and they’ll use some of those volunteers to rate and approve all the gravatars in the queue.

The other part of me says forget about it. Maybe it was just a bad idea.

I’ve always had a problem with patience. Maybe this is a test.

In any case, I’ll let you know when my gravatar appears so you can see how it’s implemented on this site. I’ll probably write an article about it for WordPress users, too. But first I need to make sure I got it right.

Time, apparently, may tell.