Archive for the ‘interface’ Category

Another year gone by

Thursday, April 10th, 2008

A few days ago this blog celebrated its second birthday. It’s been a good year, with links to my article published by such notable authors as Luke Wroblewski and Ethan Marcotte – the same article was translated into Russian. The blog was also included in Planet Microformats.

I’ve written only 61 posts (down from 100 in the first year), gotten 134 comments (down from 155 in the first year) and more than 70.000 spam comments (up from 17.000). I have 56 subscribers according to FeedBurner, which is more than a 100% increase from 25 a year before.

Firefox is the dominant browser with 47%, Internet Explorer lost some market share and is down to 44% with Safari rising to 4% and Opera to 2.5%. Almost 90% of the visitors have Flash 9 installed, an additional 4.5% are stuck at Flash 8. Screens grew a bit with only 27% having 1024×768 or less (32% year before) and less than 2% 800×600 or less. Windows have a share of 85%, Mac OS 10%, Linux 4%.

Top content is still This page contains both secure and nonsecure items, Messing up the interface coming in at a distant second with merely a third of the visits.

Redesign

I’ve had a redesign planned since day 1, but as usual it took quite some time to get here. Since I’m not a design I couldn’t just create a fancy look with everything else left the same. The idea was to shake everything up and try to come out with a layout that would be worth redoing everything. When I posted about what a TV network / news page should have when being redone I was also setting my own targets.

Tableless layout

This goes without saying. All the pages should validate, although there might be some crap left.

Width

I increased the width to 850px with the addition of 140px to the left used only for design purpose, not content. The main content is only 410px wide which means you can easily read this blog on devices like the Nokia n800.

YSlow

Not really that relevant since the page only creates about 15 requests which might even decrease as I compact the JavaScript. There are a bunch of other requests made that are content related – images, Zemanta pixies, favicons…

Microformats

Every page is supposed to be valid hAtom and the About section is an hCard with adr and geo. Links to others are of course XFNed. The about page is planned to be an hResume.

There’s no need to talk about blog compatibility and screensaving for banners. I don’t use OpenID there are no log-ins.

Context sensitive

Markos recently pointed out the fact that not many pages on the internet make use of the possibility to change the page for different users and different context. This, of course, is not an easy job, especially if you’re doing heavy processing – doing this for each user might be a bit to heavy. It is something I think differentiates the internet from other media and should be used to provide a better user experience.

User based

Returning visitors of this page will get special treatment. Since they’re coming back they don’t need to see the About section and they will also not have banners displayed.

Referrer based

People coming from search engines will see their query parsed into words that will be colored for easier findability. They will be able to switch them on and off and be able to repeat the same query on the internal search with the last option available only if the referrer was an external search engine.

Location based

