Official CDN for exported code?
Cannot find an official CDN to support exported code as an alternative to the documented procedure (embed in reveal.js framework). A CDN should enable required assets to be downloaded on demand, optionally minified (unless I'm doing something wrong).
For example at http://cdnjs.com/libraries/reveal.js
Tried prepending "http:" and "https:" to
//cdnjs.cloudflare.com/ajax/libs/reveal.js/2.6.2/css/reveal.min.css
And that doesn't point to anything.
This would enable exporting and running exported code without uploading the reveal.js framework to the website (which isn't always feasible or practical).
-
Tony Su commented
Spitballin' a bit...
A possible alternative to exporting the presentation and then embedding in a website (especially if limited access to webserver files) is to simply embed the presentation already running at slid.es.
Depending on the website technology of the website you want to embed the presentation, a container would need to be created with specified dimensions, then reference the presentations runnin on slid.es.
Maybe a frame could be used if permitted on that site.
Still, for those who want to serve the presentation from the same webserver it would be nice to be able to reference an official CDN for resource files.
Tony
-
Tony Su commented
An update...
I found minified resource files in the reveal.js github repo.So, I suppose it should be possible to reference the files either in the official repo or host another location, but doing that bothers me... I'd like to think that files used in this way should be hosted by a proper CDN provider.
One advantage to using a proper CDN provider where everyone would use the same reference is that the files are locally cached when used the first time. So, for instance if someone viewed my reveal.js once referencing a CDN and then viewed a presentation created by someone else using exactly the same reference, the file would not be downloaded again because the required files would already exist in the local cache.
If everyone used a different URI to the same file hosted different places, the same file would be downloaded every time, the same result if everyone hosted the files locally the way the official documentation describes.
Tony