Skip to content

Technology Boost- Library Web Development

October 23, 2012

Hi all. I thought this was pretty interesting article in regards to web development for libraries. As we have learned, a website needs to be organized and precise. We learned a lot about CSS in class and I thought this article really touched on how important it is to have a website designed to be appeasing. It needs to be straight to the point and easy for the user to understand. This article goes into detail on specific features that a website should include to be user-friendly. It discusses the organization of the site as well as the CSS page. The CSS page needs to have certain characteristics to keep the page to look clean but also interesting. I think these articles are very helpful to those who plan to create a website or are thinking of fixing theirs.

Hope you enjoy the article.

Web development article

3 Comments leave one →
  1. jnetzloff permalink
    October 23, 2012 3:30 pm

    Thanks Danielle,

    The author made two really important points – page speed is everything. Think of how many web pages you have abandoned because they were too darned slow.

    The other critical point is mobile. A lot of companies are starting to design their mobile experience first – it requires you to simplify and really get to the meat of what your users need to do on the site. There is no room on mobile for cool but relatively useless features. By designing for mobile first, you have ruthlessly prioritized your features, and this simplification will help you build a better browser based experience.

    • blazekj permalink
      October 23, 2012 4:22 pm

      Page size and connection speed is something that’s been nagging at me over the past few weeks. I’m in the fortunate position of having pretty fast connections both at home and at work, and even on my phone with a reliable 4g connection. As a user, unless I’m really looking for it, I can’t tell much difference between a 100k page and a 5mb page. But as a developer, the idea of designing for mobile first is really helpful to me. Even if a really advanced and powerful phone can load a huge page quickly, the screen size limits the effectiveness of having tons of bells and whistles on any given page. You either require your users to do lots of scrolling or use a microscope to navigate your page. Even more than on a computer screen, less is more on a phone’s screen.

      As opposed to page speed, dead links and error pages are one of my biggest turnoffs as a web user. The point made in this article about the difference in user experience upon encountering different 404 error screens hit me pretty hard. In all, this article had a number of great examples of little things that developers can do to significantly improve the user experience of their sites.

      Great choice, Danielle!

  2. October 24, 2012 11:55 am

    Very practical article. I know that if I do have to see an error message or a dead link, I would prefer it be witty or interesting verses the boring “404”. Recently I was looking through the archive of a webcomic and there were several dead links, or pages where the image simply wasn’t there anymore. Instead, the image was replaced with a stock “Oh, looks like that hasn’t been fixed yet, check back later” notice. Problem was it was a comic from 6 years ago. Not exactly high priority.

    This article really talks about how important it is to really think about the experience of the users. That’s something that is especially germane to all of us right now in regards to our final project.

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: