20121 2012-11-28 16:00:08 +0000 See Also context hints 2012-11-28 16:06:20 +0000 1 1 1 Unclassified webplatform.org skin unspecified PC All NEW P2 normal --- 1 letmespellitoutforyou schepers public-webplatform-bugs oldest_to_newest 79001 0 letmespellitoutforyou 2012-11-28 16:00:08 +0000 See apis/css-regions for example. Undifferentiated links give little idea of context. Ideally prefix w/icons giving feedback about what sort of info is at the destination: a[href=~"/dom"]::before { content: url(icon_dom.png) } a[href=~"/apis"]::before { content: url(icon_api.png) } a[href=~"/css/properties"]::before { content: url(icon_cssprop.png) } a[href=~"/css/cssom"]::before { content: url(icon_cssom.png) } Perhaps a deeper template rather than skin issue, but see-alsos for API member pages might also benefit by being prefixed with the interface name. In this case, instead of "name", "NamedFlow.name" gives more context. 79003 1 letmespellitoutforyou 2012-11-28 16:06:20 +0000 See-also links displaying "NamedFlow.name property" or "NamedFlow.getContent method" would provide yet more context.