Posted by eigentor on May 2, 2008 at 5:48am
og_panels is here! And when I look at this http://groups.drupal.org/drupal-dojo I gotta say, I get a little envious... With being quite some design people here in this group this page should rather look that good.
And it is not only about eye-candy: make the information better accessible by introducing more blocks. I volunteer to provide mockups and do the stuff. But I think we depend on Neill Drumm to get things rolling...
Ah, and that's not all. Look here: http://groups.drupal.org/node/10445
Comments
More calls to action
I'd like to see more calls to action. Big buttons to sign up for local groups, attend events, volunteer for a mini-task.
If a user hasn't signed up for a local group, I'd like to see a notice that suggests they sign up for a local group when looking at a local group.
Alternately, if there's an event in their local group, I'd like to see the ability to add the event to your calendar and to forward an invite to an event to get some viral activity going.
Cheers,
Kieran
Drupal community adventure guide, Acquia Inc.
Drupal events, Drupal.org redesign
OG Blueprints
Not to push my own modules, but...forgive me for pushing my own modules :)
OG Panels is designed to allow individual group admins to add as many panels as they want to a given group. However, every group admin has to start from scratch.
If what your after is raising the baseline appearance of groups across the board using og_panels, then you should look at OG Blueprints. It lets you construct design a 'baseline' set of og_panels that all new groups will immediately have upon creation.
Some tips, and discussion points
Top issues core
Usability Reports
Usability Books & Resources
Discussion
Since there isn't an discussion page on the wiki, we should just go ahead and paste it all in here. I sincerely consider ground breaking changes not to be top priority projects, since at the moment they are continued by long threaded discussions that are not step-in-able for people who want to participate. Or are driven by rules and principles that are outside of the CMS domain we are in, or are kayak problems to the user.
If we want to drive for actions, we should focus on tasks that are highest priority and work on some that require a lot of discussion and research. So clearly separate between those that need immediate action and those that need discussion. Personally I believe there is a lack of training(stuff to read, listen to) amongst the Usability group on how to give qualitative feedback that can get improvements in rather then opinions, maybe its smart to refer to some topics on that field.
I added the h3 Usability books & Resources as I found them incredibly important, I think that Luke's might be a bit to heavy though, and for the amazon.com book we should put up a drupal assoication account that can be setup as referral.
Oops!
I was a bit sleepy, so I acctually put this in for a second on the real usability wiki for this group. Should be fixed.
So clearly separate between
Having one or two words about each project's status/needs would be good.