From: Andrew Sayers <andrew-git@pileofstuff.org>
To: Scott Chacon <schacon@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: git-scm.com refresh
Date: Sat, 05 May 2012 10:14:45 +0100 [thread overview]
Message-ID: <4FA4EF85.2060104@pileofstuff.org> (raw)
In-Reply-To: <CAP2yMaJy=1c3b4F72h6jL_454+0ydEQNXYiC6E-ZeQQgE0PcVA@mail.gmail.com>
I had a poke round the site looking for trouble - here's what I found:
I'm using Linux, but for some reason the front page offers me downloads
for Mac. When I click on "Mac GUIs", I am taken to a sensible URL for
Macs[1] but the button at the top says "Only show GUIs for my own OS
(Windows)". I'm not sure how the detection works, but I have Javascript
disabled and the following user agent string:
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.11 (KHTML, like Gecko)
Chrome/17.0.963.56 Safari/535.11
Automatically guessing the user's OS is a good way of reducing interface
complexity, but for example the Firefox homepage[2] shows Windows, Linux
and Mac OS buttons if it can't guess. This probably also helps Google
index their site, as GoogleBot can follow links to all the OS-specific
download pages.
The "about" section doesn't work in JS-disabled browsers - I always see
the "branching and merging" page no matter what I click on. Again, this
means GoogleBot most likely won't index the other pages.
Not a bug, but a little tip - while investigating the issue on the
"about" page, I noticed that all the links had href="#". You might want
to consider using href="#some-unique-identifier" so when you click round
the site with a JS-enabled browser and notice a "#" in the URL, you can
identify which click handler(s) failed.
Probably another non-JS browser issue, although not one that will bother
Google: the "book" section in the documentation page[3] has the first
"book cover" block protruding way into the left column, with all its
text mirrored.
Not a bug but a feature request: in the actual book pages, could you put
the prev/next links at the top as well as the bottom? If I read through
the book, then come back a few weeks later looking for one of the pages,
it's much quicker to click through links at the top without needing to
scroll or move the mouse.
These bugs are relatively minor - the new site looks great overall.
- Andrew
[1] http://git-scm.com/download/gui/mac
[2] http://www.mozilla.org/en-US/firefox/new/
[3] http://git-scm.com/documentation
next prev parent reply other threads:[~2012-05-05 9:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 23:29 git-scm.com refresh Scott Chacon
2012-05-05 0:26 ` Jakub Narebski
2012-05-05 22:24 ` Scott Chacon
2012-05-05 23:20 ` Josh Juran
2012-05-05 1:31 ` Junio C Hamano
2012-05-05 16:47 ` Felipe Contreras
2012-05-05 22:38 ` Scott Chacon
2012-05-06 1:39 ` Junio C Hamano
2012-05-06 2:31 ` Felipe Contreras
2012-05-06 3:51 ` Scott Chacon
2012-05-06 8:33 ` Philip Oakley
2012-05-07 17:06 ` Junio C Hamano
2012-05-08 16:51 ` Junio C Hamano
2012-05-08 17:46 ` Andreas Schwab
2012-05-08 18:00 ` Junio C Hamano
2012-05-05 9:14 ` Andrew Sayers [this message]
2012-05-05 14:01 ` Felipe Contreras
2012-05-05 14:36 ` Philip Oakley
2012-05-06 0:08 ` Neal Kreitzinger
2012-05-06 5:10 ` Neal Kreitzinger
2012-05-06 11:04 ` Matthieu Moy
2012-05-06 13:36 ` Scott Chacon
2012-05-07 4:18 ` Christian Couder
2012-05-07 17:08 ` Ævar Arnfjörð Bjarmason
2012-05-07 15:08 ` A Large Angry SCM
2012-05-07 21:04 ` Matthieu Moy
2012-05-09 22:13 ` Heiko Voigt
2012-05-08 12:29 ` Antonio Ospite
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=4FA4EF85.2060104@pileofstuff.org \
--to=andrew-git@pileofstuff.org \
--cc=git@vger.kernel.org \
--cc=schacon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.