Tagged: javascript

March 9th, 2009

7 Best Practices for Adding Mobility to Your Blog

Front face of an Apple iPhone, including default iconsI’m one of the lucky few who do not yet have a smartphone. That’s right, no iPhone, Blackberry, or Android for me; I’m stuck with an ancient brick of a phone, which is fine because in general, I hate the telephone. But Chris has an iPhone, so I’ve become quite aware of the need for mobile web sites, for I always hear his complaints when he’s on a web site that does not have a mobile version of itself. After checking the browser statistics on LifePointOzark.com and SarahJoAustin.com and noting that on both sites, access from a mobile device has increased even in the last month, I’m more than convinced that our blogs need to be “mobilized.”

So what do we do? The easy answer is to add some mobile plugins that will do all the work for you, and I will get to those plugins tomorrow, but today, let’s consider seven best practices in our everyday blogging to make them mobile friendly.

Best Practice #1: Base Your Blogging on Text
Unless you have a photo or video blog, more than likely, your blog posts are text-based, and text-based posts have smaller file sizes than those with video, photos, or graphics. Smaller file sizes allow for faster load times on a mobile device, which increases the likelihood that a reader will get to your blog and read it.

Best Practice #2: Optimize Media for the Web
If you must have video, audio, photos, or graphics in your blog posts, that’s OK. As you edit your media, find a balance between quality and file size. No, your media shouldn’t look or sound like crap, but at the same time, you shouldn’t ask your readers to wait five minutes for something to load. For images, this means using a compressed JPG format and setting the resolution to 72 dpi; for video, this might mean sacrificing HD quality; and for audio, this might mean compressing an MP3 file.

Best Practice #3: Add Title Attributes to Links
As good bloggers, we should already be adding title attributes to our links for search engine optimization, but I’ll confess, I just started being deliberate about this on SJA. For every link you add, include a title attribute that tells the reader more about the link before the reader clicks on it. Give your reader all the information they need about the link, so they can make an educated decision about whether or not to follow it.

Best Practice #4: Add Alt Attributes to Images
Assuming you’ve followed Best Practice #2 and have only essential graphics in your post, your images are already worth your readers’ time. But some readers turn off graphics to quicken load times, which means they won’t see your illustrative image. Instead they’ll see the image description from the alt attribute. Give them incentive to turn images on by adding a short but powerful description of the image (i.e. not picture of flower but pink and white stargazer lily, close-up). Think of an alt attribute this way: How would you describe the image to the blind? Whatever your answer, that should be your alt description.

Best Practice #5: Don’t Resize Images with XHTML
When you resize images with XHTML, your web page loads the full-sized imaged before resizing it to what you’ve specified. This takes precious time on a mobile device. Instead, edit your image in Photoshop, iPhoto, Picasa, or GIMP; note the dimensions; and add width and height attributes to your image tag. Both Blogger and WordPress allow you to resize images with XHTML when you add images, but don’t take them up on their offer.

Best Practice #6: Keep Text and Style Separate with CSS
This goes without saying for all the blogging platforms I’ve used, but I mention it nonetheless. If you add styles to your XHTML to specify how your text looks, your mobile browser has to “think” through all those styles at it loads the page. Plus, it increases file size. Instead, keep your blog’s structure and text in the XHTML and keep your visual specifications in CSS files. As an added bonus, you can create a mobile style sheet that will render your blog exactly as you like in your mobile device without affecting how it renders on a regular screen.

Best Practice #7: Minimize Javascript
Javascript gives our blogs functionality that is often useful on a regular screen but usually unnecessary on a mobile device. Sacrifice this functionality, and you’ll make your blog load faster by decreasing file sizes. If you don’t want to sacrifice functionality, add Javascript by linking to an external file rather than embedding the Javascript code into your XHTML. As with media, there’s some give and take with this best practice. For example, because I want to collect traffic data for my blog–wherever it is accessed–I leave my Google Analytics Javascript in my XHTML.

Faster Mobile Blog = Faster, More Accessible Blog
These seven practices will not only minimize your file sizes and speed up your blog on mobile devices, but they’ll do the same for your blog on a regular browser. Not only that, your title and alt attributes and CSS will make your blog more accessible to non-traditional readers: primarily those with visual disabilities who use screen readers or those who still have dial-up connection speeds. It’s good blogging either way.

Stay tuned tomorrow for tools that will make mobile blogging and reading easier for you and your readers.

May 12th, 2008

Blogger vs. Wordpress: Who’s Got the Upper Hand?

