Loading it from the Google CDN and ensuring it is cached reduces load, with the functionality gain it brings.
jQuery is not perfect, but it gives us a baseline to develop against and reduces the barrier to entry for building richer client-side functionality.
- WCMS use
- MVC.net use
All scripts go in the bottom of the page.
This is a good thing though, as it enables us to:
- begin to abstract common sets of functionality into self-contained modules
- pull application specific code into a single cacheable file
The plugins.js file has been developed to provide a core set of common rich functionality. This functionality applies itself based on matching class names and data- attributes. Scripts are lazy-loaded (and cached) on need.
This allows us to manage common functionality in one place, and upgrade components in a managed way.
- Version and status