A few years ago, when I first started seeing HTML e-zines in my inbox, I admit I was jealous. They were attractive, attention getting, snazzy. They made my text e-zines look boring.
But my mind fought the idea of upgrading my own. "My readers appreciate my e-zine for its content," I told myself. "They don't need some slick design to get their attention. They just want my information, straight up. Publishing in HTML won't make a difference."
I was wrong.
Well, I was right that my readers receive my e-zine for its content. After all, that's why they subscribed - for my concise, how-to articles.
But I was mistaken that a better "presentation" wouldn't make a difference.
After much deliberation, I decided to give HTML a whirl. I had my e-zine professionally designed in HTML, featuring my logo, colors, and photo.
First off, let's all agree that it's ridiculously easy to publish in text. That's a good thing.
If you're just beginning your e-zine and are a bit overwhelmed, text is a great place to start. You can then focus on developing great content and publishing on a regular basis, without worrying about HTML design and coding snafus.
Text also gives you complete freedom and flexibility - you can add new sections and delete others any time you feel like it, without having to redesign your entire e-zine.
But let's face it: There are hundreds of thousands of text e-zines out there that all look the same. I subscribe to 30+ text e-zines, and they all seem to lump together in my e-mail inbox.
The ones that catch my eye and make me read on - they're HTML.
>
"Okay, okay," you say. "I know HTML e-zines look great. But do they get better results?"
I'll let these statistics answer that question: