One thing I always loved about Max/MSP was the insanely rich learning scenarios that have been embedded with the software.
sandboxed, emulated environments are awesome, kind of like the max/msp examples you mention, @laborcamp. recently, in the react.js community, a tool called CodeSandbox has gained a lot of traction.
am wondering if implementing something like the “see also” menus or selections, that would link to related elements of Teletype scripting language. If these were links to those portions of the docs, it would also help navigating through the files (less scrolling). I understand that this would be a huge task to undertake, but thought I would bring this up for the sake of conversation… thoughts?
Linking may be something we could leverage without changing any thing on the pandoc or the templates. each section of the doc has an id, and we may just be able to do something like
[#specific_section](see more) within the markdown for a particular doc page. In other words, I think this would be more of a content, rather than a code change.
Also, just so its clear, excited about the future of what we can do with this (and other monome projects) web docs, but my priority #1 is to get my current pass PR’d, merged in and push to the monome site. So I am pretty set on the bug fixes and the enhancements I’ve outlined above, and I don’t want to add more changes in this “release”, so that we can get this up and useful for people (and also so I don’t burn out on doing this stuff, heh)