Our existing documentation focuses on the names of functions and how to call them, but provides little sense of architecture or how to connect different pieces.
As other developers become interested in using mechanisms for interactivity, the lack of solid tutorials has increasingly been a source of pain that is only partly alleviated by our example gallery.
In particular, some of the APIs (such as match and filter syntax) are quasi-private, so that they could see further development and breaking changes before widespread adoption. As these APIs have matured, there has been a need to expose this information somewhere.
TODO
[ ] Stabilize the wiki --> JSDOC conversion
[ ] ...so that our tutorials can link to appropriate information
[ ] Editing, polish, and feedback / testing
[ ] Explore converting docs to a jekyll theme so that gh-pages can autobuild assets
[ ] Document linked axes / locking an axis to prevent scrolling
Purpose
Our existing documentation focuses on the names of functions and how to call them, but provides little sense of architecture or how to connect different pieces.
As other developers become interested in using mechanisms for interactivity, the lack of solid tutorials has increasingly been a source of pain that is only partly alleviated by our example gallery.
In particular, some of the APIs (such as match and filter syntax) are quasi-private, so that they could see further development and breaking changes before widespread adoption. As these APIs have matured, there has been a need to expose this information somewhere.
TODO