[kdewebdev-site] Quanta Public Site Structure < final ?

Tue Mar 16 21:25:30 EST 2004

I think part of the problem is that you are occupied with other things, and 
tend to miss key emails that break out information.  This probably is what is 
leading you into confusion.

> 1) We will be working with subdomains. This means that we have essentially
> a whole next tier of application front pages like quanta.kdewebdev.org.

Yes, right

> This is *not* inconsequential for several reasons.
> 1A) We have a standard format second "home page" menu to work on

We are discussing the second level page (ie Quanta public site)

> 1B) We are addressing the central domain page as if it is largely the
> quanta.kdewebdev.org page but it's not... for instance where are the other
> applications? Is this actually the quanta.kdewebdev.org page or is it
> really the kdewebdev.org page?

This is the quanta.kdewebdev.org page... the kdewebdev.org page is much 
simpler and was discussed in other emails 

> 1C) The only way to deal with all of this with any coherent visualization
> is to complete a list of menus for kdewebdev.org and one subdomain which
> should be Quanta. Other subdomains should copy all or part of the Quanta 
> design. 

This was done in two different e-mails

> 2) The things that we believe are important need to be top level 
> which means that we need to revise structure to condense based on priority.

I would agree

> 3) The second level menus as I have asked for them are still not clarified.

What?  I clarified all the comments you posted I noticed.

> As we won't likely be using Javascript on the site these have to actually
> be pages and this is why I asked for the information to be organized by
> single depth groupings. The reason is that a second level page may contain
> the information listed in headings or it may contain information central to
> the concept along with several menu items of it's own or links in the text.
> Because of all of these things I believe the problems we are having start
> with the layout not being specified in a clear enough outline. This really
> bugs me because now I guess I need to do it...
>
> [kdewebdev.org]
> Home (with short description and News)
> Applications (link to page with brief descriptions, links and app menu)
> ...Quanta
> ...Kommander
> ...KFileReplace
> ...KXSL Dbg
> ...KImageMapEditor
> ...Kallery
> Screen Shots (selected 2-4 images from each grouped)
> Testimonials
> Download Area
> ...Requirements
> ...Installing
> ...Donate to Quanta
> User Support Area (description and menu)
> ...Forum
> ...Mailing Lists
> ...Hot topics
> ...FAQs
> ...Resources (downloadable enhancements)
> ...Contact
> Help the Project
> ...Contribute Resources (upload files)
> ...Join the Developers
> ...Sponsoring Developers (information about how we sponsor developers)
> ...Become a sponsor
> ...Make a donation
> Developer Support Area (developer.kdewebdev.org)

> [quanta.kdewebdev.org]
> kdewebdev.org (in some way this link needs to be there)
> Home (with short description and News)
> Features
> ...Quanta in Action
> ...Comparison chart
> ...Support
> Screen Shots
> Testimonials
> Get Quanta!
> ...Requirements
> ...Installing
> ...Extras
> ...Donate to Quanta
> User Support Area (link to main)
> Help Quanta (link to main)
> Developer Support Area (link to main)
> FAQ (application specific - can be gathered in main by app)

> This leaves 8 items on the main page and 9 (10 really) on the Quanta page.
> I almost left of the developer link on the menu as people are probably
> going to know about the developer domain and it certainly could be covered
> in helping out. I left the FAQ on the Quanta page as a concession to ease.
> The only shortcoming here is that it is two clicks from the main page to
> the application pages (unless we want to use a combo box menu) ;-) however
> people can just as easily be directed to quanta.kdewebdev.org so in reality
> it's not much of an issue.
>
> Feel free to munch this up and toss it around. A little spirited debate
> never hurt... or we can sign off on it and get to work. ;-) What a concept.
> One thing I think we will have to remember, same as the discussion of top
> level menus in Quanta... This is a complex application and the only way to
> make things work is organize the vast feature set in an intuitive way so
> that it is still highly usable. I think the same will go for the site.
> Usability is for your target audience and web developers are supposed to be
> slightly more sophisticated than aunt Betty with her first computer so the
> key will have to be good judgement and intelligent compromise between
> ideals and essentials.
>
> Eric

> > > Cheers,
> > >
> > > Américo
> > >
> > > ----- Original Message -----
> > > From: "Chris Hornbaker" <chrishornbaker at earthlink.net>
> > > To: <kdewebdev-site at mail.kdewebdev.org>
> > > Sent: Tuesday, March 16, 2004 11:59 AM
> > > Subject: Re: [kdewebdev-site] Quanta Public Site Structure < final ?
> > >
> > > > On Wednesday 03 March 2004 05:21, Bill Chmura wrote:
> > > > > Okay, to keep us on track and moving in a direction...  (any
> > >
> > > direction)...
> > >
> > > > > I've rechecked through... and while we had a lot of good
> > > > > discussions on this and that, not much has changed.
> > > > >
> > > > > So I put forth that this is a good navigation structure to start
> > > > > with
> > >
> > > for
> > >
> > > > > the Quanta site...  A trick I have learned in corporate life is to
> > > > > ask
> > >
> > > if
> > >
> > > > > anyone objects instead of asking for approval.  Approval takes
> > > > > effort...
> > >
> > > If
> > >
> > > > > no one answers it means it must be okay right?
> > > > >
> > > > >
> > > > > Home
> > > > > Features
> > > > > ...Quanta Can...  (Was its own heading before)
> > > > > ...Comparison chart
> > > > > Screen Shots
> > > > > Quanta News  (Was Quanta in the news)
> > > > > Testimonials
> > > > > Get Quanta!
> > > > > ...Requirements
> > > > > ...Installing
> > > > > ...Donate to Quanta
> > > > > Support
> > > > > FAQ
> > > > > User Support Area
> > > > > Developer Support Area  (Link to developer.kdewebdev)
> > > >
> > > > What's the difference between Support and User Support Area?
> > > >
> > > > --
> > > > Christopher Hornbaker
> > > > Jabber ID: Jilks at jabber.org     Email: chrishornbaker at earthlink.net
> > > > Join the Free State Project!    http://www.freestateproject.org
> > > >    "Liberty in Our Lifetime"
> > > > Was I helpful? Let me know! http://svcs.affero.net/rm.php?r=Jilks
> > > > _______________________________________________
> > > > kdewebdev-site mailing list
> > > > kdewebdev-site at mail.kdewebdev.org
> > > > http://mail.kdewebdev.org/mailman/listinfo/kdewebdev-site
> > > >
> > > > Esta mensagem foi verificada pelo E-mail Protegido Terra.
> > > > Scan engine: VirusScan / Atualizado em 15/03/2004 / Versão: 1.4.1
> > > > Proteja o seu e-mail Terra: http://www.emailprotegido.terra.com.br/
> > >
> > > _______________________________________________
> > > kdewebdev-site mailing list
> > > kdewebdev-site at mail.kdewebdev.org
> > > http://mail.kdewebdev.org/mailman/listinfo/kdewebdev-site
>
> _______________________________________________
> kdewebdev-site mailing list
> kdewebdev-site at mail.kdewebdev.org
> http://mail.kdewebdev.org/mailman/listinfo/kdewebdev-site

- -- 

Bill Chmura
Director of Internet Technology
Explosivo ITG
Wolcott, CT

p: 888.560.YWEB (9932)
e: bill at Explosivo.com
w. http://www.explosivo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAV7caEEA64RcvcRERAqyQAJ4onMi/kXCAkewjcy8aakGMlwyzxQCfanoN
AaxLHEPnexc8ElC1G7ZkOqI=
=BOkk
-----END PGP SIGNATURE-----