Posterous theme by Cory Watilo

Summer holiday reading for web geeks...well, web project managers anyway

So, its that time of year again to head off to a beach with wifi to **go on holiday**. If Atonement doesn’t seem like your sort of thing, let me share what is on my list for this year:

Reviews back as and when I get through them.

Writing content the Google way...writing for the web 2.0

While browsing a few bits on Google Analytics, I came across these two:

Five Tips for Writing Effective Web Headlines

http://www.google.com/support/conversionuniversity/bin/answer.py?answer=77157&hl=en

and

Five Objectives of Website Copy

http://www.google.com/support/conversionuniversity/bin/answer.py?answer=77130&ctx=sibling

both of which have some good basic information and provide more than a few hints about how to get your copy formatted to get great Google flavour in search listings.

Free HTML e-mail templates from Campaign Monitor

are here :

http://www.campaignmonitor.com/templates/

and you don’t even need to worry about testing them with Outlook 2007! For anyone new to the world of sending out HTML mails, it would be worth downloading a few of these ones and then picking them apart to see how they work. Its really the use or lack of CSS and the way of handling and styling the HTML that is key.

Oh and do make sure you have a nice plain text version too…even Mailchimp now has an automatic-text-o-tron:

http://www.mailchimp.com/blog/automatic-plain-text-email-generator/

UPDATE 12:20pm

Blimey, its all go on the mail front today…here is a converter that makes all your lovely CSS inline…

http://code.dunae.ca/premailer.web/

UPDATE 12:36pm

and I should probably mention the email newsletter archive as well:

http://www.newsletterarchive.org/

which is a great online store of past newsletters, to give you inspiration and ideas for your own work.

UPDATE 16:08

Pleaaaaaase, just stop it with the e-mail stuff, really…here’s how to e-mail the future:

http://www.clickz.com/showPage.html?page=3630542

Here we go again with CSS Flash image replacement...or do we?

Most people have probably heard of SiFR, Shaun Inman’s lovely technique of embedding Flash in a site to replace the fonts. But now we have Facelift or FLIR stepping up to the table.

Facelift Image Replacement | About FLIR Image Replacement

Apart from the techy side (whether its better than any other technique which needs a bit more testing yet I think…), its a good example of how to make a up a product site.

Despite the fact that its free at the moment, its obviously been put together by somebody that know what a customer (paying or non-paying) would like, and a web customer at that.

So, we have a nice examples page which is interactive and shows what can be done.

An easy quick start page means coders or designers could easily get cracking.

A documentation page, which can be added to by users, is invaluable to show all the various options.

A forum allows people to post on great examples of how they have used your product, as well as request any help they may need. This could either be answered by Mawhorter or other users themselves.

Last of all, a blog allows the site owner Mawhorter to post occasional updates as to what is going on.

Total score? About 4.5 out of 5.

What’s he missing? Well, the blog does have a feed but there is no way to easily subscribe to its updates other than follow the RSS and there is no e-mail newsletter. The RSS is only actually in the blog when it could be easily put in the header of every page, then more and more people could subscribe to it.

Launching a site into beta...the web 2.0 way!

Howdy all…does seem like more and more sites are chucking out open betas of their homepages these days, very web 2.0.

The grand daddy I suppose was the BBC one - [ http://www.bbc.co.uk/blogs/bbcinternet/2007/12/a_lick_of_paint_for_the_bbc_ho.html  ] which most people probably saw, but recently Facebook have rolled out a new one as well as the retailer Comet.

Why have they all bothered?

Well, first of all, its much better to get real users to test sites out rather than the creators. They respond in so many unexpected ways, to things that you maybe didn’t even think were important at the time.

Secondly, if its a public beta, its a damn site cheaper to sort out that running a more formal usability test. Recruiting participants,

Thirdly, in web 2.0 land (tm), involving users in virtually everything is one of the main tenets of running and managing an online prescence. If users are publicly involved in the consultation around a new home page, they will certainly feel a greater sense of engagement with it and ownership over it.

So, to get the best out of it, here is my top ten (ahem, er, seven) for running a public beta:

  1. Make sure you have enough changes to make a beta out of - nobody is going to bother to check out the new beta of your new contact us icon. Just roll that one out as usual. 
  2. Make it clear how people can send comments on the beta
  3. Tell people what you are going to do with your comments
  4. Tell users of the alpha site that you are doing a beta
  5. Check you have good stats to record how many views your beta is getting
  6. Seed links to the beta through chosen forums, to try and get the word out in as many ways as possible
  7. Play nice with your users now - if it all goes well for this beta, users will also get involved in future rollouts and might be interested in helping out on other things

Any examples on the interwebs currently?

Well, Comet has a new beta out:

www.comet.co.uk/shopcomet/betahomePage.do?zone_id=13

and what I quite like about it is that users comments are actually public here:

www.betacomet.co.uk/

which is a rare thing. The BBC has a  new gardening site here:

www.bbc.co.uk/gardening/ 

and the comments go here:

www.bbc.co.uk/vision/genres/feedback.shtml?genre=gardening

but aren’t public, at least it tells you what is going to happen to them anyway.

If I find any more, I will post them back here.