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

[Eric Laffoon]

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

On Tuesday 02 March 2004 9:21 pm, 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?
>
A trick? You mean ask Monday at 2 AM and commit at 3 AM? ;-)
>
> Home
> Features
> ...Quanta Can...  (Was its own heading before)
If I might comment, if there is a better phrasing that doesn't sound like "The 
Little Engine That Could" I'd support it. Maybe "Quanta in Action" because it 
also denotes action as in something happening as opposed to the tendency to 
relate "an" to "could" which is less dynamic.

This also could be a rather involved section because it could have subsections 
for PHP, XML, projects, etc...

> ...Comparison chart
This is as we discussed comparing to professional tools or would we prefer 
just a feature chart? Is Chris doing his wizardry here?

> Screen Shots
> Quanta News  (Was Quanta in the news)
Do we want to make this kdewebdev news? Do we want to subsection it for "news 
for this app" or "news for the module"?
> Testimonials
> Get Quanta!
> ...Requirements
> ...Installing
> ...Donate to Quanta
I don't see how this goes here. I think it goes in a "Get involved" section, 
which may be a good phrasing, along with "sponsor development", "join the 
programmers" and scripting, templates, site, etc...
> Support
> FAQ
> User Support Area
> Developer Support Area  (Link to developer.kdewebdev)

Actually we might want to look at the kde.org pages for a bit just to see what 
fundamental menuing elements we could commonly apply. I want the site to be a 
stand out, but I think we should be "not emulating" where we have good 
reasons and emulating where we don't have any particular reason not to. I 
don't know how much we would toss aside but it seems logical doesn't it?

I will say I think that some KDE sites are a little too cluttered menu wise, 
but we should attempt some degree of consistency.

Eric
>
> Going once, going twice...
>
> Bill
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFARXcLSiV5TqRTAEsRAv/qAJ9R5n1iU6BRbPiRr68C91qehFxTswCcD39b
oVm4O/Lo6QoeAQOAXeUlJSQ=
=nL/E
-----END PGP SIGNATURE-----