Static Assets for Use In Forms

The online forms system provides a number of static assets that may optionally be used with forms built in the system.  Downloadable templates all make use of these assets.

Style Sheets

bootstrap.min.css, bootstrap-responsive.min.css: version 2.3.2 of the Twitter Bootstrap framework.

bootstrap.namespaced.min.css, bootstrap-responsive.namespaced.min.css: "namedspaced" implementation of the above.  Bootstrap styles only apply inside containers with the bootstrap-styles class.  You probably only need one or the other.  Available in 1.3.4.

northwestern-bootstrap.css: a set of custom additions to Bootstrap, mostly used in the Online Forms backend.

northwestern-bootstrap.namespaced.css: namespaced implementation of the above.

northwestern-forms.css, northwestern-forms-responsive.css: Basic styles for displaying forms

northwestern-forms-print.css: Print-friendly styles for forms.

northwestern-layout.css, northwestern-layout-responsive.css: Styles to handle the overall wrapper of the page, particularly the header and footer.


bootstrap.min.js: JavaScript for the Bootstrap framework.

jquery.min.js: Version 1.10.2 of the jQuery framework.  The Bootstrap framework expects jQuery to be available.

jquery.onlineformhelpers.js: A custom plugin to simplify common form-creation task.  See Forms jQuery Plugin for more information.

modernizr-respond.min.js: Version 2.6.2 of the Moderizer framework with version 1.1.0 of Respond.

plugins.js: A custom script that executes when the form is rendered to trigger functions defined in the jQuery Plugin.

Versions and Numbering

Each version of the static assets should persist as long as the Online Forms system runs.  So you can link to a specific version and not worry it will change or disappear.  Newer versions will have an incremented version number following the major-minor-patch or "semantic versioning" scheme.  Changes to the major version number indicate a change that is not backwards compatible.  Changes to the minor version number indicated backwards-compatible improvements.  Changes to the patch number indicate a minor feature or fix.

The version number is included in the URL.  When the patch number is missing that refers to the most recent patch of that minor version.  When the minor version number is missing it refers to the most recent minor version of that major branch.  In theory it should be safe to always link to the most recent minor version.

Most Recent Version

Most Recent Feature Release

Most Recent Patch