From: Nick Dokos <email@example.com>
Subject: Re: Tables of contents for individual sections wanted -- will donate
Date: Tue, 01 Jul 2014 09:10:18 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
"D. C. Toedt" <email@example.com> writes:
> Hi all --
> BACKGROUND: I've been using org-mode to develop the Common Draft annotated collection of business contract clauses, in part for the law school course in contract drafting that I
> teach to third-year law students. I've been posting the collection as a Creative Commons document 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.
It's not a pure org solution, but I'd go this way:
o have each "article" in a separate org file - export each one to HTML
(that can be scripted easily) - you get the article TOCs for free.
o have a separate top-level org (or HTML) file that contains the TOC with
pointers to the "articles". The production of this file can be scripted
as well: get the #+TITLEs of each "article" file and turn them into
The whole thing can be wrapped up in a Makefile to automate the process.
Navigation (prev/next/top) may be a problem but it shouldn't be too hard
prev parent reply other threads:[~2014-07-01 13:10 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
2014-06-30 20:19 ` Ian Barton
2014-07-01 2:45 ` D. C. Toedt
2014-07-01 13:10 ` Nick Dokos [this message]
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 \
* 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).