Even though many blog themes have the same sidebar for all the pages (as did the previous one I used) this doesn’t follow the normal architecture rules. The sidebar is normally context specific – in my case a regular user reading a blog post will currently see nothing in it (while others will see the About and the Ads.

Other candy

Grid and baseline

The page is set to a 7 unit grid, with units 60px wide with a 10px gutter in between. It’s also set to a baseline height of 18px that is respected throughout the page. Images and other non-text blocks on the page are corrected with JavaScript to a half of the unit (9px).

Links

The links bar will try to retrieve the favicon of the link – if it succeeds it will use it instead of the default icon.

Maps

If you click on the Google Maps link in the About section they will open as small inline maps with a link to open them in a new window.

Yet to be done

You might have noticed that post categories are nowhere to be found. I didn’t forget them I just found out that I’ve changed my categorizing pattern and had to rethink the display. I also wanted to add the Elsewhere section with links to or even content from other pages where pieces of me reside (Twitter, Flickr, Marela, Pownce, Facebook, LinkedIn, del.icio.us,…). Another thing missing is the Projects and Experiments sections, I’ll tackle these in a separate post sometime in the future…

Zemified

Relaunching…

Friday, March 28th, 2008

the webSource: ShutterstockA big Slovenian media house is announcing a relaunch of the biggest Slovenian web page (according to Alexa). Since they own two TV channels they’re advertising it with a short commercial that shows a glimpse of the new design. Another hint is a very very small, almost unreadable banner on their front page which “reads e-volution / evolution continues / next stage in [4] days”. What I want to know is whether it is to be an evolution in technology. That’s why I’ll list a few things I’d want if I was the client:

Semantic use of HTML (tableless layout)

The current page sports a fat table layout. The time of lame browsers and the need to create such a layout has passed and using semantic HTML for all the elements is the standard now. As a fan of XHTML Strict I’d also opt for that, allowing users to use the page as a source of content.

Width

The current page is 800px wide with a skyscraper banner on the right. I think a wider default with a hint of elasticity (that would make it almost or completely useful on smaller screens) would be a great choice. If elastic is too difficult I’d opt for 960px.

YSlow

The current homepage needs more than 180 request and more than 700kB to download. It takes about 5 seconds to do all this. I’m sure that with a little smarter use of CSS and image sprites these numbers could be much lower. A smart thing would be to move the static content to static.24ur.com so the browser could download all the resources faster. I’d also want the styles to be on the top and the scrips on the bottom. And since they use their own system to deploy banners I would expect them to use WEDJE to deploy them without stopping the site.

Microformats

Since all the content on a certain page is actually a news feed I would want them to use the hAtom microformat, with hCard for people and hCalendar for events and the TV schedule also possible. There’s no need to use propriatary format in the age of interoperability.

Blogs compatibility

I don’t think they should offer blogs, but it would be nice if they had a way to embed their content into blogs commenting on the current events. It would also be great if news posts would allow trackbacks so other people could see who blogged about the news.

Screen saver

I’ve noticed lately that when they have a few heavy banners that it’s important to close the tab the page is in to get the full power out of my computer. This could easily be solved with a screen saver JavaScript that would hide all the banners when a user doesn’t interact with it for some time.

OpenID

With OpenID providers around every corner I really don’t see why anybody would want me to register on their page anymore.

Can you think of anything else?

Zemified

Zemanta is live!

Thursday, March 27th, 2008

Zemanta, a Slovenian start-up that got into seedcamp, moved to London for a few months and came back a few months ago launched their service at Spletne urice yesterday. The service that bares the name of the company helps you enrich the blog posts you’re writing. What you need to do is download their browser extension (only Firefox currently supported) and a box will appear in your favorite blogging tool (WordPress, Blogger, Typepad currently supported) that makes adding relevant images, links and related articles to the post a one-click operation.

I like the technology and I think it will make the life of an ordinary blogger a whole lot easier. What I don’t like that much is the HTML they produce in the blogposts. I understand the dilemmas they have with all the themes and platforms they need to support but adding that much style attributes is really not nice.

Disclaimer: I’ve cleaned up the HTML in this post, to see the output check the demo.

Zemified

Content patterns

Saturday, February 9th, 2008

When laying out a website everybody has a few building blocks that they keep using over and over. The more layouts you make, the more refined these blocks are. And the better. I’m not talking about creating the HTML but rather the IA (information architecture) phase of the creation process when you’re creating wireframes with boxes that represent content.

I recently read an article on design paradigms for lots of data which made me think about what I commonly use when laying out pages. I’ll call this the one-few-many content pattern.

The main premise is that content on a website is presented in one of three basic forms – “one”, “few” and “many”. Let’s see what all these are and how they work together.

One

This one is the most obvious and consists of displaying a single entry. When you do this you will most probably want all the data a certain entry (asset) contains. You will use this block for a single news item, blog post, product page or anything similar.

  • CNN sample
  • Yahoo! sample
  • BestBuy sample
  • NY Times sample

To lay out the single content you will first need to decide on the importance of content parts, then set the layout. You will need to think about what content you’ll always have and what you might not. A common case of this are images that can change the form factor and might not even be present sometimes. When you know what you’re working with you’ll want to set priorities and based on that the size and shape of the parts. You should know that users can only focus on a few things – if everything is important and exposed essentially nothing is. The common solution in the cases is to put the image title on the top left, add meta data (author, date and similar) just below it. A single image is positioned on the top left with content flowing around it. A nice touch to this layout is to have the image a few lines below the top.

Few

A little less obvious that the previous one. This is usually a list, that is not a true list, but a short tasting of what’s there. You might think of this as “last 5 news” or lists on the front page that only list a few items. To display these you will not need as much data as you would for “one” but you need something. For a news and blog posts you’ll need at least the abstract, products will need the image, prices, discounts,…

  • CNN sample
  • Yahoo! sample
  • BestBuy sample
  • NY Times sample

You will see this block in many different shapes. You might see a thumbnail image with a title and an abstract in online stores you will see more data. In some cases it nowadays replaces the many block. A big part of this is that searching is very popular (no more lists) and using this block gives more information than using a simple many block.

Many

The last one of the bunch is pretty obvious but it might be hard to tell the difference between the last two. This is a list that is primarily used to list content when you have a lot of content and you do not want a user to browse through 10+ pages of paginated content or scroll 30 screens down to find something. You usually need less content, a title will usually do the trick, sometimes you need the date, products definitely need the price.

  • CNN sample
  • Yahoo! sample
  • BestBuy sample
  • NY Times sample

Using this is very easy and utterly unpopular. Displaying data only as a list is not very user friendly since it requires reading – something people rarely do on the web. This is why the many block often disappears in favor of the few block. A common place to find it is in the search results or the archive page.

To demonstrate the use let’s think about a simple corporate web page. On the first page you’ll most probably want to show a set of products using the few block, some news, again using a few block. Most of the content on the page will be using the one block since you’ll only have single articles describing what the company does. The news portion of the site might use the few block on the landing page, the many block for the archive and of course the one block to display a single news post. Displaying the products will be a bit different – the landing page might use the few block to display exposed, new or discounted products. The category listings will use the many block which will include an image with the title and some products specs or a short description. Again you’ll be using the one block to display a single product.

This doesn’t solve all the problems when laying out the page. It helps me define the main blocks and the content that’s used to display them on the page. It also makes some of the choices easier and helps the designers envision what the final, more detailed wire-frame might look like early on in the process.

YouTube related videos

Saturday, December 22nd, 2007

I see that this isn’t news anymore but I was amazed when I saw it. It needs a few more refinements though.

YouTube related videos vizualization