Kenneth Lim

@davepagurek In the gist I have updated the test file to something that works 90% of the way. The main thing that doesn't work at the moment is modules. I'm...

> I notice the warnings top-level array in the old JSON seems to just be warnings from yuidoc about unknown tags and such. Those are also in the .min.json version...

For constants I'm not exactly sure how documentation.js expects it to be handled (will need to look into it), I'm thinking if we can use type alias to give something...

I'm thinking more in terms of ```typescript type CLOSE = "close"; ``` if it were typescript, so that when it comes to documenting it, it would be something like ```...

@davepagurek I would need to look into the code in more detail but I think it may be related to the order things already are in in `data.json` that YUIDoc...

Comparing the current website's reference section order with the `src/*` folder order, I would say the order here is basically alphabetical in terms of files and folders. If anything else...

@davepagurek I just had a check on the converted JSON working with the current website and noticed that there are still some issues between them. The Constants section currently seems...

I'll merge for now and worry about it later if something breaks

For parameters definitely, for things like default modes though it can be more ambiguous and probably won't have a specific syntax that deals with state machine's default state.

@GregStanton There are no major work on the documentation currently with @nickmcintyre probably already done with most if not all of the copy edits. That being said, if you would...