On Tue, Feb 3, 2015 at 10:43 AM, Dave Page <dpage@pgadmin.org> wrote:
Hi On Tue, Feb 3, 2015 at 9:36 AM, Gevik Babakhani <gevik@postgresql.nl> wrote: > Hi all, > > At FOSDEM we had a discussion regarding redesigning postgresql.org to make > it modern and responsive. I might have had one drink too many (water that > is) and I kind of volunteered to give a shot at it. The following items we > discussed briefly: > > [1] Color and theme of the website should remain largely the same blue(ish) > [2] JavaScript can be used but the website must work 100% should someone > have JavaScript disabled. This one is particularly hard since many “nice” > things in web development, like client side validation and such rely on > JavaScript.
I think you misunderstood that a little. If Javascript is disabled, the site should gracefully fall back to a mode where the content is still readable and usable, but not necessarily as nicely.
+1.
> [3] The website should be responsive, and adaptive when needed (for this one > we need JavaScript for sure) > [4] We discussed the possibility of a CMS functionality briefly.
Meh. Maybe we could use Django-CMS, but I can't get that excited about it.
I'd really rather not unless we really have to. Most of the "interesting" parts of the site are not part of that anyway, they're not driven from the "cms side". Dealing with the little bit of static info we have now as, well, static info, is more of a feature than a bug IMO. And it's definitely something *different* from fixing the layout, so if we do want to change it, it should be done as a separate project from this.
> [5] We discussed the usage of web-fonts and supporting Internet Explorer as > of version 9 > [6] We did not discuss the backend!!
We do not want to change the backend from Django.
Yeah, we did not discuss that for a reason - backend != design. Again, if we do want to change backend at some point, that is a completely separate project from changing the design, and should be treated as such. And right now, we definitely don't want to rewrite the backend code *again' - what we have now works, and is a lot more modern than the current *design* :)
