> I don't want to diminish your excitement but we're already in the > process of building a plugin repository to better manage the jQuery plugins.
Speaking of which, is there any list of things you are building into the first release? A list of future enhancements? As I've been reading, experimenting, and developing, I had a few thoughts. If 20k is the jQuery limit, that means new development on the core library will probably be really limited, and the future of jQuery really lies in the plugins. Is this the vision? If so, then the plugins area certainly warrants a lot of attention. It is probably where many new jQuery users will be hooked because they can easily do X or Y, not because they can do the lower-level JS stuff easier with the core lib. With these thoughts in mind, I had few suggestions - some (or all!) of which I'm sure you're already considering: 1. The "official" list of plugins should get its own page and be clearly separated from other non-official plugins. They should meet some tough standards, be updated and supported, and avoid overlapping functionality as much as possible. It should be clear what is required for a plugin to be considered "official". 2. Official plugins should have a common naming convention, always have the same license as jQuery itself, and follow some similar coding guidelines. 3. Documentation should be consistent. There should be a single format which all plugins should follow - perhaps an enhanced version of jsdoc? This way the API for every plugin could be published using the same structure and format, and multiple libraries could be combined and documented together. 4. In line with #3, some meta-data should be consistent across all plugins so a dynamic list of plugins could be built. Name, description, author, last updated, etc. 5. There should definitely be a ratings system or some way for the best plugins to quickly rise to the top. From a user perspective, there's nothing worse than a long list of optional modules like exists now. If a user is looking for a plugin, they might lack the experience or knowledge to create the functionality on their own. So how are they supposed to pick the best and most appropriate plugin to accomplish a task? Those "in the know" need to help them do it by making the best ones most visible. Just some thoughts. I would really like information or discussion on the documentation/API side of things, as I am currently looking for the best way to document a jQuery API. Matt Kruse _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
