Habari Website

[Alex Hempton-Smith]

One of the ways I'd like to help the Habari community is to start looking at what I can do to improve the official website. I've been working on some designs and feature proposals which I'd like to share over the weekend, but before I do it would be interesting to get some information from the community about your views of the current implementation.

If you could spend a few moments writing out a wish-list of things you'd like to see added or changed, and things that would be key for a website overhaul, it would be hugely appreciated!

Many thanks,
Alex

Ps. Who's currently responsible for the website, and are there any plans in the works that I should be aware of?

[John Wrana]

What I don't like at the current website is that »black hole« with an
white arrow (the screencast). Is it possible that there is an initial
image to see if you come to website?

Also some thumbnails of screenshots could be eyecatchers and may
impress people with the clean interface of habári.

Otherwise I like the website so far.

Regards,
John

On 22 Mai, 02:21, Alex Hempton-Smith <hempswo...@googlemail.com>
wrote:

[David]

On May 24, John Wrana <m...@jowra.com> wrote:
> What I don't like at the current website is that »black hole« with an
> white arrow (the screencast). Is it possible that there is an initial
> image to see if you come to website?

Good point. I once got rid of a black hole in a jw_flv_player object
with:

so.addVariable("image","http://www.url.com/image.jpg");

The actual page in question is: http://my.dlma.com/2007/06/24/game-face/

Please forgive that blog's engine, it was years ago. :)

--David

[Andrew Hagen]

The way I evaluate blog and CMS software is to examine the official
web site. The official site indicates what my site would be like if I
were to install the software. In particular, I am looking for
features. I also take notice if the site loads quickly or not. It
seems safe to assume others use a similar method of evaluation.

The current Habari front page provides good basic information. The
front page, http://habariproject.org/en/, has many important items
linked. This includes download, demo, documentation, support, FAQ, and
community. There is an indication of how to pronounce "Habari" and
what it means. There is a concise list of key features.

The Habari blog, however, should be the main part of the Habari front
page. Unfortunately, it's not. The main features of a Habari blog
should be demonstrated right on the front page.

On the current front page, there is no link to an Atom feed. There is
no link to a tag cloud. There is no indication of what is the home
page for the blog, other than perhaps http://habariproject.org/en/page/1.

The video is helpful, but it should not occupy the prime spot on the
home page.

I would suggest the following changes.

* Move the blog to the large column on the front page. Give the blog a
new, prominent home page, like http://www.habariproject.org/.

* Use the charcoal theme for the blog, as it is the most distinctive.

* Take a screenshot of the video. Place a thumbnail of the screenshot
in the sidebar in the right sidebar. Link from that image to a blog
item that contains the video.

* On the top link bar, add links to the wiki, the demo, and the screen
shots.

* If the home page has been translated to a language other than
English, link to that translation. Otherwise, create a new link to
"help translate Habari to new languages." A static web page managed
from Habari could be the launch pad for that effort.

* Try to manage as much of the web site from Habari as possible.
Habari is not attempting, of course, to be an all-inclusive CMS.
Having separate software for the wiki, for instance, is perfectly
acceptable.

* The right sidebar should have a link to a page dedicated to
"Technical Specifications." That page should list the system
requirements (such as PHP 5.2.0), the fact that Habari uses PDO (a
very good thing), the databases Habari can use, template engines, and
other specs. Technically-astute persons should find everything they
need to quickly evaluate Habari.

* The right sidebar should have a search box that submits a custom
Google search covering the entire web site.

* Keep in mind that the web site has two audiences: users and
developers. Today a large proportion of visitors are developers. It
can be foreseen that in the near future regular users will greatly
outnumber the developers. Users should be steered toward feature
lists, user mailing lists, community forums, the wiki, the FAQ list,
available themes, and so on. Developers should be steered toward
plugin and theme development information, developer resources, and the
wiki. Maybe there should be a second, development-oriented blog.

