website management

Blogging Process for Topeka

by David Lee King on June 28, 2011

Today, I met with some library staff where I work and talked about starting up another blog on my library’s website (look for a sports-related blog soon!). That reminded me that I said I’d write a post about our blogging process at tscpl.org … so here’s that post!

Our blogs are generally team-based, and are connected in some way to our collection or services:

Content Connections: For example, our Travel blog is connected to our Travel Neighborhood in the library (we have been pulling our collection out of traditional Dewey order, and are grouping them by topic – so for example, now all our travel books are grouped in one handy place, and labeled Travel). Our Art blog is connected to the art gallery in the library.

Team-Based: we generally have a team leader and 1-3 other staff who are team members. The team leader makes sure blog content matches the goals for the blog; makes sure content is actually getting posted; writes content; and can edit content as needed. Team members help write the blog posts, and do whatever else is needed for that blog.

When we create a new blog, our web team meets with the blog team (can you tell we like teams?), and we create some short-term goals and next-steps, including:

  • What’s the topic? Is it connected to the library’s collection?
  • Who’s the team leader? Who are the team members?
  • How often will you post? We have a posting schedule for our blogs. For example, the Travel blog has a new post every other Wednesday. We have a Google Calendar that serves as our content calendar.
  • During the meeting, we talk about content – mainly me talking about how every post needs to relate back to the library. Each post should focus in some way on our staff, our stuff, and our community – and it should always point back to the library.
  • They’re also reminded that photographs and videos are cool, too – as long as they relate back to the topic.
  • We ask the blog team to create a list of 25 things our customers should know about that neighborhood or collection, and use that list as ideas for the blog’s first 25 blog posts. This helps our bloggers (some of who are new at writing scheduled posts) some blog posting ideas.
  • I also ask each blog team to develop a persona or two to target with posts. We’re big on analytics and market segmentation data here, so generally we’re using a couple of target audiences that relate back to the library’s strategic plan.

That’s pretty much it. We have approximately 18 blogs on our public website right now, and are growing more as we need them.

image by Maria Reyes McDavis

1 comment

Check out builtwith.com

by David Lee King on June 23, 2011

Mark this down as a cool tool for your website-building toolkit…

Ever wondered what CMS or web server a certain website was using? Wonder no more! Simply enter the URL of that interesting site into builtwith.com and voila! – this site will tell you all that geeky stuff!

For example, look at their CMS page. For the top million websites that BuiltWith tracks, they find that 62.87% of websites use WordPress, 14.77% use DotNetNuke, 10.25% use Joomla, and 3.40% use Drupal. Then when you move to their Top 10,000 sites graph, those percentages change quite a bit.

Or look at the Top Payment Distribution Services – look at the top 10,000 sites graph. % us Paypal (duh), 35.94% use CCBill, 10.94% use Google Checkout, then Flattr, Mollie, and Amazon Payment Services are there, too. CCBill, Flattr, and Mollie? Never heard of them.

So – use it to check out your website against others, use it as a discovery tool to learn about new services. Pretty handy!

Swiss Army knife by AJC1

3 comments

If you’re interested in building better websites, make sure to sign up for my upcoming webinar for ALA TechSource on June 8 – Building the Digital Branch: Designing Effective Library Websites. Just click the link to sign up!

This will be the second time I have given this webinar. If you attended the first one, never fret! There will be new content – I’m going to talk about how Topeka & Shawnee County Public Library (where I work) built our current website (the redesign went live on March 1).

Here’s the blurb for the webinar:

Every library needs a presence on the web. Whether you work at a large academic library or a public library in a small town, you need to be able to deliver service and content to patrons outside  your building. David Lee King will once again present this popular workshop, taking you through the process of building an effective, user-friendly library website that will expand and enhance your library’s presence in the community.

In this workshop, you’ll learn:

  • How to successfully plan and implement a redesign of your website
  • How to find out what patrons want from your website
  • How to use your website to interact with patrons
  • How to create strategic plans and goals for your website

Sign up NOW!

4 comments

How We Post in Topeka

by David Lee King on September 7, 2010

I was recently asked how my library posts so frequently on our blogs. It’s a morphing process – here’s where we are now, and where we’re [probably] going.

Right now, here’s what we’re doing. Our digital branch is a huge priority for our library. We’re one big building and 17 bookmobile stops, and we have to reach a whole county. So we have prioritized reaching out digitally. In fact, our executive director often says “no one can opt out of the digital branch.” It’s that important to us.

How does everyone participate? Some blog, some take pictures or create/post videos. Some of us watch/add content to our outposts like Facebook or Twitter. Others answer texts/IMs/email reference questions.

For blog posting – right now, our guideline is two posts a week per blog/section of the site. Do we always make this? Nope – some areas do, some not so much. It’s a work in progress.

It also factors into our annual job performance reviews (more on this in a bit).

