YUI Gallery Deprecation Announcement

By Julien LecomteJune 16th, 2014

Since it was first introduced in 2009, the YUI Gallery has been a great tool for web developers, allowing them to contribute to the YUI library in a more open way, make their YUI modules more discoverable, and deploy them at scale using Yahoo’s CDN. As a result, the YUI Gallery now contains over 600 modules.

Since that time, the industry has drastically changed and evolved. New tools, which did not yet exist when the YUI Gallery was introduced, have since been widely adopted by the community. GitHub, package managers (npm, bower), build tools (grunt and its myriad of plugins) and free or cheap CDNs (cdn.rawgit.com, jsDelivr, cdnjs, CloudFare, etc.) have made it much easier for developers to share and deploy their modules efficiently. As a result, the YUI Gallery is not as actively used by the community as it used to be. However, the cost of maintaining it is still there. Therefore, the YUI team has made the difficult but necessary decision to deprecate the YUI Gallery.

The last gallery build will take place on Thursday, July 31st, 2014. All the modules that have been published to the gallery prior to that time will continue to be available from Yahoo!’s CDN as they have always been. However, after the last gallery build, it will not be possible to publish any new modules, or update an existing module, to the YUI Gallery. This means that modules will no longer be pushed to the yui3-gallery repository on GitHub and no new gallery modules will be pushed to Yahoo!’s CDN. If you try to publish a module after that date, yogi will return an error. Finally, the YUI Gallery web site will be statically archived for posterity.

As I mentioned, all the modules that have been published to the YUI Gallery prior to Thursday, July 31st, 2014 will continue to be available from Yahoo!’s CDN as they have always been. But what if you need to update an existing module (to fix a bug for example)? After the last gallery build, updating your gallery component will not update the corresponding artifact on Yahoo!’s CDN. Thankfully, there is a very simple and straightforward solution to that problem. Because the source code and build artifacts of YUI Gallery modules are hosted on GitHub, you can load those modules directly by taking advantage of cdn.rawgit.com. Here is a trivial example of how to do that:

Additionally, just like you would do with any other JavaScript resources, you can also bundle modules together, host them on your own servers, and deploy them using your own CDN provider.

If you publish a YUI module to the npm or bower registry (for example) and wish to make it more discoverable, we recommend that you tag your package with the yui-module tag.

If you need additional support, or have questions related to the deprecation of the YUI Gallery, feel free to post a question to the gallery sub-component of the yui-support group.

Julien and the YUI team @ Yahoo


  1. It is what it is. My question is how to discover the new stuff? Yes, there are lots of tools out there, but since the gallery stopped being managed, with it also went a way to easily discover the new and interesting modules out there. I notice that you’re not mentioning any alternatives in that area.

  2. The same discoverability issue applies to all packages, no just YUI modules. This is something package managers such as npm or bower address by giving developers the ability to tag their package as well as search for packages by tag. In the article, I suggested people may want to use the yui-module tag to help with that.

  3. Ryuichi Okumura said:
    June 17, 2014 at 5:49 am

    We might be needed the detail plan about this.


  4. Matthew Robb said:
    June 18, 2014 at 10:38 pm

    @Marc Schipperheyn – Try this: https://www.npmjs.org/browse/keyword/yui

  5. @Matthew yeah, that’s pretty nice. I would hope that the YUI team keeps highlighting interesting new modules in their weekly blogposts

  6. I think this is the right move. I’d also like to know what the team’s thoughts are on AngularJS and Ember leaping quite a ways ahead of YUI’s Backbone-based application framework.

  7. barny relph said:
    July 3, 2014 at 4:54 am

    Could I suggest that as part of the final build, the paths to images in CSS are tidied up? There’s a lot of incorrect paths in /build currently that prevent or complicate hosting the gallery yourself. See this for a fuller explanation: https://groups.google.com/forum/#!category-topic/yui-support/gallery/iEYpa9pfT3o

  8. So, guys, what’s happening? After the forum and the gallery now also the blog seems to fall into disuse.

  9. A lot of cool things are happening, but nothing we can talk about just yet…

  10. That’s great to hear. Hope you can share soon. Count me nervous.

  11. Will YUI start incorporating some of the gallery features in to the core build? There is quite a bit lacking in the core which is covered by the gallery but if the gallery isn’t updated and modules break over time (as changes break modules) then YUI is kind of killing it self a bit