Leaving aside the intended audience for our plugins, throughout our development process we've used a mix of different techniques, but with one thing in common—our plugins have very few dependencies! This is not to be sniffed at, as clearly any dependencies that change may have a resulting knock-on effect for our plugin.
This aside, there will be times when the lack of any dependencies may require more development effort than is sensible (or practical)—it is at this point where we may need to consider using additional plugins to handle some of the processing. A perfect example of this is to parse a font: statement so that we can work on the constituent elements; there are a few others that are worthy of note:
|
Type of parser or helper |
URL of plugin source |
Purpose of plugin |
|---|---|---|
|
Selector | ||
|
Value |
Transforms CSS values and |