From: "Sverre Rabbelier" <alturin@gmail.com>
To: "Wincent Colaiuta" <win@wincent.com>
Cc: Dill <sarpulhu@gmail.com>, "Git Mailing List" <git@vger.kernel.org>
Subject: Re: RFC: Website redesign
Date: Mon, 14 Apr 2008 20:29:00 +0200 [thread overview]
Message-ID: <bd6139dc0804141129h25c829e2i320f227594763d71@mail.gmail.com> (raw)
In-Reply-To: <96F7571C-1D9D-4F0A-99F1-A2307DAB0374@wincent.com>
On Mon, Apr 14, 2008 at 7:03 PM, Wincent Colaiuta <win@wincent.com> wrote:
> With all due respect, all of the designs you've posted look like _weblog_
> templates, and that doesn't seem appropriate to me for a software website.
> One of the things I most dislike about the weblog format is the fixed-width
> centre column and the large tracks of wasted space down the sides; although
> the official site is certainly "bare bones" (some would say "ugly") at the
> moment, at least the information density is high and there isn't any wasted
> space.
That is most probably due to that the templates googlepages offer are
mostly aimed at such weblogs. I think the suggestions are not just for
layout but also for color (which is very important, to me at least,
when deciding whether a webpage is 'damn ugly' or 'quite nice').
Also I think that the main page should not contain more information
than fits in one 'screen'. That is, there should be no scrollbar on
'sensible' (say, above 1024*768) resolutions. To me a site feels
'overfull' if it's mainpage has a scrolbarr. Instead, I think the
mainpage should be a portal to other parts of the website, instead
of... well... everything-crammed-on-one-page-so that.... so that what?
What purpose does it serve to put all information, ungrouped, not easy
to find, and as such chaotic, on one page?
Anyway... </rant>
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2008-04-14 18:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 5:37 RFC: Website redesign Dill
2008-04-14 13:56 ` Jonas Fonseca
2008-04-14 15:38 ` Dill
2008-04-14 17:03 ` Wincent Colaiuta
2008-04-14 18:29 ` Sverre Rabbelier [this message]
2008-04-14 20:39 ` Anand Kumria
2008-04-14 21:33 ` Dmitry Potapov
2008-04-15 3:24 ` Anand Kumria
2008-04-15 5:05 ` Dill
2008-04-15 6:48 ` Dill
2008-04-15 7:59 ` Jakub Narebski
2008-04-15 11:57 ` Petr Baudis
2008-04-15 16:20 ` Git Homepge Update Petr Baudis
2008-04-15 17:57 ` Steve Hoelzer
2008-04-16 1:36 ` Jakub Narebski
2008-04-15 7:08 ` RFC: Website redesign Dmitry Potapov
2008-04-15 7:53 ` Jakub Narebski
2008-04-15 14:33 ` Petr Baudis
2008-04-15 11:54 ` Petr Baudis
2008-04-15 18:04 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bd6139dc0804141129h25c829e2i320f227594763d71@mail.gmail.com \
--to=alturin@gmail.com \
--cc=git@vger.kernel.org \
--cc=sarpulhu@gmail.com \
--cc=sverre@rabbelier.nl \
--cc=win@wincent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).