Stas Bekman wrote: > > i don't understand you here stas. do you mean the actual > > relevant header won't scale well? > > or did you mean the breadcrumb/path idea won't scale well. > > both scale well here. > > the breadcrumb/path idea. By 'scaling' I meant the length of the titles. > The possible cons are: > > 1. very long concatenation of many long titles > 2. pages with short sections where this overhead will be significant and > instead of improving the experience, will make it worse. > > You should to test with these 2 cases and you will see better what I mean.
i understand you now. yes, that would probably not look too good with very long concatenations where there's a small section at the same time. > > If we do agree to proceed with this idea nevertheless, I suggest to > improve the user experience by showing the actual nesting, similar to > the old split version of the guide, e.g. see: > http://thingy.kcilink.com/modperlguide/install/Callback_Hooks.html > Click on the sub-menus to see how the nesting change, also note that > childred and listed as well, if you click on parents. > I'm afraid this can be a problem with 2. but solves 1. agreed. > yes. There are two ways people read the guide: > > 1. sequencial - read from the top to the bottom (no need for the nav > help here) > 2. selective - when learning a certain short topic or solving a problem: > usually getting to the spot via the search or the TOC (no problem here > as well) > > So I'm afraid this extra info will be too much of a noise. ok > I wish tooltips had a better utilization, so this extra info could be > displayed on demand. We could use DHTML for that, but I'm afraid we will > release the new site in Apr, 2003 then. IMHO i know DHTML pretty well, but we dont want js introduced either do we. what is tooltips? ./allan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
