1* Make section anchor unique, use characters not allowed in identifiers2* Make Record.hs like macro expansion more generic3* Use SyntaxError error type in Record.hs4* Special handling for `(define x (case-lambda …))`5* Check for broken anchor links in generated HTML6* Consider removing declaration description7* Support `include-ci` in `Library.hs`8* Add flag to include un-exported identifiers in documentation9* Consider using `lucid2` instead of `blaze-html`10 * Ideally in combination with `mmark`11 * See: https://github.com/mmark-md/mmark12* Scribble-like syntax for comments13 * Have a function call syntax e.g. `@function{parameter}@`14 * Map that to formatters to allow stuff like `@pre{code}@`15 * Should also allow for customizations through the SchemeDoc library16* Somehow allow for a semantic representation of scheme objects17 in the Formatable type class, e.g. don't already return specific18 heading levels etc19* Parser: Better error messages20* Tests: Perform some compliance tests of the R7RS parser21* Make it easier to use SchemeDoc as a library22 * E.g. for supplying custom expression formatters