[
https://issues.apache.org/jira/browse/SOLR-10612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017745#comment-16017745
]
ASF subversion and git services commented on SOLR-10612:
--------------------------------------------------------
Commit c42455c89b0446238adbad3548485498d671dd7d in lucene-solr's branch
refs/heads/branch_6_6 from Chris Hostetter
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c42455c ]
SOLR-10612: add jekyll support for page-toclevels, page-tocclass, and a new
{section-toc} macro
(cherry picked from commit 3392a128667f927783199fe3d9f0c6a17f0a787f)
> make ':toclevels:' work in our jekyll templates
> -----------------------------------------------
>
> Key: SOLR-10612
> URL: https://issues.apache.org/jira/browse/SOLR-10612
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Reporter: Hoss Man
> Assignee: Hoss Man
> Attachments: lang-analysis-1-level-toc.png,
> solr-10612-largepage.patch, SOLR-10612.patch, SOLR-10612.patch,
> SOLR-10612.patch, SOLR-10612.patch
>
>
> asciidoc has a concept called {{:toclevels:}} which is suppose to determine
> which how deep down a page's section/header depth the generated table of
> contents will show -- ie: some LONG pages have a huge number of level 2
> headings, and on those pages we only want to show level 1.
> but in jekyll, asciidoctor isn't responsible for generating the TOC --
> instead it's done by some javascript (which is better for a variety of
> reasons) and at the moment this javascript doesn't know anything about
> {{:toclevels:}}
> But it should be possible to tweak our rendering templates to include
> {{:toclevels:}} as an attribute in the generated HTML, and then we can tweak
> the javascript call made to generate the TOC so that it respects it on a
> per-page basis
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
