+1 on what Kieran said... Please read below for a super cool idea on how to fix this problem.<br><br><div><span class="gmail_quote">On 9/26/06, <b class="gmail_sendername">Kieran Lal</b> <<a href="mailto:kieran@civicspacelabs.org">
kieran@civicspacelabs.org</a>> wrote:</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style=""><div>2) We need to come up with a fast, error free way, to change that logo and make the user have a positive experience in controlling the look and feel of their site. Suggestions: tooltips with instructions on how to change, instructions embedded in the image, welcome page instructions to be tested with newer users.
</div></div></blockquote><div><br>Hmmm, I just had an interesting idea... I'll get flamed for it I'm sure as I have no way to implement it, or even if it's possible. <br><br>But what seems like it would be cool is, to provide a "Lock/Unlock" Theme switch that an admin could even hide. So somewhere, on the default theme, Perhaps above the Login area, or somewhere on the actual Primary Links, you have something like: Theme Details: Change / Hide This [?]
<br><br>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. Next to the Drupal Logo would now be the words: "Click to change this image". with AJAX browse for new logo and upload all rolled into one easy thingy.
<br><br>If they click the [?] it tells them what that stuff is all for. If they click Hide, it prompts "Are you sure you want to hide this, it will make it more difficult for you to change your theme elements in the future?"
<br><br>Am I a genius or what? *chuckle*<br><br>Peace Love and Bananas.<br>Trae<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style=""><div>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.
</div><div><br></div><div>Cheers,</div><div>Kieran</div></div>
</blockquote></div><br><br clear="all"><br>-- <br> Trae McCombs || <a href="http://occy.net/">http://occy.net/</a><br> Founder - <a href="http://Themes.org">Themes.org</a> // <a href="http://Linux.com">Linux.com</a>