* Add a footer with a link to an about page. This should indicate that
Habari is available under Apache License 2.0. There should be a
notation as to when the project was founded, why, and who did so.
There should be a link to the Habari cabal wiki page, or other
explanation of the project's decision-making process. There should be
a note about whether this is affiliated with any other project like
Apache. There should be a note that options such as becoming a non-
profit organization have been proposed, but no action has been taken
as yet.

* Don't throw out the good. There is a lot of great information on the
web site. It's just not presented or organized as well as it could be
thus far.

[Arthus Erea]

Frankly, this makes no sense.

I'm not sure you understand the intent of the Habari project site.

It isn't to be a blog, it's to provide information about the project. We most definitely should NOT make the homepage the blog.

Tag clouds are useless, distracting, and provide nothing of value to the project site.

Instead, we should focus on the features which Habari provides. Those features should be demonstrated through linked screencasts and/or screenshots.

No offense to Ali, but I frankly don't think the Charcoal theme is the best way to highlight Habari. It's not built around the features we need. The equivalent would be showing up at wordpress.com and seeing kubrick and a list of releases... not exactly very impressive.

[Michael C. Harris]

Hi Andrew,

Thanks for taking the time to outline your thoughts about this. There
has been some effort to document the goals and requirements of the
Habari web site. It's a work in progress, so feel free to pitch in.

http://wiki.habariproject.org/en/Designs/Habari_Home
http://wiki.habariproject.org/en/Habari_Website_Overhaul

--
Michael C. Harris, School of CS&IT, RMIT University
http://twofishcreative.com/michael/blog
IRC: michaeltwofish #habari

[Scott Merrill]

On Mon, May 25, 2009 at 7:49 PM, Arthus Erea <arthu...@gmail.com> wrote:
> Frankly, this makes no sense.

The tone of this reply bothers me. A lot of what we discuss regarding
the Habari home page will be bikeshed issues. We all have strong
preferences, but they're all just that: preferences.

> I'm not sure you understand the intent of the Habari project site.

There is no specific, unified, unerring intent. A website will be
different things to different people.

> It isn't to be a blog, it's to provide information about the project. We
> most definitely should NOT make the homepage the blog.

I actually think we should be displaying blog entries more
prominently. We should show that we're eating our own dogfood, as well
as demonstrating some of the advanced ways our blog software can be
used.

> Tag clouds are useless, distracting, and provide nothing of value to the
> project site.

I personally dislike tagclouds, but I recognize that that's purely a
personal preference. Some people like vanilla ice cream, some people
like chocolate. To say that tag clouds are useless is pretty
grandiose. YOU find them useless.

I agree, though, that a tag cloud doesn't provide much benefit for the
Habari home page.

> Instead, we should focus on the features which Habari provides. Those
> features should be demonstrated through linked screencasts and/or
> screenshots.

I don't disagree with these suggestions.

Cheers,
Scott

[Arthus Erea]

Hi,

I'm sorry for being too harsh in my initial reply—this is an issue I care strongly about.

On May 25, 2009, at 8:59 PM, Scott Merrill wrote:

On Mon, May 25, 2009 at 7:49 PM, Arthus Erea <arthu...@gmail.com> wrote:

Frankly, this makes no sense.

The tone of this reply bothers me. A lot of what we discuss regarding
the Habari home page will be bikeshed issues. We all have strong
preferences, but they're all just that: preferences.

On a second reading, the tone bothers me too. I should've taken the time to read it through. (How many times has that happened to me!? :( )

However, I'm not sure these are really bikeshed issues. You're right, there are a lot of bikeshed issues with the site: what color we use, etc.

In contrast, I think this is really about setting down the purpose of the site. And I am adamant in that the main purpose of the site should be to:

– Entice new users

– Provide support for existing users

– Integrate the community

