Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id E849F1E34FD7 for ; Wed, 23 Nov 2011 11:28:45 -0400 (AST) Received: from moutng.kundenserver.de ([212.227.17.10]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RTEkf-0000dy-KV for pgsql-www@postgresql.org; Wed, 23 Nov 2011 15:28:46 +0000 Received: from [192.168.1.6] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0Lsupa-1QjqG23sPS-011qqZ; Wed, 23 Nov 2011 16:28:33 +0100 Message-ID: <4ECD111F.3090207@2ndQuadrant.com> Date: Wed, 23 Nov 2011 10:28:31 -0500 From: Greg Smith User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20111110 Icedove/3.0.11 MIME-Version: 1.0 To: pgsql-www@postgresql.org Subject: Re: PostgreSQL website redesign References: <4EC7BD63.4080707@dalibo.info> In-Reply-To: <4EC7BD63.4080707@dalibo.info> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:Mno79oP5NeTPgIN1QprC5LSaAqYSKrw0s6CHIeGHfcF g1nGSrwOPEDcCuuGQPcUrw1sWZc4ph/dhVz437sylk7l+EsobB v8mc61R9Dl8E4dZpgiYN1MsMo4a3q8UB1XpKKiCLAezKWaiwMN wV8KB7Tq2740lwJzxeIKQRLpKEsgCAlRt1iuOw6KKI082OhJ1t aG/x2PzVpDoRQsVPv3uGjqolUrAjW4bQorqG11QiuAnHwXnMnR PAmiUcHVAthkkfZHzHl9VlzHWgDnsK/NPWgP0BU/2utRU8wofi K9UaLLz4lfYCtucK8LS4s3graFratWibn+Rw5k1SgeSDldn1gI 9+bFW+q46JpW6QPkcXI0= X-Archive-Number: 201111/37 X-Sequence-Number: 20313 On 11/19/2011 09:29 AM, damien clochard wrote: > c/ Sorry but I'm not a huge fan of the Postgres Open website :-/ It's > full of HTML and CSS errors everywhere. The meta tags are pretty poor. > Basic files like sitemap.xml or robots.txt are missing. There's no > favicon either.... On what basis is this an "excellent job" ? > The Postgres Open site is built on top of some Django code from another conference, and it turned out to be a nightmare to work with. The primary basis you should judge the designer of that site on is whether the visual look is nice. As far as I know every error you mentioned resulted from a framework issue that they had no control over. All time that had been intended for fixing those sort of things (and far more) was gobbled up just getting the schedule to display, which had nothing to do with the job they were working on. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us