I'm a little unclear about the difference between Documentation and Community Support given the Documentation has community contributions and the stuff in Community Support is often heavily indebted to the core team (eg forums, IRC, presentations).

I think Forums and FAQ are buried too deep at 3rd level.

If I understand correctly, the top level menu items are About, Support, Blog, Donate. I would have more items at the top level.

I like burying the stuff in the Additional Resources down at a third level.

A task orientation that would segment people wanting differernt types of resources might be:

1. Resources
   1. Evaluating
   2. Installing
   3. Configuring
   4. Using
   5. Customizing Look
   6. Customizing Functionality
   7. Getting Help
   8. Reporting a Bug
   9. Developing Enhancements

Each page would have links into appropriate parts of the book, the documentation, the relevant forum(s), etc. I see Resources as an additional way in to stuff to supplement top level menu items for Download, Documentation.

HTH

Hi,

Some quick thoughts before I have to run to a meeting.

Great that this is starting off.

I think we need to do a high level split between non-profits and developers.  The site is pretty good for developers already but we don't do well enough for non-profits.  I think a home page puts more emphasis on non profits would be a good opening to the site.  If I get time, I'll make some mockups based on the below...

Non-profits

The current website assumes that the visitor is familiar with the architecture of an open source product websites.  But that definitley isn't the case for the majority of non profits.

These people need to quickly evaluate if CiviCRM is right for them.  Can it do what they want it to do.

So how about start off with a list of things that CIviCRM can do.  Rough draft...

CiviCRM can help you...

• Run email campaigns
• Raise money
• Manage events
• etc.

Start by

• Trying the demo
• Hiring a consultant
• Talking to community people (if you want to find out more)
• Getting stuck in and doing it yourself (if you have an internal IT dept.)
• Seeing if something is happening locally

[From Xavier]

Looked at the stats. This page is a very important one, and beside being quite ugly, I think we miss there the opportunity of promoting more the customisation and various option based on what type of organisation is going to use it (what you described yesterday) http://civicrm.org/download

It seems to be coming along well. A few additional points:

It would be helpful to me to know more about home page content as the points above focus on navigation it seems. A mockup of home page and a few other pages would be a good next step to ensure we're on the same page about what's on these pages.

I would label the blog as Developers' Blog, and move it to a lower importance towards right or in a three column format, in a block down on right.

I think the forum should not be treated as a monolithic whole, but have each forum container referred to in appropriate places. We want people with installation and simple use issues to end up directly in the appropriate forums, and assist developers getting back and forth between their forum and appropriate wiki material etc.

I would drop the list archives.

Can we integrate search across wiki forums book and site? It's very important for user experience, and for newbies to find what they want. Apache solr might help.