Thank you @jonathan , this is super helpful. In fact, I'm going to be meeting with developers soon and I would love it if you (or anyone else) could point out any flaws in my thinking. I've researched this quite a bit but I'm sure there are some holes in my ideas.
I'm planning the project to be in two phases:
I'd like to use AJAX (likely via Jquery) to send data to my Canvas site from my HYPE static page. For example, a user reaches a certain scene and this triggers some code that initiates the Canvas API to mark a certain module complete. I know there are cross-domain limitations with AJAX so would having the Hype site be at the same domain as my Canvas install be essential?, or just easier? Would I need to use something like CORS instead? Also, am I correct in thinking that using Jquery with AJAX works around this limitation? Do I have this scheme all backwards and actually need to create some kind of middleware? Would I have to use some kind of third party software wrapper like this .
I'd like to use the Canvas API to populate my Hype static site with the data from my Canvas install (users, courses, modules etc). Wouldn't this be the same as using AJAX with the APIs of say Twitter or Flickr to add content to a static site? As the admin of my Canvas site I can generate a client ID and secret. I also can generate tokens. Is this doable?