Site Search:

Archive for June, 2009

5 ways for your library to Fail at Twitter

Author: Laura
June 8, 2009

Twitter has finally hit the mainstream (If Oprah isn’t the mainstream, then I don’t know what is).  So we’re finally seeing more and more public libraries putting their feet into the Twitterstream.  This is generally a good thing; however, I am also seeing more and more libraries just dipping in their toes without really understanding what direction the water flows or which bathing suit to wear.

(Ok, enough with the water analogies.  Let’s face it:  some libraries are not using Twitter to its fullest or are making errors that will prevent them from actually reaping the benefits of the work they may be putting in. )

In order of importance, from least to most important, here are my top 5 ways that public libraries are failing at Twitter:

  • Failing to use current terminology. I was caught out on this one myself recently; thankfully, it was in an email and not in an actual tweet where people could see it.  But the verb form is “to tweet,” not “to twitter.”  Using the wrong term is like putting a big pic of your library online with the word “newbie” scribbled across it.
  • Failing to post a picture. Not posting a pic/logo/icon/avatar/gravatar/picture/something is not only a newbie error, it is a sure way to ensure that your library doesn’t engender any trust.  Use your library’s logo not just to lend credibility to the account, but to emphasize your comprehensive branding efforts (because your library has those, right?)
  • Failing to actually link to the Twitter account when promoting it. Your library’s account on Twitter has a special URL you can use to send people there directly.  The syntax is “http://www.twitter.com/YOUR_USER_NAME_HERE”  Be sure to use it and not just tell people on your web site that you have a Twitter account.   Chances are, nobody is going to go looking for your Twitter account later.  Give them a direct link.
  • Failing to follow back. No, your library doesn’t have to follow everyone back.  But if you can identify that someone is from your service area, at the very least follow THEM back.  It’s a courtesy.  Not following anyone back is a clear sign to potential followers of your library that you’re not on Twitter for the right reason (see the next point).
  • Failing to engage in conversation. This is the most important thing about Twitter.  Twitter is a two-way application.  It’s not just a matter of shouting into the ethernet void.  Viewing Twitter as only a broadcast service is not only failing to utilize Twitter properly, but is a virtual slap in the face to the people who follow you.  Nobody wants to talk to a wall!  Almost certainly, they want to ask you/your library questions or make commentary.  They will assume that is why you’re on Twitter–not just to make announcements, but to interact with them.  Learn about using the @ symbol in replies and talk to your followers.
[Bloglines] [del.icio.us] [Digg] [Facebook] [Fark] [Furl] [Google] [MySpace] [Reddit] [StumbleUpon] [Technorati] [Twitter] [Windows Live] [Yahoo!] [Email] More »


read comments (4)

CSS Part I: Why you need them

Author: Laura
June 2, 2009

scary words–> CASCADING STYLE SHEETS! <–scary words

Are you scared?  Cowering in a corner?  (Okay, I suspected you weren’t.)   How about uncomfortable?  A teeny bit?

If you’re a regular user of CSS, you probably think I’m a bit nuts.  If you’re not, you might feel intimidated by the idea of using Cascading Style Sheets instead of those old <font> and <b> tags in your web pages.  Or, you might not even know what Cascading Style Sheets are, except that they’re just one more thing you’re supposed to know about and don’t have the time to learn.

In Part I, I’m actually not going to talk so much about about what CSS is, as much as why you need to make the time to learn it.  “What” and “why” are really difficult to explain separately, so no doubt there will be some intermingling here.  But I’ll give it a shot.

Why should *I* learn CSS, Laura?

  • Power. Lots of it.  [Insert evil laugh here.]  With CSS, you have extremely granular control over how your web pages look; much more power than using old HTML.  With CSS, you can change things you never could with just HTML–positioning elements on the page in particular.  With much more finesse to boot.  You also get, at no extra charge, the ability to manage how EVERY page in your site looks from one central location.  It’s like the display control panel for your entire site.  No more changing inline code on every #@$! page of your site when the library’s logo colors change and the whole site has to match the new color scheme.
  • Standards-compliance. I covered this in a separate post, but it’s worth bringing back up here:  using those old tags immediately makes your site’s code non-compliant with current coding standards.  Sorry, there are no exceptions.  As soon as you start putting those old tags in, game over.  Your site  now immediately qualifies for 1) Non-professional status and also likely for 2) Visitor frustration, especially if they are coming to your site with a more obscure browser and/or a mobile device.
  • Accessibility. Want your site to be clear and understandable to those visitors using adaptive software, such as many of the blind and visually impaired use?  The first thing you have to do is learn CSS.  CSS gets a lot of those styling instructions off the individual pages (remember the “control panel” I mentioned earlier?) and out of the way for them.
  • HTML 4.01 is dead. It has been since 1999.  That’s right–CSS has been around for 10 years.  It’s time to move on.  If you’re still using old HTML tags to do your dirty work, you’re basically using zombie code.

Coming up next week in Part II:  What is CSS and a gentle introduction to using it

[Bloglines] [del.icio.us] [Digg] [Facebook] [Fark] [Furl] [Google] [MySpace] [Reddit] [StumbleUpon] [Technorati] [Twitter] [Windows Live] [Yahoo!] [Email] More »


read comments (0)