In my opinion, having our blog front and center doesn't serve any of those purposes especially well. I don't think the #1 thing people come to the site for is to find a list of our most recent releases.

I'm not saying we shouldn't have a blog, I just don't think it is the most important reason for the site. The first thing I want a potential user to see isn't:

"Today we are pleased to releaseHabari 0.6.2, the latest update to our 0.6 release. This is a modest update which fixes two potential security vulnerabilities. All users are encouraged to update."

It's more important that we encourage people to download and learn about Habari—then they can start getting interested in the latest releases.

There is absolutely no reason a first-time visitor to the site needs to know about the last 5 releases, as the first thing they learn. I'd much rather tell them our top 5 features.

It isn't to be a blog, it's to provide information about the project. We

most definitely should NOT make the homepage the blog.

I actually think we should be displaying blog entries more
prominently. We should show that we're eating our own dogfood, as well
as demonstrating some of the advanced ways our blog software can be
used.

Isn't that what the whole site does? I mean, it's not like *any* of the main site isn't powered by Habari. It's just as much "eating our own dogfood" to show off a features list or a 

Tag clouds are useless, distracting, and provide nothing of value to the

project site.

I personally dislike tagclouds, but I recognize that that's purely a
personal preference. Some people like vanilla ice cream, some people
like chocolate. To say that tag clouds are useless is pretty
grandiose. YOU find them useless.

Sure, that's true. But what does it say that both of us find them useless?

That's not to say we shouldn't have one. But it's probably best relegated to /blog.

Again, sorry for my harsh and rude reaction.

~Morgante

[Alex Hempton-Smith]

Thanks for everybody's input so far, I'm a strong believer in getting heaps of feedback and opinions and refining them later on, so keep it coming! Although homepage content is an important part of the overall website, it is just a part and I want to reaffirm that the 'Website Overhaul' effort isn't just about the homepage. However, it's kicking up quite a storm so I'll put in my two cents!

I think the hompage needs to do two main things:

• Show that our software is amazing
• Show that we have an active and welcoming community of users and developers

And that's all people want to see when they visit for the first time. We need to convince them to download Habari before we slam a download link in their face! :P

How do we show it's amazing? Screenshots, videos and well organized featurelists - perhaps split developer specific features from the rest, and list summaries of our features and be able to click on the summary sentence and have more details expand below it?

How do we show off our community? Have an activity stream for the whole site, aggregate recent activity from the forums, trac, mailing lists, and blog. There is an incredible amount of things going on every day, and you just don't get that feeling of a vibrant community from visiting the site, it's very 'static'.

I also feel we need to make the official blog less of a release announcement blog, but a place to get weekly roundups on decisions made, and changes in trunk, in ways people can get involved, we may want to post a survey to see what features get into the next few releases etc etc.

Repeat visitors are a different story, but we can accommodate them too... It's almost a given that the new site will have user accounts, so when a repeat user logs in they will be shown a different homepage to a first time visitor.

All users could have a personalised homepage which they customize (?), tick boxes to choose what widgets appear on there and drag and drop them around? So I could choose to have the feed for the -dev list on there, a latest/popular plugins widget, an API QuickSearch widget for when I need to find an Habari function quickly, and a tonne of other widgets I choose. My experience of the Habari site is now far more personal, and tailored to my needs.

Developers will be able to visit the 'Developer Center' homepage which will be more relevent to them and offer them quick access to the developer wiki, blog posts tagged 'developers' will be shown, latest activity in the -dev mailing lists, trac activity and SVN commits etc etc.

Regular users will be able to visit the 'Community Portal' homepage, a place dedicated to making community participation easier. We will have feedback polls, surveys, latest extensions, forum activity, we can embed an IRC client to make it easier for people unfamiliar with it.

The Developer Center and Community Portal will be available to new users, and linked to from the homepage, but it gets a whole lot better when you log in...

I've talked too much, and probably talked some rubbish, but these are my random-ish ideas - feedback and refinement is needed!! :)

