Updates

Plugins status updates from the jQuery Team.

Plugins: April 28, 2012

We’re taking a new (better) approach for the integration with WordPress. Instead of interacting directly with the database, we’ll be utilizing the WordPress XML-RPC Server. The majority of the underlying work is now complete in the node-wordpress module and the plugins site will be updated to leverage it soon.

Plugins: March 30, 2012

The new plugins site is being developed in the plugins.jquery.com repo. After a discussion with the community, we’ve finalized the format for the package.json file. After more discussion about package naming, we decided to go with a convention that will work for the most number of use cases. You can read about the naming convention and name reservation process on the names page. Since this is the first post for the new plugins site, and the site has been in development for a while, there’s a bit too much to list in terms of what has gotten done. Feel free to follow the open issues and these weekly updates for more news.

Plugins: August 19, 2011

Joern got us a Balsamiq account.

Richard, Adam, Dan, Joern, Corey met Thursday to begin working on wireframes for plugin site, we decided on a general direction for where to place and structure navigation and came up with a workable wireframe for an individual plugin page.

Plugins: July 8, 2011

package.json spec is essentially finalised
We are now developing wireframes to comprise the functional spec for
the site, Dan is investigating that this week.
Views: Home, Search Results, Plugin, Plugin submission process
Narrative presentational information on plugins site will be pulled
from README in Github repository.

Preparing to submit specs for team approval in 2-3 weeks.

Plugins: June 24, 2011

We are nearing completion and agreement on the package.json spec:
https://github.com/jquery/jquery-plugins/blob/master/docs/json.md

While we will still be primarily distributing jQuery plugins, because
these plugins have non-plugin dependencies (CSS, JavaScript Utility
functions/libs, shared code to power “suites”) that will also need to
be distributed, plugins and all these other dependencies will all
distributed as simple Packages, which contain links to the resources
contained therein.

The package.json spec is used to describe a single plugin or resource.
If a repository has multiple plugins or resources, intended to be
top-level citizens of the site, it constitutes a suite if all the
resources will take the same version number. If a repo is a suite,
its author can apply to be whitelisted and can have multiple
namespaced foo.package.json files in the repository, which the site
will then index.

Next step is to plan frontend: NPM’s browser is instructive
http://search.npmjs.org/

Plugins site wiki is located at http://jqueryplugins.pbworks.com

Plugins: May 27, 2011

Plugin Team Status Update May 27, 2011

  • Team is currently discussing the project and next steps needed to see the plugin redesign to completion as quickly as possible.

Plugins: April 29, 2011

v3.0

  • Worked with Bocoup to redefine the project
  • Bocoup to work up new statement of work 
  • Need to work up project plan
  • set up weekly meetings on #jquery-meeting
  • Corey Frang (gnarf) has expressed interest in contributing.  Need to get him integrated and helping.

Plugins: April 22, 2011

  • Working with Pete and Sam at Bocoup to pick up where Boaz left off.
  • Reevaluating the current functional spec
  • May need to update func spec as Official plugins are no more
  • Will be planning a plugin hackfest at Bocoup in the future