CiviCRM.org Redesign Project 2011

Hi,

For our chat, quick braindump of various points (really good docs btw, below a trying to focus on what didn't work 100% when I read/scanned them):

Identity discover:

- the point about holistic vs. bunch of modules is really important IMO, but didn't find it reflected in the schematic (that I read a focussing on a list of needs/features)

- measuring success: I strongly thing that one of the main focus should be about growing our contact db (ie. let's apply to ourselves what we are saying to our customers)

- demo: according to google analytics, that's one of the most visited page now. I think the discovering by playing with it works quite ok, any reason to "hide" it? (and open question: shouldn't we use it as a way of collecting data about the visitors ?

Schematics

- Are the mugshots on the banner only for dev (I doubt we'll find a lot of clooneys in that population) or also for users ?

- Not sure I understood the logic on what goes on the primary menu (above the search) vs. the secondary one (on the right of the search

- It seems to be a lot of focus on the new visitor, didn't find what the regular visitor would want to see (eg I'd want a link to /blog to the unread replies on the forum, but seems to be mostly me needing to get use of the nav)

Here are some points along similar lines of xavier's brain dump:

- Create a "user intention survey" ahead of CiviCon, use on new civicrm.org site as part of demo signon to gather data on prospective customers or current users of CiviCRM (In CiviCon case tie it to free admission to the event as a raffle to give prospective users/attendees an incentive to tell us about their use case early on)

- Tie into the site relaunch a set of screencasts of the current capabilities of the latest CiviCRM release that gives a nice overview of the current feature set (maybe segment out for different use scenarios, membership, donations, events)

- Regarding revisit value-add for existing users (i.e. pull them back to the site), we should try to bring out a new screencast every 2 weeks on a regular schedule, but definitely for all new releases (timed with the release). We're formalizing the technical production workflow and so far we've got CiviCRM, Korlon and Emphanos committed to help write scripts for a set of simple 2 to 4 minute how-to screencasts (would be good to have a way of proposing and scripting future screencasts with others from the community moving forward)

- Show the vibrancy of the CiviCRM community by showcasing meetups through picture slideshow (video footage?) and narration, explaining what happens at a meetup (topics covered, who comes, why?), to encourage more people to attend them to learn more.

- List a set of other CRM systems that we as implementors have been successful at migrating data out of and into CiviCRM (e.g. Salsa DIA, Salesforce.com, Raiser's Edge, eTapestry, Convio, etc.)

- Timelines showing which versions of CiviCRM will be supported until when. Same view should contain information on which version of CiviCRM is to be paired with a given CMS release. (Link to this table a similar graphic indicating maturity of the release tied to open issues and bugs? Time since release?)

- In table view showing which features are available/unavailable depending on the choice of underlying CMS (this is a recurring question that should be handled by an infographic or table view, especially with respect to ACL-related limitations)