What feature should be changed? Please provide the URL of the feature if possible. ================================================================================== The Live Sample system is pretty cool, and works well for most things. However, there are a some cases where it fails to come through, and I'd love to see them addressed: 1. When you want to link to external resources in your live demo, be they JS files, CSS files, whatever. Yes, I could just put the code in the page, but in cases like web components it completely defeats the purpose of using the component in the first place, and probably won't work anyway. I appreciate the security implications of doing this. Perhaps we could just put the demo on say gh-pages (or https://mdn.mozillademos.org*), whitelist that particular subdomain for embedding, and put it in an IFrame. Or maybe there is a way to allow linking/script tags in a secure way? 2. When you just want to embed a demo that someone has already put up on say github or jsfiddle. It is more reusable where it is, and it would be a waste of time to recreate it in a live sample. * could we have some kind of system to allow us to manually upload demos to https://mdn.mozillademos.org? I'd still probably prefer github, as the code is more reusable that way. What problems would this solve? =============================== Shortcomings in MDN live samples/sample embedding Who would use this? =================== MDN editors/contributors What would users see? ===================== Better quality demos What would users do? What would happen as a result? =================================================== Better quality demos Is there anything else we should know? ====================================== Nope.