Tom MacWright

> I think we should allow ourselves to "preprocess" that markdown to handle cross-references (#19) and such. For instance, this is one of the main reasons why documentation.js _did_ return...

Sure, so... JSDoc has a whole [tutorials system](http://usejsdoc.org/about-tutorials.html), which is not implemented at all by documentation.js. Documentation.js's 'table of contents' does allow some room to add longer-form documentation, but I...

Totally, that'd probably be way more useful. I haven't found a solution to that that isn't brute-force and I think the perf of the brute force approach might be crazy.

Now that we're aiming at a CommonMark superset, could we adopt the CommonMark 'verbatim reference link' syntax, like ```js /** * Automatically turns into a ref: [JSON.stringify] */ ``` So...

I think yes and it might be a double-win - this could give us a way to replace **Pedantic** because it'd do basically the same thing! The only gotcha is...

Ecmarkup looks great. There's enough consensus on enough parts of the spec to start drafting imho, will start soon.

I've started drafting something up! https://github.com/tmcw/dx-spec/blob/master/spec.md

Sure, seems like a good option.

Started in 364675fa03261ec08e85eab3b6ea4b588ba4cc26

😭auth0 buries it deep in their documentation but they [don’t support SPAs requesting from GitHub or any other 'identity provider](https://auth0.com/docs/connections/calling-an-external-idp-api). Wish they had stated that a _bit_ earlier in the...