Not finding the answer you're looking for here? Check out the YUI developer forums, where thousands of YUI users and developers gather to discuss the library, or head over to the #yui IRC channel on freenode.net.
With a wealth of documentation and a thriving online community, YUI takes you from basic DOM manipulations to the most complex applications without missing a beat. It is a world-class platform for novices, hackers, and application developers alike. By providing a concise, convenient, and intuitive API that is lightweight and lightning fast, plus a well-thought-out infrastructure and a comprehensive suite of tools to help you code like a professional, YUI is perfect for throwing together simple effects on a web page and engineering maintainable, performant, and well-architected web applications.
No. If you're using SSL, it is recommended, and honorable, that YUI is hosted and loaded from your own server. SSL implies the user is communicating strictly with your website, and your website only. When YUI is hosted under your own server, you must also implement your own combo handler.
The YUI forums are a great place to go to ask a question. They're searchable too, and with thousands of questions already having been answered, a quick search there might get you just the answer you need.
The #yui IRC channel on Freenode is another great place to give and get community support. There are almost always YUI core developers or contributors around to answer your questions.
The YUI team designates products or components as beta during their initial release phase. This allows us to get valuable feedback from the community about the product and its API before we lock down that API from major changes. If a product is marked as beta, that means we're expecting to make modifications to the API that may not be backward-compatible. If you include a beta product in your project, you may find that when you upgrade to a future release, you'll need to make changes in your implementation code for that product.
In some circumstances, the YUI team may release a product or component in an experimental state to indicate that it has not been extensively tested or may involve a technical approach that has not been proven out in other applications. We release such products to solicit community feedback and to begin the process of evaluating them in a wider context than we can provide within the YUI team. Significant work may need to be done before the product is ready for production release on mission-critical applications. Some products will evolve from experimental state to beta and then to GA, but other experimental products may never evolve to production quality due to technical hurdles identified during community experimentation.
All of YUI's open source code is available on GitHub.
The -debug.js versions of YUI build files contain additional log messages that output to the browser console or Console component. These messages include information about any warnings or errors that may happen at runtime, as well as "interesting moments" that happen during an interaction.
The -min.js versions of YUI build files have been minified via YUI Compressor for maximum performance in a production environment.
Our development schedule is available on GitHub and you are free to join our
yui-contrib mailing list to stay up date on the latest developments in the community. (Note
yui-contrib is not a support forum. Please visit the YUI forums for support questions.)
See Tutorial: Report a Bug for everything you need to know.
Within the YUI team, we tend to pronounce it "why-you-eye". However, in the community and all over the world we more often hear it pronounced "yooey." We answer to both!