launchpad-dev team mailing list archive

[Matthew Paul Thomas <mpt@xxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Nelson wrote on 14/10/09 11:24:
>
> Matthew Paul Thomas wrote:
>>
>> Michael Nelson wrote on 07/10/09 13:21:
>>> ...
>>> Yet another breadcrumb/heading question :) Basically, which is
>>> better:
>>> Option 1: low redundancy:
>>> H1: Define upstream link
>>> BC: Ubuntu >> 9.04 >> “mozilla-firefox” source package >> Define
>>> upstream link
>>> or
>>> Option 2: redundancy and possibly google-fu (h1 being weighted?)
>>
>> Google-fu is not an issue here: Google doesn't have permission to see
>> this page.
>
> Sorry, maybe I wasn't clear - the above is just an example for a
> general question regarding all our h1+breadcrumbs.

Yes, and it's a general exception too: Where a page requires permission
to access, you can concentrate on optimizing its <title> and headings
entirely for humans, not for search engines.

>...
>> In your next user testing, I suggest testing a branch that displays
>> realistic-looking but completely wrong breadcrumbs, e.g. "Ubuntu »
>> Hoary » Translations » trunk » Latest bugs". With their current style
>> and placement, I predict most people wouldn't even notice.
>
> Sure - the placement and style is out of the scope of my question (I
> assume a lot of discussion by designers went into their
> placement/style). But I'm not sure whether you're implying that the h1
> heading is a more important source of context either way? (ie.
> something closer to option 2).

I was being slightly unfair -- I think people would ignore the
breadcrumbs almost regardless of their style and placement. More
effective would be reducing the number of breadcrumb elements and the
length of each element, but that would still mean the <h1> needs to
shoulder more of the burden of orienting you.

Cheers
- --
Matthew Paul Thomas
http://mpt.net.nz/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrWG5UACgkQ6PUxNfU6ecq1jgCbB31mn1zKWfr+G1X1vM+m7FLU
j3UAoJsvhxWypTFe8OMTEp1wEz4S0Nr5
=t3jU
-----END PGP SIGNATURE-----