-- Alex  (Hempsworth)

[Owen Winkler]

I'm glad that people are interested and passionate about the hp.o site.

My current major concern: If we do not state what we are trying to
accomplish with the site, then we have no means to evaluate the success
of any changes.

Alex gets off to a decent start here:

> I think the hompage needs to do two main things:
>

> * Show that our software is amazing
> * Show that we have an active and welcoming community of users and
> developers

But I think that this only really applies to one type of user who would
visit the site. There are actually FOUR types of users who visit our
site. (I documented this long ago at
http://wiki.habariproject.org/en/Designs/Habari_Home)

I certainly don't need to know that our software and community is
amazing. I'd nevertheless appreciate direct links to the API docs, the
wiki, or support channels. We might say, "yes, of course," to these
issues, but we do need to remember that our biggest contributor to the
goal of bringing in new users right now is word of mouth. Satisfying
the needs of users who are willing to try and stick with Habari is just
as important as bringing in new people.

The above are also hard goals to measure. Is there a click-through that
serves as verification that a user agrees our software is amazing, or
that the community is welcoming? Hard to say. "We're awesome! Click
here if you agree!" Some more down-to-earth goals could be
quantifiable, like, "Turn X% of visitors into registered users." Or,
"Have X% of visitors continue from the home page to at least one more
page." In analytics terms, these are called, "conversions." We should
assemble a nice list of these and discover a way to measure them.

We need also to keep in mind that our home page (as distasteful as it
may seem) must include some SEO. If a goal of the site is to attract
new users, and they never find our site when searching, we've already
failed. One of the primary reasons to have the blog on the home page is
to keep fresh content available for search engines. We're currently
doing a poor job of keeping that content fresh and engaging -- oh, well.

There are some claims being made by folks about what users want to see.
I made this Crazyegg heatmap a while back, showing where people
actually click on our site:

http://farm4.static.flickr.com/3178/2817018229_663dc042c1_o.png

This one for the wiki is not quite as useful (because Crazyegg's page
rendering throws off the columns on the wiki), but does indicate our
dire need for themes (not just a directory to hold them, but an actual
quantity of themes):

http://farm4.static.flickr.com/3269/2814569817_ddc9a208d5_o.png

I'd suggest looking at actual analytics to see how people are using the
site, but someone insists on loading Woopra onto the site instead of
something useful, and I'm not sure how to access the Woopra stats. To
be clear, I don't want to access the Woopra stats -- I want real, public
analytics. We should choose a single, web-based analytics provider, and
open up access to review the statistics there. Sadly, none of our
historical stats are going to be in there.

In any case, I'm sure that we can do the site better, but it would be
folly to take the knowledge that is available and research that has been
done and discard it in the name of a cool idea. Whether it's true, it
seems to me like people are coming at the "hp.o sucks" problem with no
review of the past work, perhaps simply because they don't like the
site's current design.

Nonetheless, I like the idea of portals for the separate user types,
because it caters to the idea that there is more than one type of
visitor to the site. I'm not sure that those should be automatically
presented based on user preference, but a "developer center" that
appears after you log in would be useful.

On the other hand, I oppose the idea of draggable, personalized,
configurable interface elements. Habari is not Netvibes, and I don't
see that we have that much information to drag around anyway. Please
also keep in mind that this site will require maintenance.

Specifying cool features is fun, but someone has to implement them. If
they're built poorly, or they fail for some reason in the future,
someone will need to fix them. I submit that neglect is the reason the
site is as poor as it is. Making the site more complex will only
exacerbate that issue.

Developing features that do not target our goals would be even worse.

And finally: Tag Clouds--

Owen

[Andrew Hagen]

I am seeing the light on tag clouds. Let me withdraw that suggestion.

My main concern is to expose Habari's features to users on the front
page. One of the best features is the community.

I like the idea of doing two portals. The user-centric information
could reside at hp.o. The developer info could be moved to
dev.habariproject.org.

The user portal should show information relevant to evaluation. This
includes the demo, screenshots, community, and technical specs.

The left part of the top link bar should be devoted to evaluation. The
right side of the link bar could have information about downloading
and installing. Down from there, along the sidebar, could be info on
customizing Habari once it's installed. A large icon to the right side
that says "Get Habari themes" would be very useful, not just for
existing users but also to evaluators.

The plan is apparently to add a login to the site. Users could
customize hp.o to display the information relevant to them. If we're
going to do that we should plan to eventually have a single, sitewide
authentication mechanism. One day, users should need only one username/
password for the entire site. That should include forums, the web
pages, and the wiki. Perhaps OpenID could help. MediaWiki has an
OpenID extension. A Vanilla OpenID add-on will probably be developed
soon, judging by the clamor at http://is.gd/EXmj (Vanilla add-on
page).

