The caption of jumps (i.e. links to other chapters or sections) should be more customisable. For example, instead of the chapter name, the user may want to use its number instead (e.g. "Chapter 1" or "Section 1.2"). Document.toDocumentTree could take a function similar to generateId.

A user should have the possibility of reporting errors/suggestions in the generated manual. This could be implemented by integrating the GitHub issues API.

When writing a manual for a library, there are certain constants like package names or version numbers which often appear several times throughout the document. As for Scala projects, a user may want to extract the version number directly from the build.sbt, so that the manual can be easily kept in sync.

Support different modes: in the 'release' mode, todos should be hidden.

For example: http://jsfiddle.net/gilbitron/Lt2wH/

A non-javaScript solution should be preferred though.

Every element should have the Boolean parameter draft. A function filterDraftNodes() could be provided to exclude those elements from the generated HTML file.

Support boxes such as warn or note.

Write an sbt plugin, so that the manual generation can be made part of the build process.

See also com-lihaoyi/fastparse#35.

• Support comments

The following three paragraphs should not be merged:

a

bold{b} c

bold{d}

The paragraph detection must be covered by test cases as it's too complicated already.

Use the "modified" timestamp of the generated source file to implement this.

Currently the chapters are organized starting with "ch00" and incrementing up. What if I want to inject a new chapter in the middle? This means I have to go through and rename every following chapter file name.

The following error is not meaningful:

[error] (run-main-0) java.lang.RuntimeException: Nonzero exit value: 1
java.lang.RuntimeException: Nonzero exit value: 1
        at scala.sys.package$.error(package.scala:27)
        at scala.sys.process.ProcessBuilderImpl$AbstractBuilder.slurp(ProcessBuilderImpl.scala:132)
        at scala.sys.process.ProcessBuilderImpl$AbstractBuilder.$bang$bang(ProcessBuilderImpl.scala:102)
        at pl.metastack.metadocs.document.writer.SbtScala$$anonfun$runProjects$1.apply(SbtScala.scala:153)
        at pl.metastack.metadocs.document.writer.SbtScala$$anonfun$runProjects$1.apply(SbtScala.scala:150)
...

It should be fairly straightforward to add support for LaTeX and PDF generation. As in Pandoc, the user should have the possibility to specify a custom template.