Repository files navigation

The jQuery Plugins site,http://plugins.jquery.com/

The plugins site is an index of GitHub repositories that contain jQuery plugins.The repositories can contain one or many jQuery plugin with an accompanyingvalidplugin.jquery.json manifest file in the repository root. Thespecification for this file liveshere.

Simply add apost-receive hook toyour repository with our Web Hook URL,http://plugins.jquery.com/postreceive-hook..When you push to your repository, the plugins site will look at your repository'stags and their corresponding manifest file (thepluginname.jquery.json). You canread up on this process, as well as the requirements of the manifest file onthe jQuery Plugins Site.

Assuming there were no errors in your manifest file, your plugin should be onthe plugins site within a minute after pushing to GitHub. If you still don't seeyour plugin listed, check theerror log.

We are currently exploring options to provide better feedback on errors encounteredduring the process of adding your plugin to the plugins site. If you are stillencountering issues after verifying the post-receive hook is in place and thatyour manifest file is valid, ask for assistance in #jquery-contentonfreenode.net.

• jQuery'sjquery-wp-content
• Web server (such as Apache)
• PHP
• MySQL
• WordPress
• node
• git

1. Follow the installation steps forjquery-wp-content.

1. Followhttps://github.com/joyent/node/wiki/Installation

You can also installnave, a node version manager.You can easily install it usingnave-installeror download it manually.

To build and deploy your changes for previewing in ajquery-wp-content instance,follow theworkflow instructionsfrom our documentation oncontributing to jQuery Foundation web sites.

If you want to setup and ultimately run the node scripts that manage pluginentries, rungrunt setup. If you need to clear the db or are getting and errorrunninggrunt setup regarding the setupdb or retrydb tasks failing,rungrunt clean-all.

If you have made changes to the documentation and simply want to deploy or updatethat content, rungrunt update.

1. node scripts/update-server.js --console will start the update server andlog its output to the terminal window. This willnot update wordpress, butwill let you see the result of adding a plugin locally.

2. node scripts/wordpress-update.js --console will process the changes insqlite into entries in wordpress. Note, if you're re-adding plugins that havealready been added, you will need to remove those entries from wordpress.

node scripts/manager.js runs the update-server and wordpress-update scriptsautomatically. However, because it handless restarts/failures of these scripts,it is harder to stop this process. Also, running the servers manually andindividually is much easier for development, as you will probably onlyneedupdate-server.js running.

On occassion, a plugin will be transferred from one owner to another. When thishappens, you will need to verify that the transfer is legitimate. The requestshould come from the original owner, but in rare circumstances the request maycome from the new owner and the original owner may not be reachable.

To transfer a plugin, log into the production server and run thebin/transfer.jsscript. The script will prompt you for the necessary information and has severalchecks to ensure that the data provided isn't junk.