MayLith: This idea is for large pages which, for whatever reason,

  1. you don't want to break up into subpages, or
  2. the time has not yet come to break up into subpages, perhaps because enough detail has not yet accumulated.

Prime example: the FrequentlyAskedQuestions. That page isn't very large yet, but it probably will become so. A huge table of contents, with every question on that page incorporated into the TOC, would be extremely cumbersome.

On the other hand, a sub-TOC under each main heading (Technical issues, Gameplay questions, etc) would be very useful. If you know it's a gameplay question, you could jump to that subheading, and from THERE read a shorter TOC that is specific to that section only, with each entry of the contents being an individual FAQ title, which you could then jump to.

Also, something like this might make specific linking (say, from the forum) easier, not to mention breaking a large page up into subpages at a later date.

And yes, most of this could be done with individual links, but it would be soooo much easier with a macro....

MassimilianoMarangio: You can limit the depth of the ToC with the macro [[TableOfContents(maxdepth)]], e.g.

Contents

  1. Part 1
  2. Part 2
  3. Part 3

Part 1

Part 1.1

Part 1.2

Part 2

Part 2.1

Part 3

This solves one problem, the short ToC of the page.

MayLith: Interesting and cool (I didn't know that!), but I guess we still need deep, limited TOC for the subsections. You could put the regular TOC within each subsection, true, but from my experiments, if you do that, it'll list the full TOC for the whole page, which is again defeating the purpose. :-/

Wiki Suggestions/Wanted macro or method: means of subordinate table of contents (last edited 2004-07-28 12:59:28 by MayLith)