[Haskell-cafe] Re: Haskell.org re-design
gcross at phys.washington.edu
Tue Apr 6 22:09:17 EDT 2010
While I think that (d) is a valid concern, it is also important not to let the perfect be the enemy of the good. If we agree that the proposed web site layout is sufficiently better than the current one and is "good enough" aesthetically, then I think we should go ahead and switch to the new layout and *then* start thinking about how we could make it *completely amazing* like the Ruby web site, because if we demand completely amazing for our *first* try then I fear that all that will happen is that nothing will change because the bar will have been set too high.
On Apr 6, 2010, at 6:25 PM, Jason Dagit wrote:
> On Tue, Apr 6, 2010 at 5:49 PM, Thomas Schilling <nominolo at googlemail.com> wrote:
> Ok, based on both your and Ivan's comments I modified a bit more.
> Making the top columns and the lower columns the same width looks bad,
> but I agree that the large margin between the blurb and the
> Documentation headline was too large.
> After I changed that, however, the Documentation section and the News
> sections did not line up anymore which looked even worse when the news
> section had a different background colour. So instead the background
> colour is used for the quicklinks. Removing any use of a background
> colour would makes things too boring, though.
> I also swapped the heading colour and the title bar colour. So
> headings are now a very dark blue.
> The italic things in the blurb are actually not links (though they
> could be). Without any styling the blurb would look too boring, so
> I'm using the same blue that the title bar uses.
> We were discussing it briefly around the office and some things I recall from that:
> a) There's only so much you can do with square boxes, flat colors, and a single font.
> b) http://www.ruby-lang.org/en/ is probably one of the best looking programming language websites.
> c) the wiki bar at the top has got to go
> d) how do the designs look on mobile devices?
> It looks like you've definitely tackled (c), so that's great. It seems like maybe we can draw on (b) to help address (a).
> I wish I had more concrete suggestions. Keep up the good work!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Haskell-Cafe