Dave Burke : Freelance .NET Web Developer specializing in Online Communities

CSBlogs : Smart Registration Design and useability considerations

I like the Community Server registration piece.  I think it is smartly designed, particularly in that it asks for essential information only: username, password and email address.  It takes the burden out of registering and quickly enables the benefits of CS registration: post tracking among them.  Always room for improvement, of course, as I would get rid of a username requirement (replace it with optional first and last name fields) and make the email address the unique user identifier.  I would also get rid of the forums verbage at top of the page and with extreme prejudice would eliminate the line "By creating a user I agree to the rules and terms of use published on this site." 

Okay, so registration for my CSBlog would be a snap.  I could turn off anonymous posting, there would be no need for CAPTCHA, and I simply ask readers (in my sweet voice) to kindly perform a one-time 20-second registration process to enable comment entry.  Tempting, but not going to happen for two primary reasons. 

  1. I found through experience that as easy as I've tried to make registration here with a drastically streamlined DotNetNuke registration module, people resist registering.  I don't blame them.  I'm not going to register at your blog either.  It's just too weird.  I eliminated the registration requirement here for the post tracking mod I created, in fact.  What I did instead was auto-register users as part of the comment entry process when they entered a valid email address and checked "remember me."  That really boosted participation in the post tracking function and avoided the nasty concept of registration.
  2. Apart from Registration Resistance there are useability considerations.  Let's say readers do decide to register with the simple CS piece I would provide.  All is good until you consider the required login element.  CS may retain identity to avoid logins on return visits, but if you're on a shared host like 90% of us you cannot absolutely depend on persistance as I've found with WebHost4Life recently.  Bottom line, I don't want visitors to have to login to add a comment.  End of story. 

So we'll start with anonymous posting and CAPTCHA and see what happens along the way.  I'll keep you posted (if you register first.)  KIDDING!

 

Comments (2) | Post RSS RSS comment feed

Posted on 3/23/2005 9:14:00 PM by Dave Burke
Categories: Community Server
Tags:

Related posts

Comments (2) -

3/24/2005 12:33:00 AM Permalink

blog and forum registration is why I mourn the loss of passport.  I refuse to sign up for another forum because I already have so many that I can not remember.  A CommunityServer central membership server (running passport, liberty, anything) would be a great first step.  

I would love to register as a member of a few hundred blogs/forums at once, but I just can't be bothered to register with 5 different ones that look exactly the same and that I don't visit enough to keep my log-in cached.

Shannon J Hager |

3/24/2005 8:29:00 AM Permalink

Hey, Swingin' Shannon!  Passport.  Heh.  I never thought of a more universal authentication scheme for CS.  I wonder if the Telligent fellas ever did.  That's a great idea.  I like how you described the re-login problem as "don't visit enough to keep my log-in cached."  That's more clear than the "user authentication persistence" approach I've been taking.  Thanks for your thoughts on registration.

Dave Burke |


Powered by BlogEngine.NET 2.0.0.36
Theme by Dave Burke