[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: No, not just yet! ;)
From:       "Jason Bainbridge" <JaseOne () myrealbox ! com>
Date:       2002-10-23 3:58:08
[Download RAW message or body]

I am planning to start semi-formally gathering requirements for the new design and \
look at it as a real life project using the proper methodologies as I think this has \
been one of the major problems with the way things have been developing.

Once we have the requirements then I think we can make more informed decisions on the \
final designs. I will be doing my best to trawl through past mailing list posts and \
recording anything that is usable as a requirement, but not any of the "I like this \
one better" comments unless there is a reason given that can be used as a \
requirement.

I think this step backwards is going to end up being a huge step forward in the long \
run, we shouldn't be rushing into anything as when you rush you make mistakes. :-) \
There was a goal originally of launching the new design with the release of 3.1, but \
I think we should forget that goal as it isn't realistic if we want to do this \
properly.

So if anyone has any requirements or ideas for the new design they haven't put \
forward yet please do so, no matter how out there they are or how radically different \
they may be. 

Eric's analysis is a perfect example of the kind of stuff we need so it is a good \
starting point to expand upon as suggested by Irwin.

If anyone has any other ideas or suggestions related to this in anyway please let me \
know. :)

Regards,
Jason

-----Original Message-----
From: Irwin <emerald-arcana@rogers.com>
To: kde-usability@mail.kde.org
Date: Tue, 22 Oct 2002 22:35:52 -0400 
Subject: Re: No, not just yet! ;)

On Tuesday 22 October 2002 08:07 pm, Eric Ellsworth wrote:
> Ok, attached is my writeup of KDE.org.  I'd appreciate it if someone could
> post it publicly so we can refer it as (if) we discuss it.

Comments:

-I see, generally, no problems with the description of the user classes and 
their primary purposes.  I think this is an excellent starting point for us 
to define the purpose of the components on the web page - and Jason has 
already made quite a few clarifications that I hope to be able to emphasize 
(maybe I'll add the comments to the page).  If we wanted to nitpick, we could 
probably clarify some of the points about what users do what.  The 
documentation is easily expanded to contain use cases, actually - it would 
simply be a list of what kind of actions a user may want to do with the web 
site.

From Jason:
> As for the main kde.org site there is a few ideas floating around as to how
> to make use of it the best and use it to kickstart navigation around the
> rest of the KDE sites. There isn't currently any proposals for this that I
> am aware of apart then the original two column design.

I think the navigation and reporting the user's location is very important and 
deserves a lot of thought.  I actually like the listing of the tree in the 
top-left corner, with the separating slashes.  However, the rest of the 
navigation should probably concentrate on the broad "areas" of KDE that 
people are interested in.  We MOSTLY have these areas highlighted in the left 
side of our example web pages "Learn" "Develop" "Download" etc.


Random idea: Perhaps we can put links to the rest of the KDE sister sites only 
in the menus of content pages that are relevant.  For example, the main site 
wouldn't have anything.  But the "Applications of KDE" sub site will have 
links to kate, konqueror, kmail, etc. web pages.  The "KDE for your Whole 
Family" sub site will have links to usability and so forth.  That's a random 
idea, as stated above. :)

Our overall problem spawning endless discussion is probably that we were being 
a little too fuzzy, and not really identifying WHAT we wanted to do, as 
opposed to how it looked.  Perhaps we should take a moment, write down who 
the web site serves and what it will provide to those it serves.  We've 
gotten most of the users listed, so the "what we provide" is going to be an 
extension of that.

-- 
-- Irwin

Dreams may be in sleep, or may occur waking.  In all cases, listen to your 
dreams.
_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-usability



_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-usability


[prev in list] [next in list] [prev in thread] [next in thread]