>> I really, really don't want to put any links in the left-nav proper to
>> destinations that don't carry that menu. I cannot stress this enough. A
>> site visitor should reasonably expect that the menu that helps him or her
>> get around the site also keeps them "on the (branded) site". And as I've
>> mentioned in other discussions, HACKING is far too lengthy a document to be
>> considered "part of the website", in much the same way that "Version Control
>> with Subversion" is.
> My hunch is that HACKING probably ought to be split up rather than
> kept as a monolithic big guide.
I've already lost one battle for splitting up HACKING, so you can wage this
one yourself, buddy. :-)
> Oh, BTW, I know you're going to hate me, but ASF policy is that every
> project site has a reasonably-prominent link to:
Right. Of course it does.
It's becoming more clear to me every moment that my personal design
philosophies don't gel with apparent community needs and inherited policies.
That's fine -- on my list of Major Life Problems, this doesn't even rate a
footnote. If I'm honest with myself (which folks really should be), I was
far more disgusted by the actual content (it's duplication, it's redundancy,
and it's browbeating of casual visitors) of our previous website than about
its navigation menu. So if the worst thing that happens is that we have a
bunch of "offsite" links in our menu, I'm still basically happy.
Edit away, Justin!
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2010-02-03 22:16:33 CET