JQuery - application code against creating a plugin

Question

When does it make sense to turn your code into a jQuery plugin?

What are the criteria / signs that parts of your code may be better as plugins?

Answer 1

In fact, your code is a jQuery plugin as soon as you start adding new stuff to $.fn.

But also, it makes sense to reuse code or code that is not specific to your application.

Also see the Plugin Creation Guide - this shows you some best practices that you should follow; especially if you can release your jQuery plugin at some point. But it may also give you some ideas on when it makes sense to make your code a plugin.

Answer 2

This is more than anything else, if the code is completely completely abstracted / can be reused, and if so, if you think you really need to reuse it at any time in the near future. I usually get a mixture of both; general functionality abstracted in plugins, and custom user code that configures these plugins and customizes everything that is unique to this page.

, , , . , , , , . Javascript .