How will this be changing? Right now, we’re in the midst of a pretty major website redesign. We learned lots from our current design and the current way we operate on the back end, and are ready to put some improvements in place.

One improvement will be how we handle web content – here’s our thinking right now. We’ll probably align our blogs more closely with our physical library’s neighborhoods – we’re taking stuff out of Dewey Decimal order and putting them into content areas (i.e., all health-related books go in the Health neighborhood, etc).

Each of those neighborhoods has a team and a team leader … and each has a blog, too. So the blog is that team’s responsibility. We’ll figure out a posting schedule for them, and jointly create some goals/strategy for growing their little section of the digital branch (that’s a part of my job).

We’ll also probably figure out a way to more formally reward those teams for the digital branch work they do. Right now, it’s easy to say “no one can opt out” and “it’s part of our job performance” – but there’s no good, formal way to make that happen.

We’ll need to figure out a better way to say stuff like “yes, Joe wrote  24 posts this year, answered 200 text reference questions, and livestreamed an author event.” And have that somehow count for better scores on an annual review (alright – still need to talk to HR and other managers about this – it’s been mentioned that we need to improve in this area, just not exactly how yet).

The goal isn’t to punish people who don’t do the work (cause most of us already do it) – instead, the goal is to better recognize this great work.

And last – remember, I work in a pretty healthy organization. If our library decides to do something … we do it. If someone’s assigned to do something, that thing happens. Isn’t that how all libraries are [David quickly ducks]?

pic by pallotron

7 comments

Digital Branch Style Guide

by David Lee King on February 10, 2009

Thought someone might find this useful – it’s the styleguide we use for my library’s digital branch! It’s a long document, broken up into these sections:

  • General Guidelines for Blog Posts
  • Citing/Attribution
  • Featured Section
  • Comments – What to do with them
  • Creating a “Voice”
  • How Can I Get a Conversation Started?
  • I have a suggestion/problem. What do I do with it?
  • Staff Responsibilities

******************

Digital Branch Style Guide

Please follow these guidelines when writing blog posts on our public website. This document is a start – I hope to add to it as needed. Notice something glaringly obvious that I haven’t listed? Email it to me.

General Guidelines for Blog Posts

Post frequency/length:

  • Frequency:
    • 2 posts per week for each Subject Guide
    • Posts in the Services section – as needed
  • Length:
    • sufficient to cover topic
    • shorter is always better – just enough to cover the content

Formatting:

  • one space between sentences – not two!
  • avoid ALL CAPS
  • use a spell checker
  • break post into small paragraphs rather than one large chunk of text

Post titles:

  • keep them short, snappy, and descriptive
  • capitalize every word except prepositions (like a book title)

Internal Post Structure:

  • Bulleted lists are great
  • Subheads are great – helps people quickly scan content
  • Images that complement article tend to attract readers

specific words – Be consistent with these terms:

  • email (all one word, all lowercase)
  • website (all one word, all lowercase)
  • webpage (all one word, all lowercase)
  • web (lowercase)
  • Internet (uppercase “I”)
  • Our library – first reference is “Topeka & Shawnee County Public Library.” Second reference is “the library.”
  • Our website is “the Digital Branch.”
  • Refer to our Neighborhoods by their full title (i.e., the Travel neighborhood, the Health Information neighborhood)

Summary of post

  • Each post should have a summary – there are two ways to do this:
    • Create a summary paragraph in the summary box
    • Leave the summary blank – the beginning of the post will automatically be used as the summary

Tags:

  • Use 2-3 descriptive tags for each post
  • Tags are usually keywords that are descriptive of the content of a post
  • These should be different from a category. Ex – a post could be in the Books Subject Guide with a Category of Sci-Fi, and have tags like Steampunk, Robots, and Mars.

Links:

  • For book titles
    • make the book title the link text
    • don’t include the URL with the book title
      • Do this: The Hobbit (where “The Hobbit” is the text used for the link)
      • Don’t do this: The Hobbit – http://catalog.tscpl.org/asdfhasdf/etc.htm (where “The Hobbit” is NOT the link text, but the URL is also used as the link text)
  • Other links
    • When linking to webpages or blog posts, make the webpage title or the blog article title the link text
    • Refer to the link within a sentence, like this: “Topeka has a great library that everyone should visit.” (“great library” would be the link text used for our library’s URL)
    • Another example: don’t write “you can read the full report here” – using words like “here” or “click here” is generally bad practice. Instead, say “the charity released a report, which said…” (“a report” is the link text, and is incorporated within the sentence). This type of internal link reads better.

Citing / Attribution

