Tom MacWright

This is already fairly performant at runtime, but finding the right way to transform it is important.

Modules

2

JSDoc has [its own idea of modules](http://usejsdoc.org/tags-module.html), which [I've discussed before](https://github.com/documentationjs/documentation/issues/803#issuecomment-330340611) - essentially * JSDoc modules are not CommonJS or ES6 modules. * I'm unconvinced that JSDoc modules are a...

Differentiating what is a documentation comment

5

### Intent Code comments are heavily used as things other than documentation: for TODOs, for notes to self, for swear words, and sometimes more. We don't want to accidentally include...

Does the dx-spec data model need to inherit from unist/mdast?

6

So: the idea to be a Commonmark superset still seems very good to me. But it raises a question that has also been relevant to documentation.js: if you're parsing Markdown...

https://developer.apple.com/documentation/cloudkitjs

Sketch out cross-references section

7

Refs #4: a proposal for how we could do cross-referencing documentation. TODO/qualms: this really hinges on how we define 'namepaths' or something similar, but this section does not specify that....

Add more cocktails

10

https://archive.org/stream/modernamericandr00kapp/modernamericandr00kapp_djvu.txt is public domain and classy, but very outmoded.

mdconf-style tags

3

In drafting up the [spec](https://github.com/tmcw/dx-spec/blob/master/spec.md) and testing out some code examples in CommonMark, I'm really liking the approach of [mdconf](https://github.com/tj/mdconf#example)'s tags: instead of ```js // @param a {string} // @param...