refactor table of contents
The big change is that we're going to generate the table of contents in the browser with JavaScript manipulating the browser's dom parsing. At the same time we'd like to address most or all of these:
- have ToCs reflect only some headers in inclusions (needs some design)
- stop showing root of relative plus cards in ToC
- keep blank headers out of ToC
- include anchors even if no toc
- make toc work on Related subtabs
There may be others, check:
Related support tickets:Relevant user stories:add one
now starting to think this might be possible to do as chunks. tagging 1.5.3 but just want to have a look.
(would restore old functionality, with an eye toward these other issues)
--Ethan McCutchen.....Fri Feb 18 10:16:39 -0800 2011
The idea I had for getting refactor table of contents working in wagn 1.5+3 would mean moving the handling into lower level rendering, which I'm now realizing would make it hard to have any rendered content view (including content and naked) without the toc.
The takeaway is that we might want to give toc some more talking over.
--Ethan (from make toc work on Related subtabs)
You want to talk about toc?
--John Abbe.....Mon Feb 28 10:13:26 -0800 2011
We'd offer some flexibility if we class ToC links to anchors based on whether they're from the root card of an inclusion.
--John Abbe.....Tue Mar 22 21:43:11 -0700 2011
We've been asked how to display the TOC bullet points as numbers instead of Roman Numerals.
--John Abbe.....Tue Mar 22 21:58:02 -0700 2011
Notes