Web Site vs. Blog

What’s the Difference?

Today I got a phone call from our local newspaper’s “business advocate” — the guy who writes stories about business. He was researching an article about blogging and figured that I was the most active blogger — if not the only blogger — in town, so I might be able to to provide some information about it. He wasn’t aware that I’d co-authored a book about WordPress blogging software (WordPress 2: Visual QuickStart Guide) in 2006 and he probably wasn’t aware that I wrote Putting Your Small Business on the Web back in 2000. He probably also doesn’t know that I’ve written four books about Web authoring software (various versions of PageMill, now defunct) and that I’ve been building and managing Web sites since 1994 (although I’m not crazy enough to do it for a living).

We stumbled a bit in our conversation. He referred to my Web site, wickenburg-az.com, as a blog. (The site has been around since 1999, predating the blogging phenomena by at least 3 to 4 years.) I responded that it wasn’t a blog, that it was a Web site built with blogging software. And then he asked me what the difference was.

I had to think about it. What is the difference between a Web site and a blog?

They’re very much alike.

Let’s take a look at the similarities.

  • Web sites and blogs are both published on the Web and can be read with any Web browser. This gives them the same basic look and feel and similar user experiences. Web sites built with blogging software can look and feel just like a blog, even if that’s not what they are intended to be.
  • They depend on good, useful content. Web site visitors and blog readers come to read content. If the content is good and meets their needs, they’ll be back for more. If the content sucks, they won’t.

But they are different.

Of course, I needed to explain how they were different — not how they were the same. The response I came up with centered around the purpose of visitors coming to to the site, but there are more differences.

  • Web site visitors come to a site to look for specific information. That information does not need to be new. It just needs to be what the visitor is looking for. For example, I visit the HP Web site when I need a new driver for one of my printers. I know it’ll be there and I don’t care if it’s been there for five years. People visit wickenburg-az.com to get basic information about Wickenburg: what it’s like, what to do there, etc. But blog readers visit or subscribe to blogs to get fresh information or insight on topics that are important to them. I read ProBlogger, for example, because it has timely articles that can help me understand how to be a better blogger. People visit aneclecticmind.com to read articles like this one about blogging, or other articles about flying, or even other articles about what it’s like to live in a place like Wickenburg — all from my point of view.
  • Blogs tend to be more opinion-based than Web sites. Sure, HP is going to tell you on their Web site that their printers are the best, but what would you expect? On my blog, I’ll tell you what I think about my HP printer and compare it to other printers I might own or have experience with. I’ll also tell you what I think of Apple Geniuses or local restaurants or life revolving around the Internet. (Although some locals might find this hard to believe, I keep most of my negative opinions of Wickenburg out of wickenburg-az.com. Most.) The opinion aspect makes blogs more personal than a Web site.
  • Blogs rely on fresh content. It’s commonly accepted that a blogger should post at least 3 to 5 new entries a week. Web sites, on the other hand, are more static and don’t require as much updating. Their visitors don’t expect it, either.

Does it matter?

Who knows? But it’s made me think about blogging a bit more than usual lately. And I’m sure it will lead to a few more articles here about what makes a blog a blog in the near future.

On Geniuses

Why I don’t Genius Bar hop and other comments regarding my recent hard disk problem.

One of my jobs as a blogger is to produce at least one blog entry a week. As you may have noticed if you follow this blog, it looks like I’ve been slacking off lately. Well, I just want to take a few moments to assert that looks may be deceiving.

Last week was a busy one for me. I finally got my computer back up and running after its second hard disk crash in a year. This crash was far more serious than the last and required the geniuses at the Apple Store to fix.

Now I know that lots of Mac pros laugh at the word “genius” when applied to the Apple Store’s tech support folks. And I do agree that it would be difficult to call any of them geniuses in the true sense of the word. (Think Einstein.) But if you were to compare their computer skills to the average Mac user’s, they could indeed be considered geniuses. They know a lot more about the current computer models than 95% of Mac users. Sadly, I fit into that 95% these days. I could tell you all kinds of things about fixing a Mac II cx or a PowerMac 7100/66 — and that’s because I used to teach a course about troubleshooting those computers running System 7. Nowadays, my troubleshooting capabilities are limited to what I need to know — like much of my other knowledge — and I don’t really need to know all the things the geniuses need to know to do their daily fix-it jobs.

