Open myersjustinc opened 12 years ago
You still might want to maintain this. If not for Soundslides (which are, admittedly, fading in popularity), then for other embeddable media. Maybe use the same pages for interactive graphics and other Flash and JS embeds?
The existing Markdown support should already accept arbitrary HTML for embeds--which should work for embedding things within articles, for example, but you're right that there probably should be some sort of general-purpose multimedia container type for standalone embeddable content.
I'm mainly saying that the very Soundslides-centric implementation we have now (accept a zip of the output publish_to_web
folder, unzip it on the server, look for soundslider.swf and insert its path into what's essentially a Soundslides embed code template) probably wouldn't work well for organizations that produce slideshows any other way.
The current slideshows implementation was back when Soundslides was a bigger deal than it now is. Do we remove that? Do we add other kinds? popcorn.js, perhaps, or some simple jQuery modal things?