We need a little color in the design, too. Right now we are just black
and white.

Andrew Hagen

[Arthus Erea]

Great ideas from all.

I think Alex has definitely gotten a good start, but we should
definitely consider Owen's points about analytics.

On May 26, 2009, at 9:26 AM, Owen Winkler wrote:

>
> I'm glad that people are interested and passionate about the hp.o
> site.
>
> My current major concern: If we do not state what we are trying to
> accomplish with the site, then we have no means to evaluate the
> success
> of any changes.

That's definitely true.

>
>
> Alex gets off to a decent start here:
>
>> I think the hompage needs to do two main things:
>>
>> * Show that our software is amazing
>> * Show that we have an active and welcoming community of users and
>> developers
>
> But I think that this only really applies to one type of user who
> would
> visit the site. There are actually FOUR types of users who visit our
> site. (I documented this long ago at
> http://wiki.habariproject.org/en/Designs/Habari_Home)

Right, I think we should make all our decisions being informed by
those personas.

> I certainly don't need to know that our software and community is
> amazing. I'd nevertheless appreciate direct links to the API docs,
> the
> wiki, or support channels. We might say, "yes, of course," to these
> issues, but we do need to remember that our biggest contributor to the
> goal of bringing in new users right now is word of mouth. Satisfying
> the needs of users who are willing to try and stick with Habari is
> just
> as important as bringing in new people.

Agreed, but I'm not sure the front page is where that needs to happen.
I of course value those direct links, but I think we should break down
the users into 3 categories:
1) First-time visitors/evaluators: for these visitors, we should focus
on what Habari offers. Features and screenshots should be displayed
prominently, as well as links to comparison features.
2) Current users: if you are logged in, then the homepage should
feature information on the latest release, recent activity (across all
of the Habariverse), support information, and a link to file a bug in
trac.
3) Developers: if you are logged in and have marked your account as
"developer" then the homepage includes recent Habari activity, links
to the wiki & trac, and a "quicksearch" field to look up information
in the API.

> The above are also hard goals to measure. Is there a click-through
> that
> serves as verification that a user agrees our software is amazing, or
> that the community is welcoming? Hard to say. "We're awesome! Click
> here if you agree!" Some more down-to-earth goals could be
> quantifiable, like, "Turn X% of visitors into registered users." Or,
> "Have X% of visitors continue from the home page to at least one more
> page." In analytics terms, these are called, "conversions." We
> should
> assemble a nice list of these and discover a way to measure them.

Agreed. I think 3 of the best metrics are:
1) Downloads/home page visits
2) Clickthrough to anywhere else on site
3) Registration

> We need also to keep in mind that our home page (as distasteful as it
> may seem) must include some SEO. If a goal of the site is to attract
> new users, and they never find our site when searching, we've already
> failed. One of the primary reasons to have the blog on the home
> page is
> to keep fresh content available for search engines. We're currently
> doing a poor job of keeping that content fresh and engaging -- oh,
> well.

