CODEWITHSUNDEEP
javascriptjqueryhtmlcssplugins
jsgroove
jsgroove

Reputation: 1497

jQuery plugin html and options practices

I am working on creating a jQuery plugin and I have some questions regarding how to structure things:

1.How much HTML should the plugin have written and how much should it create through jQuery ?

Is it good to have written all of the HTML so that the entirety of the markup structure is visible when looking over the code ?

Or is it better to have written only the minimum amount of HTML so that it is very easy for the user to add/modify content and create all of the rest, bulky HTML through jQuery ?

Is there a recommended practice ? How are things done in professional plugins ?

Why should things be done in a certain way and what are the reasons behind it ?

2.How to balance the plugin options with the CSS ?

Should the plugin offer options that would affect the presentation of the plugin (options that would modify the stylesheet) or is it a better practice to have the user directly modify the stylesheet for presentational modifications and in the plugin only have options relating to the functionality ?

What are some guides regarding what options to offer in the plugin as to not step over CSS ?

Regarding my experiences, I have seen all of these in different places and plugins and that is why I am asking for opinions from experienced users and what are good practices and why.

Upvotes: 0

Views: 412

Answers (2)

Michał Miszczyszyn
Michał Miszczyszyn

Reputation: 12721

1. How much HTML should the plugin have written and how much should it create through jQuery ?

According to the paradigms of progressive enhancement, there should be no markup which would be useless in case of no JS enabled. In other words - if your plugins needs some special markup and additional tags it should create them by itself.

The reasons for that is semantics. Additional plugin markup is useless for users (and bots) when there's no JS enabled and thus it should not be present at all.

Also keep in mind that developing a good JS plugin means that content will still be available when the plugin fails or JS is disabled. Moreover, you have to take additional care about making sure that your plugin is accessible. More on the topic of progressive enhancement covering also more advanced issues can be found for example in a book by The Filament Group.

2. How to balance the plugin options with the CSS ?

Do it as follows:

  • Content: HTML
  • Logic: JS
  • Presentation: CSS

Despite the fact it's changing now a bit (think CSS3 animations), options of the plugin may influence the way it works rather than the way it looks. That means your users should be able to config timings, delays, speed, number of element or whatever your plugin is doing through JS. But leave the presentational aspects in the CSS stylesheet. Use JS to change classes of elements rather than inline styles and let your users write whatever CSS they want. Obviously, don't forget to provide some default styling :)

I always recommend reading more on the topic in A List Apart. It's quite a theoretical article but absolutely a must-read for any front-end dev.

Upvotes: 2

sneeky
sneeky

Reputation: 1508

Tutsplus has a jQuery course with usefull videos. http://tutsplus.com/lesson/head-first-into-plugin-development/

This is one of the videos that explaines how te make a plugin. There are a lot of ways to create a plugin, but this is a good one.

Upvotes: 0

Related Questions