A good list of common naming conventions:

http://www.irritatedvowel.com/Programming/Standards.aspx

I like the ux prefix idea for as control types do often change and renaming is a pain.

A nice JQuery/CSS based implementation of the OS X Dock.

http://www.ndesign-studio.com/blog/design/css-dock-menu/

I’m not convinced with how it fails completely when javascript is turned off, but it’s a good start.

UPDATE: Looks like it originated here: http://interface.eyecon.ro/demos and uses http://www.jquery.com/

This is a good analytics read:

Excellent Analytics Tip #11: Measure Effectiveness Of Your Web Pages | Occam’s Razor by Avinash Kaushik

The bounce rate information is particularly worrying…

I have been thinking about how to best communicate information on a (specifically, company’s) website, and how to use content most effectively.

Take a company’s homepage for example; I’m a potential customer, I’m running through a page of google results and I’m likely to bounce straight off the website after 7 seconds (note-to-self: find the report where I read this) if I can’t see what I’m looking for – I’ve hit your homepage and I need to know immediately that I’m looking at something relevant.

The main questions in my mind are:

• WHO is this company.
• WHAT do they do.
• WHERE are they based.

The answers to these core questions should be sort and sweet, and should then invite the user to explore and learn more. WHO would logically link off to an ‘about us’ page, WHAT would link to whatever they company is trying to flog, and WHERE would link to a ‘contact us’ section. Obviously this set of questions can be extended to include others, but these core three should be clearly answered on all of the website’s main entry paths, if not to some extent on every page. Do users always enter the site via the homepage?

Similarly, this ‘three questions’ rule can be applied to a product the company might be offering:

• WHAT is the product.
• WHY do I need it.
• HOW much is it.

Again, these questions should be mind-numbingly obvious and immediately answerable to prevent users fatigue levels rising.

An example of this can be seen on twitter.com where they use what, why and how on their homepage to get the message across.

I’m not sure this is strictly the rule of three, but using this similar idea should improve copy and visit lengths by getting to the point, keep users interested and eliminating the all-too-common problem of copywaffle.

Another good bit of MVC info from the ALT.NET conference:

http://download.microsoft.com/download/f/0/8/f0830f07-44db-4eea-ace3-8865856c8d65/ScottGuOnMVCatALTNET.wmv

Not the best quality but some great content.