It’s important to give proper attribution to sources, even online. Here’s how to do it:

  • Blog posts, newspaper articles, other websites
    • See the Links section above for linking
    • When you quote someone else’s text, make sure to link to the original source.
    • With the link to the original source, reference the site. For example, say “Here’s a lovely article on the Topeka Ave. bridge project (from the Topeka Capital Journal).” “Lovely article” links to the specific article, and “Topeka Capital Journal” links to the newspaper’s main site.
  • Images
    • If using an image from flickr, photobucket, or some other photo sharing service, include some type of attribution/pointer back to the original photo at the end of the article (i.e., “photo courtesy of JimBob” – “JimBob” would link back to the original photo).
    • Use photos with a Creative Commons license when possible
  • Videos
    • Include some type of link/attribution/pointer back to the original video (i.e., link back to the YouTube video if you use a video from YouTube)
  • How much of a quote can I do?
    • The U.S. Copyright Office FAQ on fair use (http://www.copyright.gov/help/faq/faq-fairuse.html) says this: “it is permissible to use limited portions of a work including quotes, for purposes such as commentary, criticism, news reporting, and scholarly reports. There are no legal rules permitting the use of a specific number of words, a certain number of musical notes, or percentage of a work.”
    • Don’t quote the whole thing!

Featured Section

The Featured Section is structured this way:

The first Feature Box is called Featured.

  • It features big programs, events and special features of the library.
  • Populated by PR and Event Resources

Guidelines for the other Feature Boxes:

  • The other feature boxes include Books, Research, Movies & Music, Gallery, Kids, and Teens.
  • These sections usually focus on content (Gallery, Kids and Teens boxes can post about a program)
  • Handouts, booklists, links should be part of that post. No programs with registration and limits should be posted there.

Comments – what to do with them?

  • respond
    • thank them for their comment
    • add something if possible – point to another similar book, a link on our site, etc.
    • if it’s a question, answer it
    • if it’s a criticism, answer it – or refer it to someone who Can respond appropriately
    • If the comment is negative, don’t repeat it! Respond without repeating the negative question/comment.
  • In general, don’t edit the comment. Usually, it’s better to correct in another comment. Only edit if the comment:
    • Has “bad” words (that our automatic naughty word filter didn’t catch)
    • Is derogatory
    • Has an unrelated link
  • delete if spam. For example: “I have checked that really there was great information regarding that. There was another also – http://healthbeautyproduct.blogspot.com/” is a spam comment. Usually, spam comments include this type of stuff:
    • poor grammar (sounds like they don’t really know the language)
    • PLUS links to unrelated websites
  • What to do if you don’t know what to do – ask the web team to read the comment.

Creating a “Voice”

  • Write in a conversational tone:
    • goal is to start conversations
    • if you wouldn’t say it in conversation, don’t write it
    • write “friendly” – just like we are at the desk!
  • Use active voice. Example – don’t write “The tree was struck by lightning.” Instead, write “Lightning struck the tree.”
  • Use inverted pyramid writing style (explanation at Wikipedia: http://en.wikipedia.org/wiki/Inverted_pyramid)
  • The first couple of sentences of your post displays as the summary, and appears in various places on our site as teasers to the whole article – so make it snappy!
  • Write in present tense when possible. Ex:
    • Don’t write “the book signing will be held next Tuesday”
    • Instead, write “the book signing is next Tuesday”

How Can I Get a Conversation Started?

Here are a couple of ideas on getting conversations started on your blog.

  • Write great content (always top priority)
  • Take part in the conversation:
    • read blogs and Topeka-area newspapers that allow comments
    • read blogs in your area of expertise
    • leave comments on those blogs, linking to your post in the comment
    • also link to those blogs in your post
  • Focus your posts on goals:
    • Before you write, answer this – “what do you want the reader to do?”
    • Provide a call to action (ie., tell them what you want them to do)
    • Ask for a response
    • Point them to things (like books in our catalog)

I have a suggestion/problem. What do I do with it?

Problems:

  • email the web team
  • tell us what’s wrong
  • include links or descriptive text if possible

Ideas for the site:

  • Email the web team/Digital Branch Manager:
    • Include description of idea
    • Digital Branch Manager will set up meeting if needed, share idea with web team and/or Managers, etc
    • Remember – all ideas are great, but not all ideas will be implemented on the site
  • hold regular meetings
    • i.e.., fun in Topeka blog meeting
    • discuss ideas
    • make suggestions to the web team

Staff Responsibilities

Blog moderator

  • make sure there are 2 posts per week
  • encourage writers
  • check in with Digital Branch Manager periodically
  • schedule regular meetings of content area
  • all the blog author stuff

Blog authors

  • write posts
  • check links
  • respond to comments
  • delete spam
  • periodically touch base with blog moderator

Digital Branch Manager

  • big picture development of branch
    • strategic planning
    • trend watching
  • talking to internal groups
  • talking to external groups
  • mentoring digital branch staff
  • developing new content areas and unique services and tools

Web Team

  • Webmaster/designer and Web Developer
  • designs new pages
  • keeps design fresh
  • day to day operations
  • maintenance and upgrades
  • builds new stuff

40 comments