Platform

system has to literally have a way of swapping their stylesheets and scripts in and out on demand. Then it has to provide all the events to hook into and machinery for "activating" these tools: * Events for constructing parents before children * Events for initializing parents after children * Async loading on demand of all scripts/stylesheets as fast as possible * Compiling and minifying everything into a couple filesfor production * Support for versioning and storing some (most) of the code in local bundles for downloaded PhoneGap apps And then you still get questions such as "how does a Streams/related tool interoperate with a Q/tabs tool on the SAME ELEMENT, so I can combine the behaviors and have a bunch of tabs that represent articles related to a particular topic?" The tabs are supposed to "just work" and the "related" tool is supposed to "just work". So when it comes to CSS, a few years ago I just went with the straightforward approach: You call Q.addStylesheet(...) and it "just works". It adds your stylesheet when your tool is loaded and then removes it when it's not needed. Each class and id is supposed to be prefixed by the namespace of the plugin bundle you're distributing. Each tool would have classes that are prefixed with that tool's name. Naturally, you avoid ids in the actual plugin, but each tool has an id which the app can use to style things. You can take a look at the result here: https://github.com/EGreg/Platform/blob/master/platform/plugi... https://github.com/EGreg/Platform/blob/master/platform/plugi... https://github.com/EGreg/Platform/blob/master/platform/plugi... https://github.com/EGreg/Platform/blob/master/platform/plugi... And the corresponding JS modules: https://github.com/EGreg/Platform/tree/master/platform/plugi... https://github.com/EGreg/Platform/tree/master/platform/plugi... Here is an example of a Streams/related tool integrating with a Q/tabs tool: https://github.com/EGreg/Platform/blob/master/platform/plugi... So that's a proven style I would recommend.