Automation saves time, money and tedium. But overautomation destroys the things that differentiate libraries.
Interpreting what customers actually need from your website through methods such as top task analysis and card sorts is difficult work, but the results can be liberating. Coding your website is the (relatively) easy bit.
Do we need a complete list of links to every section of our website on every page? Or can we offer simple signposts to major pages and contextual links?
Users scan pages for text that might help them complete their task. Navigation bars and lists are rich in information scent, so it makes sense to avoid hiding them whenever possible.
How to generate page specific class names in a WordPress template, making it easy to extend your code and keep it DRY
Markdown is quick, easy and portable. If you're writing for websites, you really should learn it.
What we do and don't block on Suffolk library PCs. Our first instinct is to allow access to as much information as possible.
It's a bad idea to make web things look like other things when they're something else altogether. Instead, integrate services to make for better user experiences.
The web is a network of links; they’re what make plain, boring text hyper. Luckily, making a link is very, very easy, although crafting it properly takes a little thought.
The Almere library looks like somewhere anyone would like to spend a few hours. That's what all libraries should be like.
It's very easy to publish a PDF or image. Unfortunately, they're hard to read, especially on mobile screens. It's a far better idea to publish a menu in HTML, but persuading restaurant owners can be difficult.
I saw this idea in the comments on a post somewhere or other, and my immediate reaction was nope. Too technical, too using–something–that–it–wasn’t–intended–for.
Tabbed navigation looks a good idea, but it often causes confusion. Generally, it makes more sense to publish a single, visible, well-organised document.
Keep your website up to date, lean and organised.
Making your site responsive will get you more accessibility points than making it work in IE6.
Miserable and clunky search and discovery don't really cut it in the age of Google and Amazon.
Something to look out for when your work CMS has a forms module.
And your users don't distinguish between the two. Poor web skills and procurement processes result in poor user experience.
Audit your content in order to control and prune it.
Website and catalogue separation and search stuck in the mid-90s result in poor user experiences.
How to make Google docs display an em or en dash when you press the dash key twice.
Concision, chunking and emphasis will make your web writing more effective.