From: Junio C Hamano <gitster@pobox.com>
To: Petr Baudis <pasky@suse.cz>
Cc: Dill <sarpulhu@gmail.com>, git@vger.kernel.org
Subject: Re: RFC: Website redesign
Date: Tue, 15 Apr 2008 11:04:56 -0700 [thread overview]
Message-ID: <7vtzi35707.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080415115431.GA26302@machine.or.cz> (Petr Baudis's message of "Tue, 15 Apr 2008 13:54:31 +0200")
Petr Baudis <pasky@suse.cz> writes:
> I appreciate the effort, but frankly, I simply personally like the
> current layout much more - the design certainly has quirks, but I don't
> really find it bad; I also think that the current amount of content does
> not justify splitting to multiple pages. The newly proposed version
> looks to me just as barebone graphically as the old one, with the same
> level of navigability but wasting screen estate and requiring more
> clicks to get where you need.
>
> That said, this can (and quite probably does) merely mean that I simply
> have no taste at all and should be kept away from any kind of web
> design! :-) So, I do not want to inhibit progress at all, but before
> considering to adopt the new design, I would prefer to see wider
> feedback from the core members of the community to convince me that I'm
> wrong.
I always wish that any proposal for change is countered by silent
satisfied customers expressing why the current one is good, and this is a
perfect opportunity for me to do so as I am just a satisfied customer of
git.or.cz, who is not involved in the building side at all.
If I recall correctly, the old old site was split like how the sarpulhu
sample page shows, a sketchy top page with links to other pages. It is
tempting to build a sparse scaffolding in the expectation that each page
will be filled with rich contents later, and the fear of having too many
things in one page drives people to make the initial scaffolding too
sparse. But as you say, the current "single page that is not too long
describes all the necessary things and points people at outside resources"
format is much nicer.
I happen to also like one aspect of visual behaviour of git.or.cz better
than the sarpulhu sample page. The former widens as I resize my browser
window, the latter doesn't.
prev parent reply other threads:[~2008-04-15 18:06 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
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 [this message]
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=7vtzi35707.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=sarpulhu@gmail.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).