Closed akavel closed 11 years ago
all the JS does is call into http://gist.io/3135754/content
, you can interface with that on your own if you like
Yup. The only difference between what you have on /…gist-id…/content
and what you get out the github API is that I've gone through and rendered/sanitized markdown for each file, and saved the rendered output in each file's 'rendered' key (check out the JSON)
For now, the reason that it uses JS is because I don't want to hold up the pageload while the server hits the github API. It's pointless though in the case where the rendered gist is already in the cache, see #23.
It would be nice if viewing the contents (which is fairly static) wouldn't require me to have JavaScript enabled (and available at all) in the browser. This way I could also wget/curl such a page, etc.