emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "D. C. Toedt" <dc@toedt.com>
To: ian@manor-farm.org
Cc: emacs-orgmode@gnu.org
Subject: Re: Tables of contents for individual sections wanted -- will donate
Date: Mon, 30 Jun 2014 13:55:53 -0500	[thread overview]
Message-ID: <CAGN11+21Saq1yC3aE-eLWjSo7WUL8CKZ4L4vEnt2hFZd7ecUQA@mail.gmail.com> (raw)
In-Reply-To: <53B1AF24.7010502@wilkesley.net>

[-- Attachment #1: Type: text/plain, Size: 1680 bytes --]

Thanks, Ian.  I've done things like that in the past, but it'd entail
maintaining the TOC by hand, which I was hoping to avoid.  True, I'd be
able to create the initial TOC using org-mode, followed by manually
inserting jQuery calls.  But I'd have to manually edit the TOC every time I
added a new chapter or section and every time I edited a heading title.

On Mon, Jun 30, 2014 at 1:40 PM, Ian Barton <lists@wilkesley.net> wrote:

> On 29/06/14 19:51, D. C. Toedt wrote:
>  at http://www.CommonDraft.org, and plan to expand and maintain it.
>> QUESTION:  I'm currently using a single, multi-level table of contents
>> (TOC) at the beginning of the document.  That ends up being a lot to
>> scroll through to get to the first chapter.  I'd like instead to have:
>>   * a one-level "master" TOC at the beginning of the document, listing
>>     and linking to just the articles (in contracts, "articles" are the
>>     same as "chapters" in books, that is, the top-level sections); and
>>   * at the beginning of each article, a TOC listing and linking to the
>>     subheadings within that article.
> Not an org-mode solution, but if your audience is consuming the content as
> a web page generated from org-mode, you can do most of this using jQuery.
> What I am suggesting is you make your TOC collapsible and clicking on a
> heading in the TOC expands the links to the sub headings underneath the
> heading. You can probably do nested collapsible headings so you can expand
> various level of subheadings like a concertina.
> I am definitely not a Javascript expert, but I have managed to use this
> technique on some of my documents.
> Ian.

[-- Attachment #2: Type: text/html, Size: 2768 bytes --]

  reply	other threads:[~2014-06-30 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 18:51 Tables of contents for individual sections wanted -- will donate D. C. Toedt
2014-06-30 18:40 ` Ian Barton
2014-06-30 18:55   ` D. C. Toedt [this message]
2014-06-30 20:19     ` Ian Barton
2014-07-01  2:45       ` D. C. Toedt
2014-07-01 13:10 ` Nick Dokos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGN11+21Saq1yC3aE-eLWjSo7WUL8CKZ4L4vEnt2hFZd7ecUQA@mail.gmail.com \
    --to=dc@toedt.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ian@manor-farm.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).