public inbox for [email protected]
help / color / mirror / Atom feedFrom: Robert Treat <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: [email protected]
Cc: Omar Kilani <[email protected]>
Cc: [email protected]
Subject: Re: [pgsql-advocacy] Alternate PostgreSQL.org Design
Date: 12 Nov 2004 14:40:47 -0500
Message-ID: <1100288448.5508.104.camel@camel> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
It is not outside the realm of possibility, but I'm not optimistic as
there are still a number of TODO items we need to finish up...
Of course if folks feel this is something that needs to happen we could
possibly toss some things out, but there has been some reservations
about launching a new site at the same time as a major release.
Robert Treat
On Fri, 2004-11-12 at 13:00, Bruce Momjian wrote:
>
> Is the new website going to be rolled out in time for the 8.0 release,
> which could be in the next few weeks?
>
> ---------------------------------------------------------------------------
>
> Josh Berkus wrote:
> > Omar,
> >
> > > We believe that it is clean, professional and simple. And it makes the
> > > release of 8.0 actually... exciting. :)
> >
> > I like the organization of content. I find the graphics a bit HP-ish, but
> > that's work-on-able. It's certainly less crowded than our current design,
> > and you've done a nice job making things a lot more intuitively findable.
> >
> > > It is a *drop-in* replacement for the current pgweb design. No
> > > additional work is required to retrofit the current wwwdevel design.
> > > It's already done!
> >
> > Keen, this makes a discussion about it more useful. Thank you for going the
> > extra mile and dealing with some of the drill-down pages; it really gives us
> > an idea of how you envision the site being organized.
> >
> > > We've gone through a bit of the current content and fixed it up with
> > > proper headings and so forth. But we believe that the content needs to
> > > be restructured to fit within navigational guide lines.
> >
> > No arguments here ... see the collected archives of www.
> >
> > > * The overuse of subdomains is a major pain. Each subdomain uses a
> > > completely different layout and design. X.postgresql.org should be under
> > > the relevant section on the main site. Advocacy should move under
> > > /about/. Developers has it's own section. Tech docs should move under
> > > Documentation, etc.
> >
> > We've had a consolidation plan for over a year. Really, you should engage
> > more of a dialoge in the WWW list and talk to us about what's already
> > planned.
> >
> > Techdocs is one hitch; article generation/editing needs to be handled by some
> > kind of online text editor. Otherwise we limit contributors to the current
> > WWW team and nothing gets written.
> >
> > Of course, it would also be a really good idea to have any part of the site
> > requiring significant maintenance .... such as the list of GUIs, the
> > contributor list, or consulting companies ... to be editable via simple text
> > editor or html form instead of via raw XHTML. This would allow the general
> > pool of documentation volunteers -- which is 5x large than WWW volunteers --
> > to maintain these areas.
> >
> > --
> > Josh Berkus
> > Aglio Database Solutions
> > San Francisco
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 3: if posting/reading through Usenet, please send an appropriate
> > subscribe-nomail command to [email protected] so that your
> > message can get through to the mailing list cleanly
> >
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> [email protected] | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square, Pennsylvania 19073
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
view thread (59+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: [pgsql-advocacy] Alternate PostgreSQL.org Design
In-Reply-To: <1100288448.5508.104.camel@camel>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox