Saying goodbye to Demo Studio

When the Demo Studio area of MDN launched in 2011, it was a great new place for developers to show off the then-cutting-edge technologies of HTML5 and CSS3. In the years since then, more than 1,100 demos have been uploaded, making it one of the largest demo sites focused on cross-browser web technology demos. Demo Studio also served as the basis for the long-running Dev Derby contest, which offered prizes for the best demos using a different technology each month.

In the last few years, quite a number of code-sharing sites have become very popular, as they are solely focused on code-sharing functionality, for example, Github Pages, CodePen, and JSFiddle.

Given the variety of alternative sites, and the technical and logistical costs of maintaining Demo Studio, we at MDN have made the decision to remove the Demo Studio after January 15, 2016. After that date, demos will no longer be available from MDN via Demo Studio.

We encourage demo authors to move your demo to an alternate site, such as your own website, if you have one, or one of the popular code-sharing sites. In case you no longer have a copy of your demo code, you will be able to download your demo code from Demo Studio until 23:59, Pacific Standard Time, on January 15, 2016. If you’re looking for a place to share your demo, check out our guide to Using Github pages.

After January 15, 2016, you will be able to request a copy of your demo code by submitting a bug in Bugzilla. Please be sure to include the name of your demo(s) and an email address at which you can receive the source code. Demos will be available via this process until April 8, 2016.

Key Dates

Demo Studio will be removed; deadline to download your code.
Deadline to request a copy of your demo code manually, if you didn’t download it.

You are welcome to link to the new location of your demo from your MDN profile page. No automatic redirects will be provided.

Thanks again to all the demo authors who have contributed to Demo Studio!

5 comments on “Saying goodbye to Demo Studio”

  1. Stephan Sokolow wrote on

    Bad move. Often, the only demo I’ve ever been able to find that doesn’t require webkit-prefixed CSS or JavaScript is on Demo studio. (eg. for the notifications API)

    This will result in a lot of important links being broken, furthering the impression that Firefox is both dying and not worth the effort to support.

  2. Lázaro wrote on

    Es una lastima para mi es mejor que varias de las mencionadas.

  3. Md Ashraf Malik wrote on

    Why goodbay?

    1. Murad wrote on

      Because of technical and logistical costs of maintaining Demo Studio. THE MAIN REASON IS MONEY. Give them a money and demo will be work.

  4. Mori wrote on

    Google App Engine is another good option to consider.