There are a few technical detailed for making sure zingFit production starts
off on the right foot:

Bootstrap Framework

The zingFit CMS and online scheduling system make use of the Twitter Bootstrap framework.

zingFit requires that all HTML code delivered by developers include the css of the Bootstrap framework version listed below so that those developers can work out any necessary overrides.

Bootstrap 2.3.1 CDN links

  • //
  • //
  • //
PLEASE NOTE: Developers are free to deliver code built using other frameworks, including more recent versions of Bootstrap, however, these Bootstrap 2.3.1 CSS and JS CDN links must be included in the document header so that any and all necessary overrides are implemented by the developer team.

Delivery of Assets

Where zingFit will be acting as web developer and producing the website HTML, zingFit requires that designers deliver the website assets according to the following terms:


All content should be delivered in a single file, either as plain text, or in Microsoft Word format.

Style Guide

Developers should provide a document outlining:

  • general font usage and colors
  • titles
  • headers
  • paragraphs
  • footers
  • navigation
  • buttons
  • forms
  • and other elements


The designer/developer must work out terms web licensing for all fonts. Fonts should be either included with the final design package (desktop AND web fonts), or in the case of web fonts, the designer can specify from which web font repository the fonts are to be sourced (Google fonts, Typekit, etc). zingFit can and most often does setup and maintain the font repository accounts and then bill clients accordingly on a monthly or yearly basis for font licensing.


All images should be web optimized and all licensing should be purchased for website usage.

Mobile Scheduling

Please refer to the mobile page for guidance on graphic assets required for optimal mobile experience for studio customers.

Please refer to the sign-in kiosk page for guidance on graphic assets required to create a self-sign-in kiosk.


Designs should be delivered as layered Photoshop files (no Illustrator files please other than logos). Ideally, all elements such as backgrounds, icons and sprites would be extracted and provided as separate web optimized files.

Designers should specify how the design will render on a 1900px screen. For example, will headers and footers extend the whole length of the screen or stay within a fixed width container. Or will the site render as a liquid layout?


Developers should take care in outlining design layouts for each reponsive break that is architected in the design. Most often, zingFit requires, at the very least, a design for the mobile header and footer including accommodation for navigation axes.

Specify whether the site should respond responsively on the desktop at different screen widths, as well as be optimized for tablets and mobile devices.


Interactivity should be specified explicity using Photoshop layers, wireframe call-outs, and general expository explanation for hover/active states, slideshows/video, animation effects, hide/show divs etc.