5.0 Core Theme Update

Trae McCombs wrote:
> I think a happy medium (since this is a theme by
committee) is a 
> "Powered by
> Drupal" button/icon/something above the fold. 
This would probably be
> something most people will want to leave in place to
show their support for
> Drupal.  And not hinder them putting content in other
places.  The first
> thing people do with Bluemarine, I'm guessing, is to
strip (somewhat
> difficultly for newbies) the Drupal logo at the top.

I am totally ok with them removing the Druplicon after the
install. In 
fact I used to complain if somebody didn't replace the
favicon with one 
of his own. The point it to show branding to the guy who
installs the CMS.

It is also not difficult to replace the logo, you only need
to upload a 
new one.

> If there is a "powered by" button, above
the fold, and NOT the big giant
> Drupal logo, then people are going to be more likely to
leave it in place
> even when they customize the theme.

I won't mind a html block which has such a banner.

Cheers,
	Gerhard

Kieran Lal wrote:
> 3) If we do create an initial configuration process
then modifying the 
> logo should be part of that process.  This is part of a
general 
> problem of Drupal's administration interface being
feature oriented 
> (logo is part of the theme features and is therefore in
administer >> 
> themes >> global settings) instead of
situationally aware that 
> changing the logo is a common initial task that is part
of initial 
> site configuration.  Perhaps more situational
interfaces could be 
> introduced as a goal in the future.
It's a general problem with many feature-oriented
interfaces.

Some obvious questions:

Are there other common look-and-feel tasks that occur at
this point in 
the user's experience?  Any feel as to whether changing the
(default) 
theme should be done before or after changing the logo?

Are there any other tasks, besides configuring
look-and-feel, that 
compete for the user's attention immediately after setup
and logging in 
as administrator?

Gary

On 26 Sep 2006, at 10:36, Kieran Lal wrote:
>> It is also not difficult to replace the logo, you
only need to  
>> upload a new one.
>
> I have been doing some user testing on logo changing,
this week,  
> and in fact it's quite difficult for new users.  It is
a serious  
> user experience issue because many people report that
they want to  
> immediately change the look of their site so they feel
they own it.

I agree.  Task completion on changing logos is poor.  I've
had quite  
a few complaints about the logo being hard to change.  For
starters,  
it requires that the user has the files-directory properly
setup and  
that he can figure out the location and UI for uploading a
new logo.   
Then, often times, the logo is too small or too big.  The
entire  
process can easily take up 20 minutes and is not free of  
frustrations.  Not exactly fun if this is part of your first
30  
minutes of Drupal.

> 1) Task completion on changing logo's is poor.
> 2) Error rates in discovering how to change a logo is
high.  Even  
> if you knew exactly where to go it's a minimum of 4
clicks for a  
> initial task, with plenty of room to make mistakes.
> 3) Time is not unreasonable, but it could be much
faster in the  
> cases where they succeed.
> 4) Users failure to complete the change in the look of
their site  
> leaves them with a subjective negative experience.

--
Dries Buytaert  ::  http://www.buytaert.net/

On Sep 26, 2006, at 6:35 AM, Trae McCombs wrote:

> Perhaps we use AJAX goodness, and if you click the
"Change" button,  
> then the logo, mission statement, other items right
there on the  
> front page immediately become editable via some form or
some thing.

http://cvs.drupal.org/viewcvs/drupal/contri
butions/sandbox/timcn/soc/ 
liveedit/
http://groups.drupal.org/soc-admin-usability-improvemen
ts
http://drupal.org/node/7
8942
http://drupal.org/user/1
4572

enjoy,
-dww