public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dave Page <[email protected]>
To: Thom Brown <[email protected]>
Cc: Simon Riggs <[email protected]>
Cc: w^3 <[email protected]>
Subject: Re: PostgreSQL website redesign
Date: Mon, 21 Nov 2011 10:29:04 +0000
Message-ID: <CA+OCxozpxeKkETF+BfTXV1L4ApB543vP104JFx6HV_ShC0jqtg@mail.gmail.com> (raw)
In-Reply-To: <CAA-aLv6hR-=U7DPrJ++zXUVOq+2drSZwcPgrVbcm07=TXcYXjw@mail.gmail.com>
References: <CAA-aLv68enSnbGyeVqMPrMLp4UpWUdGmOCsf8TiUka9aPku02g@mail.gmail.com>
	<CA+U5nM+qqMKC9Q2b5_xettEHSf1v5ZvM1xORFZ_kWe10g_7Lrw@mail.gmail.com>
	<CAA-aLv6hR-=U7DPrJ++zXUVOq+2drSZwcPgrVbcm07=TXcYXjw@mail.gmail.com>

On Sun, Nov 20, 2011 at 11:08 AM, Thom Brown <[email protected]> wrote:
> On 19 November 2011 17:12, Simon Riggs <[email protected]> wrote:
>> On Thu, Nov 17, 2011 at 12:10 AM, Thom Brown <[email protected]> wrote:
>>
>>> As you will no doubt be aware, the PostgreSQL website is overdue for a
>>> fresh lick of paint, so we are planning to give it a new look in the
>>> near future.
>>
>> It's not clear to me that redesigning the website will give us
>> anything at all, but it will definitely drain time and focus away from
>> things like writing patches or working out clear and workable designs
>> for new features.
>
> Well we can't abandon one area of the project just because there's
> another area that's considered more important than everything else.
> The community is constantly involved in arranging conferences and PUG
> meetups, infrastructure changes and assisting others with general
> PostgreSQL problems.  And likewise, this is another are of the project
> that not everyone will necessarily be interested in.
>
>> The existing design works just fine in every way, so "we" are not
>> unhappy. In fact the existing site is fairly well tuned with many
>> people's feedback and pixel level arguments now done and dusted.
>
> Well it's 7 years old now.  It could be argued that people will see
> the same PostgreSQL that they saw 7 years ago.  As such, we haven't
> progressed, innovated or become modern in any way.  The current design
> could be seen as PostgreSQL stagnating and been neglected.  Design
> communicates as well as words.  Ours may be saying "nothing new to see
> here".  Of course, changing too often would have an equally negative
> effect, suggesting that we're inconsistent, unstable and can't make up
> our minds.
>
>> We do need some marketing, but redesigning websites without purpose is
>> not marketing.
>>
>> Please state the reasons you think a redesign is worth the effort. And
>> how that is a priority over spending the same time and money on actual
>> marketing, i.e. external contacts, whitepapers, press and such like. I
>> grant that is likely more fun to redesign a website but that doesn't
>> make it worthwhile.
>
> This is probably something -core would like to give a more complete
> answer on since it was their decision.  But my views are as above.

I think your answers above do pretty well hit the nail on the head. We
want to ensure that the all areas of the project visibly progress and
don't stagnate, and updating our web presence is a part of that. We
are also aware that the current website does not meet the needs of
everyone by any stretch of the imagination. In particular, it's quite
unfriendly to new visitors, and gives them little in the way of
guidance to find the information they're likely to need.

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

view thread (23+ 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]
  Subject: Re: PostgreSQL website redesign
  In-Reply-To: <CA+OCxozpxeKkETF+BfTXV1L4ApB543vP104JFx6HV_ShC0jqtg@mail.gmail.com>

* 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