I like Alex's idea of featuring a "stream" of content, including:
1) Trac updates
2) The blog
3) Forum posts
4) Mailing list threads

If we use good, semantic markup (which I'm sure we will) this should
definitely help to drive traffic.

Also, I think *all* homepage versions should be accessible to search
engines. Perhaps at /user and /dev respectively, with logged-in users
being automatically redirected.

> There are some claims being made by folks about what users want to
> see.
> I made this Crazyegg heatmap a while back, showing where people
> actually click on our site:
>
> http://farm4.static.flickr.com/3178/2817018229_663dc042c1_o.png

Thanks for putting that together! It's definitely useful in our
evaluation.

Based on those links, these are some things I think would do well on a
new page:
1) High quality documentation, including the ability to search it.
2) Enhance the demo with a variety of themes, making it easy to switch
between different themes. I'd also like to (once again) offer that we
use the "tour" I developed.
3) Screenshots *must* be on the homepage. The UI is one of the best
things Habari has going for it, and people are clearly interested in
finding out more.
4) We should compile a 2 different "why Habari" pages, and link them
from around the site.
— Users
— Developers

> I'd suggest looking at actual analytics to see how people are using
> the
> site, but someone insists on loading Woopra onto the site instead of
> something useful, and I'm not sure how to access the Woopra stats. To
> be clear, I don't want to access the Woopra stats -- I want real,
> public
> analytics. We should choose a single, web-based analytics provider,
> and
> open up access to review the statistics there. Sadly, none of our
> historical stats are going to be in there.

Agreed. Does GA seem acceptable? We could have a shared profile
accessible to anyone who wants it. In fact, we could even have
periodic reports sent to the list automatically (if desired).

> In any case, I'm sure that we can do the site better, but it would be
> folly to take the knowledge that is available and research that has
> been
> done and discard it in the name of a cool idea. Whether it's true, it
> seems to me like people are coming at the "hp.o sucks" problem with no
> review of the past work, perhaps simply because they don't like the
> site's current design.

Agreed, but I do think Alex at least is doing a good job of looking at
past information. The wiki pages and linked threads are definitely
helpful.

I think the most important part is nailing down the what and the why,
then focusing on the how (design).

> Nonetheless, I like the idea of portals for the separate user types,
> because it caters to the idea that there is more than one type of
> visitor to the site. I'm not sure that those should be automatically
> presented based on user preference, but a "developer center" that
> appears after you log in would be useful.

As I briefly referenced earlier, I think we should have 3 homepage
versions. Anyone can access any of them, but based on your login it
will direct you to one. They should *all* be linked to from each of
the homepages.
1) /welcome — basic information, "why habari," etc. default for non-
users
2) /user – support and community information, default for registered
users
3) /dev — community and reference, default for registered developers

> On the other hand, I oppose the idea of draggable, personalized,
> configurable interface elements. Habari is not Netvibes, and I don't
> see that we have that much information to drag around anyway. Please
> also keep in mind that this site will require maintenance.

Agreed. Seems like bloat and web 2.0 just for the sake of web 2.0.

The only setting you should have as a registered user is default page:
user or developer. In fact, that wouldn't even be a setting. It would
simply use the last version you clicked.

Thanks for all the thoughts,
Morgante

[David]

