PostgreSQL website redesign

From: Thom Brown <thom(at)linux(dot)com>
To: "w^3" <pgsql-www(at)postgresql(dot)org>
Subject: PostgreSQL website redesign
Date: 2011-11-17 00:10:42
Message-ID: CAA-aLv68enSnbGyeVqMPrMLp4UpWUdGmOCsf8TiUka9aPku02g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Hi all,

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. The plan is to use some existing community funds to
employ the services of a professional designer who will be able to
produce the new design. Some of the community already have experience
working with the designer in question as they designed the Postgres
Open website (http://postgresopen.org/), and I think you will agree,
they did an excellent job.

With that in mind, we want to establish some design goals. These will include :
- what is the website's target audience?
- how do we wish to be perceived? (e.g. traditional, modern, friendly,
professional etc.)
- what do we hope to achieve with the website design?
- what new opportunities does this present us with?
- what usability problems do we currently have that the redesign could address?

You may have heard it said "there is no spoon". Similarly, there is
no bike shed, so there's no colour to paint it. In other words, the
gritty details (such as layout, colour, font-size, borders etc.)
aren't up for discussion at this stage. Instead, a design committee
(which has already been selected) shall agree on the final design
goals, liaise with the designer to discuss the finer details, and to
ensure our goals are met.

The final design will be licenced under our very own PostgreSQL Licence.

So with that, I'd like to open this topic for discussion.

Thanks

Thom

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Thom Brown 2011-11-19 14:24:38 Re: PostgreSQL website redesign
Previous Message Robert Haas 2011-11-07 19:10:07 Re: Fwd: 1 Pgtap-users moderator request(s) waiting