So I’m not uncomfortable applying the word genius to many (but not all) of them. To me, some of them really are geniuses when it comes to diagnosing and fixing Mac problems.

I’ll also be the first to say that the capabilities of an Apple Store genius staff on any given day for any given store is hit or miss. It all depends on each staffer’s experience, knowledge, and interest in the topics he or she needs to know. I was at the Genius Bar in the Chandler, AZ store on Monday and the geniuses that day were pretty good. One of them was a super genius, the one who helped me was definitely above average, and the guy working the iPod slot was about average. (Let’s face it: it doesn’t take much skill to fix an iPod problem. Every iPod should come with a cheat sheet printed on back that explains how to reset it; that will resolve 95% of an iPod’s problems. The iPod guy probably resets a lot of iPods in a day. I’ve gotten so good at it that I can reset mine with one hand while flying my helicopter. Darn vibrations lock it up more often than I’d like to admit.)

I’ve had repeatedly bad luck at the Biltmore Apple Store in Phoenix, which is at least 30 miles closer to my house. The two times I tried to get assistance there, the lead Genius didn’t seem interested in looking deeply into my problem and didn’t seem to care whether it was resolved or not. On my fried motherboard problem, it seemed that she spent more time telling me how much it would cost to fix the problem than diagnosing what the problem was. This, coupled with her obvious lack of sympathy, made me doubt her diagnosis, so I had to go to another store (Chandler) to get a second opinion. I got a bad taste in my mouth (so to speak) from the experience. And that’s why I don’t go to the Biltmore store anymore.

Oddly enough, sympathy for my problem seems to be important to me. My main work computer or “production” machine (currently a Dual G5) is like a partner to me. It holds onto the projects I’m working on, it has the tools I need to get the job done as smoothly as possible. When it works right, we’re a team getting the job done. When it starts acting up, I get concerned. It’s not just a machine on the fritz. It’s a work partner feeling ill. What’s the problem? Can I fix it before it becomes critical? Is its motherboard about to go (again)? Or its hard disk? Will I lose data? Will I need to take it to the hospital (fix-it place) to get it working right again? How long will we be apart? And, of course, the selfish questions, like how long will I be unable to work?

The geniuses at the Chandler store are always sympathetic to my problem. They understand that my computer isn’t just a machine I use for e-mail and to surf the Web. They understand that its hard disk contains lots of important information — including books in progress — and the tools I need to get my work done. They understand that without my production computer, there’s very little real work I can do. And even though they don’t necessarily push any harder to complete a job for me than they do for anyone else, they make it seem as if my problem is one of the most important ones they’ll tackle that day. And they soothe me with reasonable reassurances that make it easier to face the 90-mile drive home and wait for their call.

This time around, the problem was a toasted hard disk. Personally, I believe it has something to do with my Firewire ports — it occurred while my iSight was plugged in and I was attempting to suck something off a portable Firewire hard drive. (My motherboard problem also manifested itself when working with multiple Firewire devices, including an iSight, so I’m very wary of using it these days.) They replaced the hard disk — which IS something I could have done myself if I really wanted to — and managed to get about 50% of the data off my old hard disk before it ceased to function at all. This cost me dearly, but the way I see it, I was paying for my own stupidity. If I’d had my entire Home folder backed up, recovery wouldn’t have been necessary at all and I could have saved the $150.

What hurts even more is that I’d written an article for Informit.com about backing up with Fetch before I had the problem and neglected to utilize my own instructions to protect myself.

The computer was done the next day and my husband, Mike, picked it up on his way home. It isn’t exactly on his way — he works about 15 miles north of there — but it was a lot more convenient for him than for me to make the 180-mile round trip drive. On Wednesday morning, I set about restoring the whole computer to it’s normal setup. I didn’t like the way the Apple folks had set up the machine — for some reason I was really bugged about my home folder being called maria (note the lowercase) rather than its usual mlanger (which I’ve used on all my computers for years). (Is that anal or what?) So I pulled off the recovered data, reformatted the hard disk, and spent the next two days installing software and updates. The updates were particularly painful now that I’m on the super-slow wireless Internet connection I whined about elsewhere in this blog. The 139 MB Mac OS X 10.4.8 combined updater took quite a while to suck off the Internet before I could install it.

