January 17, 2013 at 23:01Meet the long-awaited plugins.jquery.com
The jQuery plugin registry has long been turned into a cemetery. Over the past few years, it has become scary to navigate, names have ceased to be read on the graves of once popular libraries, and only gusts of a cold wind and strange shadows flickering between marble slabs could expect an accidental traveler who, in his misfortune, chose the path through this resource.
Fortunately, the kingdom of despondency and fear came to an end. Meet the reborn, beautiful and comfortable, useful, logical, and usable jQuery Plugin Registry
.
Following the recent update of the resource with the documentation , we have a whole new plugins.jquery.com, which until today has caused only pity.
The pages of the site received a new design. It has become more spacious, a little brighter (although the general gloom is not in a hurry to leave), but most importantly - with its help it has become much easier to find interesting plugins and determine their mental health.
The plugin profile contains information about the author and releases, links to documentation and a repository, and he is also able to talk about the activity and relevance of development. If someone is not familiar with the specifics, I explain: if there are a lot of releases, the last of them is recent, and the repository is being watched and actively forked, then it’s definitely useful to someone other than the owner.
The screenshot above shows the plugin with “5 watchers” and “2 forks” - already better than nothing. Although according to other information it’s still difficult to judge something, because All releases on the portal begin their countdown from 01/17/2013.
The team worked on the portal not only externally. The main idea has shifted. Publishing and working on plugins has become much easier. If earlier it was necessary to send your code for approval, and its publication was a strictly closed action (due to which, in part, projects were dying in obscurity), now everything is simpler and more transparent.
This was achieved through the adoption of three agreements: on the naming of the plugin , on publication and on packaging .
Plugins are no longer stored directly on the resource. They are collected and distributed directly from the repository, by adding a regular git tag. So far, GitHub is used as a platform for storing the repository , but in the official announcement it was said that the list of resources with which the Registry is integrated will be expanded. By the way, you can help in this process - the source code of all resources was open, and the team on your blog offers you to join the development.
The package manifest with the plugin was described , from which its page on the resource will be automatically collected. It contains the required information - name, version, title, author name, dependencies and license, as well as some optional fields.
I hope that nightmares will no longer torment any jQuery user, the population of galleries and sliders will stop growing, and the updated plugins.jquery.com will become something like rubygems.org (or The Ruby Toolbox , as the comments suggest) for the language ruby and will contribute to the natural evolution of good libraries and the burial (with corresponding honors) of bad ones.
I want to remind you that there are still a dozen or two fly in the ointment in the ointment, and therefore do not forget to report bugs and make suggestions - now this is a full-fledged OpenSource project managed by the community.
Fortunately, the kingdom of despondency and fear came to an end. Meet the reborn, beautiful and comfortable, useful, logical, and usable jQuery Plugin Registry
.
Following the recent update of the resource with the documentation , we have a whole new plugins.jquery.com, which until today has caused only pity.
Redesign
The pages of the site received a new design. It has become more spacious, a little brighter (although the general gloom is not in a hurry to leave), but most importantly - with its help it has become much easier to find interesting plugins and determine their mental health.
The plugin profile contains information about the author and releases, links to documentation and a repository, and he is also able to talk about the activity and relevance of development. If someone is not familiar with the specifics, I explain: if there are a lot of releases, the last of them is recent, and the repository is being watched and actively forked, then it’s definitely useful to someone other than the owner.
The screenshot above shows the plugin with “5 watchers” and “2 forks” - already better than nothing. Although according to other information it’s still difficult to judge something, because All releases on the portal begin their countdown from 01/17/2013.
Changes in the mechanics
The team worked on the portal not only externally. The main idea has shifted. Publishing and working on plugins has become much easier. If earlier it was necessary to send your code for approval, and its publication was a strictly closed action (due to which, in part, projects were dying in obscurity), now everything is simpler and more transparent.
This was achieved through the adoption of three agreements: on the naming of the plugin , on publication and on packaging .
Publication
Plugins are no longer stored directly on the resource. They are collected and distributed directly from the repository, by adding a regular git tag. So far, GitHub is used as a platform for storing the repository , but in the official announcement it was said that the list of resources with which the Registry is integrated will be expanded. By the way, you can help in this process - the source code of all resources was open, and the team on your blog offers you to join the development.
Package manifest
The package manifest with the plugin was described , from which its page on the resource will be automatically collected. It contains the required information - name, version, title, author name, dependencies and license, as well as some optional fields.
Conclusion
I hope that nightmares will no longer torment any jQuery user, the population of galleries and sliders will stop growing, and the updated plugins.jquery.com will become something like rubygems.org (or The Ruby Toolbox , as the comments suggest) for the language ruby and will contribute to the natural evolution of good libraries and the burial (with corresponding honors) of bad ones.
I want to remind you that there are still a dozen or two fly in the ointment in the ointment, and therefore do not forget to report bugs and make suggestions - now this is a full-fledged OpenSource project managed by the community.