In the blogosphere, Blogger and Wordpress are two very popular blogging tools, but they’re popular for different reasons. Blogger tends to be the beginner’s place to start because it simplifies the art of blogging and makes it easy for the novice to understand. On the other hand, Wordpress tends to be the intermediate and advanced bloggers’ tool of choice not necessarily because it’s more complicated than Blogger but because in general, it produces more professional-looking blogs. I’ve used both tools, and I like features in both.

After about six months of serious blogging and reading blogs on a variety of topics, I switched my personal blog from Blogger to Wordpress. When I made the announcement, several people asked me why I made the move, but I had a hard time nailing down the reason. I guess I was just ready to try something new—to take my blog to the next level—and I thought Wordpress was the place to start.

Even though I had researched Wordpress and how it functioned differently than Blogger, a few surprises slapped me around once I made the switch:

  1. No custom URL. With Blogger, I was able to direct the original site (sarahjoaustin.blogspot.com) to a custom URL (www.sarahjoaustin.com), which eliminated the ‘blogspot’ in the middle. If I wanted to do the same on Wordpress, I would have to pay $10/year and keep my blog hosted at Wordpress or host my blog on my own. Instead of forking over the cash, I made due for a few months by forwarding www.sarahjoaustin.com to sarahjoaustin.wordpress.com, but I always hated having ‘wordpress’ in my URL, so I eventually broke down and bought my own hosting.
  2. No JavaScript; therefore, no Google Analytics. Too many scripts on a web page can slow down or crash your browser, so Wordpress prevents this problem by banning embedded scripts (including JavaScript) on Wordpress.com-hosted blogs. On Blogger, I used Google Analytics to track my site statistics, but because I couldn’t embed my itty-bitty piece of JavaScript in my Wordpress site, I could no longer use Analytics. But Wordpress has its own stats tracker in every blog’s dashboard, so I could still see the most pertinent statistics for my blog. I just started hosting my blog on my own external server, so now I can embed JavaScript again, but even with Google Analytics available, I still use the Wordpress stats for day-to-day updates.
  3. No HTML or CSS control. Both Blogger and Wordpress have some great themes and templates, but I have some HTML and CSS skills, and I like to customize templates to meet my needs. With Blogger, I could completely manipulate the code to make my blog function as I wanted (i.e. change layout, colors, type, images, etc.), but on Wordpress, once I committed to a template, I was stuck with the template designer’s choices. Some templates allowed me to change header images, but that was about it.

This sounds like a list of reasons why I hate Wordpress, but it really isn’t. When I made the initial switch, I was frustrated because I didn’t know I’d have to give up the control that I loved having with Blogger. I wished someone had lined them up side by side and told me how they were the same and how they were different, and that’s what the table below is designed to do. On the left is a list of features that are important to me as a blogger, and in the Wordpress and Blogger columns are the details for each tool. If the specs are different for hosting on Wordpress and Blogger than they are for hosting on an external FTP server, I’ve listed those, too.

Wordpress
Blogger
Themes/templates
Yep, free.
Yep, free.
Custom URL
(excludes cost of domain name)
Yep, $10/year if hosted at Wordpress.com.
Yep, free if hosted on external FTP server.
Yep, free.
Custom CSS
Yep, $15/year if hosted at Wordpress.com.
Yep, free if hosted on external FTP server.
Yep, free.
AJAX
Yep.
Yep, if hosted at Blogger.com.
Nope, if hosted on external FTP server.
Sidebar widgets
Yep.
Yep, if hosted at Blogger.com.
Nope, if hosted on external FTP server.
Javascript support
Nope, if hosted at Wordpress.com.
Yep, if hosted on external FTP server.
Yep.
Statistics
Yep, automatic if hosted at Wordpress.com.
Yep, must install a plug-in if hosting on FTP server.
Nope, but you can embed Javascript, so you can add Google Analytics.
Multiple users
Yep, up to 35. For unlimited users, it’s $30/year.
Yep, up to 100.

I don’t want to be a blogging snob and tell you that Wordpress is best because your decision should be based on your needs as a blogger. Yes, I use Wordpress for my own blogs, but I manage other blogs that use Blogger and get by just fine. Yes, Wordpress has more (and cooler) templates, but if you have HTML and CSS skills, a Blogger blog can look just as great. Bottom line, both are excellent tools; you just have to evaluate your blogging needs and experiment a little!

 

You need to log in to vote

The blog owner requires users to be logged in to be able to vote for this post.

Alternatively, if you do not have an account yet you can create one here.

Powered by Vote It Up