Fortunately, I managed to pull e-mail messages, endo settings and contents, ecto contents, and some other stuff off my PowerBook. My iCal and Address book data was already set up to synchronize with .Mac, so getting all that data moved over was very easy. The only thing of real value that I lost was Chapter 6 of my Excel 2007 for Windows book, which I’d been working on for the second time. (The first revision went bad and I started from scratch. So today I look forward to starting my Chapter 6 revision for the third time. I knew it would be the book’s Chapter from Hell, but I couldn’t imagine how hellish it would be.)

By Friday, the computer was 90% back to its old self and I was working on it regularly instead of my laptop. So I was out of commission for two full weeks. I blame myself for that, too, letting the disk recovery software run as long as I did before finally bringing it to the geniuses.

Telephone Support for the Price of a Book?

Not likely.

I was driving down to the Phoenix area yesterday — my first time driving down there in months. It was a beautiful day, sunny with temperatures in the 70s. I was driving my little Honda with the top down and my iPod, connected to the stereo, blasting some classic rock. I had a 30-mile drive ahead of me on Route 60 (Grand Avenue) to get to the nearest PetSmart (or is it PetCo?), where I planned to buy some tropical fish for my aquarium. Route 60 isn’t the most pleasant road to drive on, but it’s nothing to complain about in the stretch I was driving.

I was having a good time.

My cell phone rang. The only reason I heard it is because it’s on vibrate mode and my ears were not necessary. I hit the mute button on the stereo and answered the phone.

The woman on the other end was difficult to hear at 65 mph in a convertible, so I pulled over. After all, she could be a customer for Flying M Air and I needed to hear what she wanted and to give her my full attention.

The words started coming through: QuickBooks. Book. Non-profit. How do I print checks?

It took all my patience not to explode. Apparently, this woman thought that since I’d written a book about Quicken for Windows and another book about QuickBooks for Macintosh, I could help her figure out how to print checks from the non-profit version of QuickBooks for Windows, which I had never even used, let alone written about. I don’t know where she got my phone number — it’s no longer on this site because of calls like hers — and I don’t know where she got the idea that the author of a book about a software product would be her free, technical support hotline.

I set her straight, hung up, and got back on the road. I was fuming for a short while, but the music and wind and great weather soon soothed me.

Here’s what people don’t seem to understand:

  • A book’s content is determined, in part, by the book’s project editor and page count. So an author cannot include coverage of every single nuance of a software program. The least used features are left out to make sure there’s room for the most used features.
  • An author cannot write a book about a topic unless the publisher feels that there’s enough of a market for the book to sell. That’s probably why this person could not find a book covering the not-for-profit version of QuickBooks for Windows. It’s also why I did not update my QuickBooks for Macintosh book to cover QuickBooks 2007 or my Quicken for Macintosh book for any version after 2003 (I think).
  • An author receives, on average, less than $1 per book sold. I don’t know where anyone can get one-on-one, completely personalized technical support by telephone for $1. (Even the folks in India use a script.) My point: buying one of my books does not entitle the reader to interrupt my day by telephone to ask questions about the book’s content or topics not covered in the book at all.
  • An author certainly cannot be expected to provide support for another author’s book. True story: I once got a question in my old FAQ system from someone who told me he’d bought a book by [insert author name here] and was having trouble understanding it. Could I help him? He wasn’t joking. Neither was I when I told him to contact the author of that book, not me.

This might seem like a hard line to take, but I don’t think so. I do a lot to support my work and provide content above and beyond what’s between a book’s covers. The Book Support categories you see listed near the top of the navigation bar are just an example — each one provides additional articles somehow related to a specific book. My Q & A system is also set up to receive questions that I can answer in a place where all readers can benefit from them.

That should be enough.

Understanding the Rules of Great Content

Somewhat related to my Three Types of Blog Entries post…

In trying to catch up with the RSS feeds I subscribe to, I ran across an article titled “Understanding The Rules of Great Content” on ProBlogger Blog Tips, which says, in part:

In your quest for creating excellent content, you may have come across the following dilemma: I would love to create something important for my blog, but how do I, as a “mere” blogger contribute to that conversation at large? If I don’t create something de novo, will it be worth posting?

To answer that question, let me tell you about the 1 / 9 / 90 rule — and, in my humble opinion, its a rule that every blogger ought to live (and subsequently), die by.

In a way, the three types of blog posts I wrote about correspond to each part of the “rule” discussed in the article. The 1 is for 1% creating content — that’s where my “full-length articles” come in. The 9 is for 9% enriching content — that’s my “analysis of Web content.” And finally, the 90 is the 90% consuming content — that’s my “link lists.”

Although I’m not quite sure if I agree with the percentages — I’d rather see a 10 / 30 / 60 rule — I find it interesting that Tony Hung over at Problogger.net should come up with the same basic idea that I did, right around the same time. It’s as if we were both thinking about the kinds of entries a blogger could write but came up with different ways to say the same thing.

If you found my post interesting, I highly recommend that you read Tony’s. He goes into more detail about how to stay in that 9 percent.

As for this post, it falls into the 9 percent category. (Or at least I hope it does.)

5 Ways to Make Your Blog Posts More Readable

Learn five easy tricks to help pull readers into your blog posts.

Okay, so you’ve written an article for your blog and you’re all ready to publish it online. You’re confident that the article’s content is well-written. And you’re sure it will appeal to your blog’s regular readers.

But wait! Before you put it out to be read by the world, have you done what you can to make it more readable?

By readable, I mean formatted in such a way that visitors will be drawn into its content and want to read every word. Or have you simply composed 20 paragraphs of good, solid information, formatted as big solid blocks of text?

No matter what blogging tool you use to publish your blog, you should have access to the standard array of formatting features available in HTML. In this article, I’ll explain how and why you should use them.

Break Up Long Paragraphs

What’s less attractive on a Web page than solid blocks of text? Long paragraphs of unbroken text can intimidate readers. They look unapproachable, like a college textbook. (For me, they bring to mind the textbook in my college tax accounting course, which further reminds me of two semesters of boring hell on Mondays, Wednesdays, and Fridays.)

Break up long paragraphs at logical points. This will require some writing skill, since you can’t arbitrarily chop paragraphs up — each one must still communicate a complete thought. But shorter paragraphs are a lot less intimidating than long ones — a point that applies to sentences, too (although I can’t seem to get that one into my thick skull).

And one more thing about this: be sure to use a space between paragraphs (usually with the

tag rather than the
tag, if hand coding is required). On the Web, that’s the standard way to end one paragraph and begin another. Just starting a new line isn’t going to break the paragraph at all — at least not in the eyes of the reader.

Use Headings

Headings cue the reader about the content of paragraphs that follow them. For example, my Use Headings heading here tells you that I’m going to talk about headings in this paragraph and, likely the few that follow up until the next heading. Readers can scan your article’s headings to get a better idea of what the article covers.

Of course, there are two kinds of headings. There’s the kind that actually reflects what’s in the paragraphs they head — that’s what I’m using in this article. And then there’s the kind that doesn’t quite explain what the following paragraphs are about, but are humorous or witty. Both types can work, but for serious content, I recommend the first type.

Headings can also help with search engine optimization (SEO), but not being an SEO expert, I can’t elaborate much about this. I seem to recall reading that h1 and h2 level headings are more effective for SEO than other lower levels. I use h3 because that’s how formatting is set up on my blog and I’m not terribly concerned with SEO. If SEO is very important to you, you might want to look into this claim. Of course, for headings to be effective at all in SEO, they must be coded as headings using

and tags (or other level tags as appropriate) around them. The appearance of text coded as headings will vary depending on settings in your style.css file or other style information for your blog. (And now we’re getting a little more technical than I wanted to get in this article.)

Format Lists as Lists

If any paragraph in your article includes a list of four or more items that are longer than four or more words each, for heaven’s sake, format them as a list!

There’s nothing so boring or potentially confusing as long lists within a paragraph, especially when those lists include explanations, commas, and semicolons. Why worry about proper in-paragraph list formatting when you can simply create a bulleted or numbered list that’s clear and easy to read?

Lists, like headings, are also extremely scannable, making it easy for readers to get an idea of the content they include. They draw the reader in by giving them information in bite-sized chunks. Bold formatting used at the beginning of a list item (see below) can act as a heading, letting the reader know that an explanation or more information about the item follows.

In summary, lists can do the following for you:

  • Break up long blocks of text. Long lists in a paragraph make big, fat, intimidating blocks of text. Isn’t this much nicer?
  • Make one point easy to distinguish from the next. Since you (and your readers) don’t have to worry about how list items are separated (comma or semi-colon?) you don’t have to worry about someone misunderstanding list items.
  • Take advantage of built-in formatting options. I’m not just talking about standard bullets and hanging indents here. As you can see in this list, a blog’s style.css file can include instructions for graphic bullets or other fancy formatting.
  • Give your readers important points quickly. By presenting information in an easily scannable format, your readers can see what a list is about without wasting time. If it’s what they want to learn more about, they’ll dive in and read it.

Apply Other Formatting…but Sparingly!

There are other, more basic formatting features you can apply to text. Want some basic information to stand out? Use bold formatting (as I did in the bulleted list above). Introducing a new word or phrase? Italicize it. Got a quote to share? Here’s what I say:

If it’s longer than a dozen or so words, consider putting quotations between

and

tags. This clearly identifies the text as a quote from another author. (Well, in this case, it’s still words of wisdom from me, but you can quote me if you like.)

Don’t use ALL CAPS. It’s childish and unprofessional and considered by many to be “shouting.” And don’t use underlines. On the Web, underlines indicate hyperlinks and you can confuse your readers.

And don’t use too much formatting. There comes a point when the repeated application of bold and/or italic formatting loses meaning and simply fails to do the intended job.

Insert Illustrations

I’m a firm believer in the old adage: “One picture is worth a thousand words.” Maybe that’s why I’ve been writing Visual QuickStart Guides for Peachpit Press since 1995. Those books are full of screenshots — mine average 3-4 per page — and are excellent tools for teaching readers how to perform tasks with various software.

In regular writing — such as the writing you might do for your blog — images can also help communicate information. Did you write a software how-to piece? Screenshots of the steps would be extremely helpful. Did you write about a recent vacation? Include a few photos to show the scenes you’ve written about. Does your article explain the organization of a company or one of its departments? Include an organizational chart to put things in perspective.

On the Web, images do more than just communicate information. They also add visual appeal. Think about it as you visit sites on the Web. Which pages or blog posts caught your attention more? The ones without images? Or the ones with photos or drawings?

If you don’t have illustrations for your article and you want to include some other kind of graphic element, try text in a box. This effect, which is often used in print publications, can add visual appeal almost as much as an image can.

Let’s face it: people like to look at pictures. By giving them pictures that relate to your article, you can capture their attention and reel them in to read more about what the picture shows.

A word of warning here: Don’t use photos that don’t belong to you — doing so is likely a violation of copyright law. You can probably use company logos — if your use is consistent with the company’s rules governing logo use (normally available on its Web site) and you’re writing about the company. But taking photos off another Web site or scanning them out of a print publication for use on your site could get you in a lot of trouble. It’s stealing, plain and simple, and you could get sued. Use photos, screenshots, and drawings that you’ve taken or that you’ve received permission to use. The rule of thumb here is, if you don’t know whether you have permission to use it, you probably don’t.

Conclusion

As you can see, each of these techniques is relatively easy to implement on your blog. While it isn’t necessary to use all of them in one article (as I’ve attempted to do here), you can mix and match them as you see fit to liven up the layout and appearance of your prose.

The main thing to remember is this: the more interesting you make your text appear at first glance, the more likely you are to get readers to stick around and read what you’ve written.

Oh, and by the way, just about everything in this article also applies to your non-Web writing efforts: reports, articles, white papers, and books. You just won’t need HTML code to get the job done.