Showing posts: 136-150 of 313 total posts
Peter J. Bogaards takes the bold step and launches BogieLand (BogieLand in Dutch), which is an information design and information architecture firm. This is a bold and yet wonderful move for Peter, we wish him well and know he will do wonderfully.
Peter has been the person behind my first outward click of the day, InfoDesign an ID, IA, Usability, UX, and UCD aggregation site.
Information Architecture for location based services is a summary from Smart Mobs of Solving Mobile Challenges with Psychology-driven IA in Boxes in Arrows
Inside the PARC: the 'information architects'. This is part of the Stanford Silicon Valley Archives.
Following a current trend of public redesign process by designers, Kevin Fox puts his laundry out to air. I did part of my redesign in public, but not to the extent Kevin is doing (or Zeldman or Joshua Kaufman has been doing). Even post redesign overviews and commontaries are helpful.
Kevin is showing the steps many of us go through as a professionals. His analysis of audience usage patterns and wireframes are very helpful first steps that will frame the decisions made down the road. Many of us consider these the most important steps, but many more important steps will follow.
Maybe I should post the wireframes for this redesign. I think I ended up straying from the wireframes a bit as the header came to life one night and changed many things.
I recently restumbled across Keith Instone's Navigation Stress Test. This will help greatly when trying to sort out browsing structure issues when thinking through how well the user from the whole in the eaves. This is a quick mental jog to ensure the user can find what they are looking for, which will help the site owner's whuffie
Jeff Lash has posted an on target article at Digital Web, How did you get here? Designing for visitors who don't enter through the home page. This has been issue for to encourage clients to look in their access logs. Most often 40 to 70 percent of a whole site's traffic has their entry point to the site at some other point than the front page. Many clients only think that people enter their site through a home page. The early Web years placed an insane amount of focus on the home page.
I have talked to Jeff about this a while back and he had the same experience with clients and in-house sponsors. Part of the change is eternal search has become much better. Many users head to Google to find what they are seeking rather than going to endpoint.com and clicking from their home page.
This focus shift requires sites to have browsing structures for their users. Test with outside users who are not familiar to the site by starting them in the middle. Check heuristics for each section and page. Does the user know where they are? Can the user find other related information?
Jeff nails this topic, which has more room to grow. Go read.
Ginny Redish and Mary Frances Theofanos have written Observing Users Who Listen to Web Sites article for the STC Usability SIG Newsletter. This article is a great insight into how blind and partially sited individuals interact with Web Sites that are being read to them by devices. This is a must read article.
This article helps developers understand how auditory reader users consume information. There are many similarities to users how use their eyes, but some of the devices we commonly use to assist auditory readers, like skip navigation, are not used as many developers think. The accessibility assistive technologies are still needed and still requested, as thie article points out. This article provides a great insight for those people who do not have a sight challenged user to learn from and to test their products with. Those who do not actually test their work or have never seen their work tested can only guess what is going on. This article helps developers get insight that helps us develop for accessibility from step one, which is where we must be thinking of accessibility.
There have been some more modifications here at vanderwal.net. Many of the pages now have links to the Essays section. The Essays page has finally been brought into the new look and layout. The page also integrates the Model of Attraction section more closely.
Over the past few months the MoA has grown through word of mouth and remembering the URL for its mainpage has been problematic. Much of the traffic that has been coming into MoA has been going to the first draft, which is good, but it is also just the first draft. The newest information on the MoA, there is more coming, will be placed at the top of the list.
The Creative Commons license has been added to more pages, including the MoA. Finally the links page has been updated to add some of my regular reads, remove dead links or stale content, and update links to where helpful resources have moved.
There are some more modifications on the way in the near future, some you will be able to see and others will be admin tools or just seemless updates.
This is post 1,001 in my homebuilt weblog CMS. Yes there have been other odometer parties on this site, but turning over 1,000 was one that really has pleased me. My tool is missing some elements that others now have, but I still have fun tinkering with mine and extending it. There are some plans for the summer to add functionality by embracing the categories and using them in conjuction with the links page as well as tying the links and entries together, sort of like a Web strawberry banana shake. I have a book review repository planned too, but it has not moved out of the ERD phase yet (uh, yes I plan, chart, and document my apps and changes for the site, it eases making changes in the future -- I just need to get all the docs on one machine and in one directory).
Lift you glass to 1,001 entries and no digi-barfing
Jeffrey Veen has a collection of IA Jargon collected from within large client walls. My favorite is "Boil the Ocean"
Indi Young provides a great guide for building browsing structures in her article Site Navigation: Keeping It Under Control.
A February 2001 article by Dennis Jerz discusses Blurbs: Writing Previews of Web Pages, which is very helpful information that helps annotate links to ease and assist the users understanding what is behind "door number 2". The blurbs help the user by providing more than the short snippet in a link. This makes the browsing structures much more friendly.
There are some essentials to building Web pages that get found with external search engines. Understanding the tags in HTML and how they are (rather should be) used is important. The main tags for most popular search engines are the title, heading (h1, h2, etc), paragraph (p), and anchor (a). Different search engines have given some weight in their ranking to metatags, but most do not use them or have decreased their value.
Google gives a lot of weight to the title tag, which is often what shows in the link Google gives its user to click for the entry. In the title tag the wording is important too, as the most specific information should be toward the front. A user searching for news may find a weblog toward the top of the search ahead of CNN, as CNN puts its name ahead of the title of the article. A title should echo the contents of the page as that will help the ranking of the pages, titles that are not repeated can get flagged for removal from search engines.
The headings help echo what is in the title and provide breaking points in the document. Headings not only help the user scan the page easily, but also are used by search engines to ensure the page is what it states it is. The echoing of terms are used to move an entry to the top of the rankings as the mechanical search engines get reinforcement that the information is on target for what its users may be seeking.
The paragraph tags also are used to help reinforce the text within them.
The anchor tags are used for links and this is what the search engines use to scrape and find other Web pages. The text used for the links is used by the search engines to weight their rankings also. If you want users to find information deep in your site put a short clear description between the anchor tags. The W3C standards include the ability to use a title attribute which some search tools also use. The title attribute is also used by some site readers (used by those with visual difficulties and those who want their information read aloud to them, because they may be driving or have their hands otherwise occupied) to replace the information between the anchor tags or to augment that information.
The application I built to manage this weblog section is build to use each of these elements. This often results in high rankings in Google (and relatedly Yahoo), but this is not the intent, I am just a like fussy in that area. It gets to be very odd when my posting weblog posting review of a meal at Ten Penh is at the top or near the top of a Google Ten Penh search. The link for the Ten Penh restaurant is near the bottom of the first page.
Why is the restaurant not the top link? There are a few possible reasons. The restaurant page has its name at "tenpenh" in the title tag, which is very odd or sloppy. The page does not contain a heading tag nor a paragraph tag as the site is built with Flash. The semantic structure in Flash, for those search engines that scrape Flash. Equally the internal page links are not read by a search engine as they are in Flash also. A norm for many sites is having the logo of the site in the upper left corner clickable to the home page of the site, which with the use of the alt attribute in a image tag within an anchor link allow for each page to add value to the home page rant (if the alt attritute would have "Ten Penh Home" for example).
Not only does Flash hinder the scapeing of information the use of JavaScript links wipes out those as means to increase search rankings. Pages with dynamic links that are often believed to ease browsing (which may or may not prove the case depending on the site's users and the site goals in actual user testing) hurt the information in the site for being found by external search engines. JavaScript is not scrapable for links or text written out by JavaScript.
Ftrain's accordian time I found to be enjoyable. I enjoy time theories and find this to be close to my own personal favorite as accordian time accounts for the percieved difference in time. Some folks have a, so called, strong inner clock that is in step with metered time.
Chronological time is problematic for many as their lives feel wholly out of step with the beating minutes regulated to 60 seconds. Time seems to move in spurts and is quasi-random. My personal time theory to account for the difference in perceived time is that everybody is on a different time pace and some folks do have time moving faster for them, while others have time moving far more slowly. These differences are synched at night so that we all can work and play together. This is just an unsubstantiated theory on my part, but I am happy to find others thinking of other time measurements that can account for perceived differences in time.
Alan Lightman has a collection of time scenarios in his Einstein's Dreams. I found ED a wonderful quick read that added a wonderful collection of time theories to my existing stack. It has been a few years since I read ED, but it seems about right to pull it off the shelf and have another go.
Time, or perceived time, is important to understand when developing applications and information structures. Different individuals will become frustrated if they can not find the information they seek when they desire that information. This is partially dependant on the persons perception of the passage of time or their relation to metered time. A person who normally has time passing slowly may find most information is easily found, but if they are trying to trackdown the address for a date or interview in a relatively short time before the event the persons perception of time may increase. This impacts the perceived ease of finding information or re-retrieving that information. The frustration for this person may increase as they can feel the minutes or seconds slipping away. This cognative element is helpful to understand as we test and build interfaces.
I must mention Boxes and Arrows is up for a Webbie Award. Congrats to all the other alumni staff who helped get this wonderful resource off the ground and to the current staff that keep this great gift running and being so wonderful. Most of all to Christina Wodtke for having this crazy idea.