On May 26, Owen Winkler <epit...@gmail.com> wrote:
>  There are actually FOUR types of users who visit our
> site.  (I documented this long ago athttp://wiki.habariproject.org/en/Designs/Habari_Home)

I'll volunteer my anecdotal experience. I'd never have installed
Habari if I hadn't seen the Monolith videos at Viddler.

What really brought me here were the silos, the loupe and the clean
entry-editing pages.

These things are not *adequately* represented on the home page.
(Mentioning "silo" as a Feature bullet-item doesn't tell me what it
is. Only after seeing it at viddler did I fall in love.) Don't get
me wrong: I'm not suggesting we clutter the home page. Just saying
that "silo" and "loupe" don't mean anything to me there.

The install video? Not so useful until after I was interested. (It
still really needs the so.addvariable( "image"...) too.) The install
video to me was less important than seeing screenshots of the admin
panels, editing page, and videos of the loupe and silo interactions.
I mean, regarding installing, I just assumed installing wouldn't be
any more difficult than most other blog engines. Php, database, what
else should I need? An easy install is a prerequisite. Not so much a
top-item feature.

I always scan for a feed icon. May be nice to put one (with a link to
the feed of course) next to "Community Blog". In the sidebar, it'd
reinforce the idea that what follows there comes from a blog, and that
this index page is not itself a blog page.

> We need also to keep in mind that our home page (as distasteful as it
> may seem) must include some SEO.  If a goal of the site is to attract
> new users, and they never find our site when searching, we've already
> failed.

So true. Searching for "habari screenshots" "habari panel" and
"habari admin" really didn't put me where I wanted to be. If I
haven't installed it yet, I'd want to see current screenshots, to know
if I want to bother downloading.

> There are some claims being made by folks about what users want to see.
>   I made this Crazyegg heatmap a while back, showing where people
> actually click on our site:
>
> http://farm4.static.flickr.com/3178/2817018229_663dc042c1_o.png

That's exactly how I clicked. I feel like it was recording me. If
the word "screenshots" had been there, it'd have been pretty hot, too,
I'd guess. If "plugins" and "themes" were links, you'd have seen
significant heat there, too, I'd wager.

I wasn't interested in the community. I wanted to learn about the
product Habari. The community is awesome, but that's not what I was
originally investigating.

> Nonetheless, I like the idea of portals for the separate user types,
> because it caters to the idea that there is more than one type of
> visitor to the site.  I'm not sure that those should be automatically
> presented based on user preference, but a "developer center" that
> appears after you log in would be useful.
>
> On the other hand, I oppose the idea of draggable, personalized,
> configurable interface elements.  Habari is not Netvibes, and I don't
> see that we have that much information to drag around anyway.  Please
> also keep in mind that this site will require maintenance.

Phew. I'm glad you said that last bit.

> And finally:  Tag Clouds--

At the blog? Whatever. At the home page? Not really applicable.

--David

[David]

On May 27, I wrote:
> On May 26, Owen Winkler <epit...@gmail.com> wrote:
>
> > I made this Crazyegg heatmap a while back, showing where people
> > actually click on our site:
> >
> >http://farm4.static.flickr.com/3178/2817018229_663dc042c1_o.png
>
> That's exactly how I clicked.

Whoops, that's not necessarily true. I looked at the heat-map again,
and realized that I felt that the screencasts and screenshots links
were buried in the "word word word word word" part after the embedded
screencast. It's possible that if those links were more prominent
that they'd have gotten more clicks. (I think they would have for
people like me.) I like how movabletype makes them prominent. OTOH
Wordpress.org frustrated me. I clicked for 10 seconds without finding
adequate screenshots of the admin area.

--David

[Shawn J. Goff]

I like a lot of the ideas here.

The three different user types are perfect except: let me set a cookie
for my default, but don't make me fill out another damn registration
form! I hate filling out registration forms; I hate validating e-mail.
Just store a cookie for me. One possible way is like this: there
should be the links for the different pages somewhere; next to the
text for the one you're on, place a pin - if I click the pin, set that
one as my default page. The pin may have a javascript tooltip type
thing that says "Make this my default Habari home".

There should be at least two "example blogs" which have lots of fake
content with entries, pages, plugins, etc. They should be very
different from each other. If possible, make them demo-fied, too.

I think the colors are fine. I also love the big text. I love the look
of the home page as it is now.

Instead of the development blog, it would be nice to have a feature
spotlight sort of blog (like Habari minute, but text) up there.