nartreb

Joined: 03 Apr 2004 Posts: 1360
[ Profile | PM ] |
Posted: Fri Mar 03, 2006 3:13 pm GMT |
|
|
One disadvantage of list proliferation is that the top-left-corner gets easily confused.
Sometimes, you see "White Mountains > Presidential Range > Mt Washington", and sometimes you just see "US State High Points > Mt Washington." (You can see the other parents by clicking the little "+" sign by "US High Points", but you lose info about nesting relationships).
Similarly, I think the order of lists on the left tab is by maximum elevation, so a small peak in the Whites has all the Whites listed above the particular range that it's in.
I've taken to adding my own links at the beginning of the Overview section of my mountain pages, so the "real" taxonomy is always obvious.
For lists, as opposed to ranges, I think it would be better to make the list related to the mountains, not a parent. The list page has all the mountains listed on it, it doesn't need a list of mountains in the left tab. The Mt Washington page really doesn't need a left-hand column listing of all the US state Highpoints, AND all the NE Hundred Highest, AND all the NE 115, AND all the NE Fifty Finest, AND all the NH("White Mountain") 48, AND all the NH County Highpoints, AND Skiable Mountains of the Northeast, AND... It should have a link to each of those lists, and Related Objects seems like the right place for that.
The US State Highpoints list was "grandfathered in" since it existed before anybody started discussing Eastern taxonomy, and later automatically promoted to group-page status. It may be time to demote it. |
|