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

[Eric Laffoon]

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

On Tuesday 02 March 2004 10:34 pm, Bill Chmura wrote:
> On Wednesday 03 March 2004 01:11 am, Eric Laffoon wrote:
> > 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? ;-)
>
> What's with the entire hour between?  Someone could actually read email in
> that great big gap!

Time to fall asleep drooling on the keyboard? ;-)
>
> > > 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.
>
> I am up for suggestions... I was thinking the subsections could be titled:
> Quanta can help with your project management, Quanta can work with PHP,
> etc, etc...  I love the concept, but I am not married to the wording...

I love the concept too, and I would be willing to hear other ideas. My 
marketing side says "strong words that connote action". And if we could make 
the cursor change from a 98 lb weakling with buck teeth to a Mr Olympia 
rocket scientist when it passes over the link, maybe change the background 
from Rosanne Barr in front of a Volkswagon to several Hawaiian Tropic models 
in front of a Ferarri that's good too. ;-)
>
> > 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?
>
> Both

I guess that's both as in (A !B) && C ;-)
>
> > > 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"?
>
> We are heavy with PHP talent on the team.  I am envisioning a news
> management program that will be able to handle the news for all the
> sections.  For example, anyone authorized to do so, can create a news item
> and set it to a specific project and also if its big news.  News pages can
> be generated from the news based on criteria for any given page:
>
> So in the Quanta development section - it can display Quanta development
> items
>
> In the main Quanta section - Quanta news
>
> In the main KDEWEBDEV page, all news flagged as being that important would
> be listed.
>
> Thats it in a nutshell... I've not done much more thinking than that - but
> the concept is there... the levels and stuff like that need to be worked
> out and all.   Also it could be used for an rss feed generator.

I like it!
>
> > > 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...
>
> My thought was that the user would be at a stage where they were interested
> in Quanta and it would be a good time to put a bug in their ear...   We can
> also have it in other sections.  That was my thought.

That's my kind of schlocky design. ;-)
>
> > > 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 don't see the point to following the KDE site.  We are not going to be
> matching a look and feel (as far as I know), and I don't think that people
> are going to be that used to the KDE site that when they come here they are
> going to be confused.

Okay... But there might be some inspiration there.

Eric
>
> > 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
> >
> > _______________________________________________
> > kdewebdev-site mailing list
> > kdewebdev-site at mail.kdewebdev.org
> > http://mail.kdewebdev.org/mailman/listinfo/kdewebdev-site
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFARYNOSiV5TqRTAEsRAoLXAJ41wFA07WHN2DgC/p4M4ueTC/YvSACeLNUs
K0pUOvumaZQFb4cyO/L7EKw=
=Vkm5
-----END PGP SIGNATURE-----