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

[Bill Chmura]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 06 March 2004 01:47 am, Eric Laffoon wrote:
> On Friday 05 March 2004 9:15 pm, Bill Chmura wrote:
> > Okay here it is again...
> >
> > Without being side tracked by the underlying structure, or how we would
> > program things, or anything like that... is this good?  At least good for
> > now?  It will not be set in stone after all...  We can move things as it
> > goes along, and that is to be expected in any web project.
> >
> > key:  ... indicates a subsection
> >
> >
> > Home
> > Features
> > ...Quanta Can...  (Was its own heading before)
>
> I still prefer a more dynamic phrasing. For example: Quanta in Action,
> Using Quanta, Working with Quanta, even Quanta Capabilities. I'd stop short
> of "Ruling the Universe with Quanta" or "Quanta won't eat your homework"
> ;-)

Okay, I can live with Quanta in action

>
> > ...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)
>
> So the ellipsis prefix indicates this is a menu item on a secondary page
> leading to other pages. Correct? This is a 10 item main menu. I have
> several elements of confusion and concern, so I'll start with the easy one,
> concern. I think having the donate menu in "Get Quanta" is an interesting
> idea, but I don't think it's really ideal as a primary location.
> Secondarily it's great. We are also missing something I think is essential,
> helping the project...

Donate to Quanta can be moved.  I am also thinking that the Get Quanta should 
link into a download area off the user-section.  That way its only maintained 
in one place (cvs instructions, install notes, what not)...

> And what is the different between "Support" and 
> "User Support Area"? I believe the following menus need to be in place. I'm
> open to discussion but I believe the above is incomplete.

User support area is where all the actual support for people running day to 
day with Quanta is.  Once your a Quanta user you will most likely be spending 
all your time in there.  This option dumps you into the whole dynamic user 
support world...

Support is a page discussing all the support that is available to Quanta 
people.. mailing lists, archives, forums, resource repositories, etc... Its 
not a path into these (they are in the user support) but instead to give a 
prospective user the warm fuzzy feeling that there is 1000 of helpful people 
out there wanting to help them if they pick Quanta.  Even though its part of 
KDE, I still would like to convey this to the users.  Maybe it should be 
"Available support", "It's supported!" or "Support options" - the latter 
sounds pricey though.

>
> User Support
> ... Mailing List Hot Topics (or something on the hot fed)
> ... Search Mailing list (Alternately may replace above)
> ... Forums
> ... How to Get help (look at the help menu and use bugs.kde.org)

> Supporting Quanta
> ... Contributing Resources (scripts, templates, etc...)
> ... Become a Developer
> ... Join Quanta Support (forum admin, vetting scripts, etc...)
> ... Become a Sponsor
> ... Make a Donation

Supporting Quanta stuff would go in the user area... since then they are 
actually a Quanta user and more inclined probably to help out.  The first 
level is to get them to a new user.  This leaves each part of the site open 
to focus on one apect of dealing with a visitor

> Resource Repository
> ... Contribute Resources
> ... Search and Retrieve Resources
>
> The resources section could conceivably be in the support sections but then
> that would break them up. So a separate top level menu seems logical. We
> need to seriously promote this to flesh out what Quanta offers.

User area

> Now on to what is confusing. We will have separate subdomains for each app.
> Technically this may not be difficult and it doesn't have to have a lot to
> do with layout... but it also does. I am not clear what menu I'm looking at
> above but I would guess it is for quanta.kdewebdev.org. It's totally Quanta
> centric. So that means we still have the main menu as well as the other
> subdomains. However common everything is that is what subdomains gets
> you... a miniature domain of your own.
>

I knew this would cause confusion, so one of my first emails out set up the 
names for each site.  KDEWEBDEV refers to ...   Quanta public site refers 
to...  

The thought is to have it approached that they are separate sites to a 
degree... you should be able to move up and down the stack (from KDEWEBDEV to 
Quanta Public and back), but all the menus on KDEWEBDEV will not filter down 
to Quanta Public.

> My impression is that we can develop some consistency of look across them
> from the first but we are still working on getting the details for it. So
> I'm confused. Wouldn't a consistant approach be to...?
> 1) layout kdewebdev.org menus
> 2) layout quanta.kdewebdev.org menus
> 3) set up exceptions for the other application subdomains
> 4) consider if we will do the same visual level for developer section

Yes, I have the navigation proposal out for the main KDEWEBDEV and Quanta 
Public sites at the same time.   I thought the KDEWEBDEV would be an easy hit 
since it was basically directing.  Both postings started a whole chain of 
unrelated discussion on everything except the information architecture which 
I even had trouble sorting through (all had the same subject line).

> I would also like to request your thoughts on the developer section. If you
> pretty much want to let the developers run with it then I'd like to request
> a volunteer to help me begin mapping the procedures and data for it. I have
> much of it in mind and you seem to have other things under control. 
> With 
> someone helping I could reduce my load here.
> Eric
> _______________________________________________
> kdewebdev-site mailing list
> kdewebdev-site at mail.kdewebdev.org
> http://mail.kdewebdev.org/mailman/listinfo/kdewebdev-site

- -- 

Bill Chmura
bill at kdewebdev.org
KdeWebDev/Quanta site development project
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFASXqUEEA64RcvcRERAr0vAKCVXkToNg05lSBq3hz2WC1jACPhXwCgqJUZ
qBQWq9qWtLk2CXNc4MUfEAY=
=+9CS
-----END PGP SIGNATURE-----