Case Studies

Here are some examples of websites that implement specific Boss features, which we thought you might find interesting.

Product Lists

www.openshutters.com.au

One feature of the Boss.Cart module is the ability for website visitors to create and save lists of products, according to how the feature is implemented on the particular site.

Open Shutters wanted to provide its sales team and their website visitors with a tool to let them mix and match different shutter features, examples, and styles to create a pinboard that gave a feel of what they liked and wanted to achieve. The pinboard can then be emailed or shared via social media sites, providing Open Shutters with a unique way of showcasing both their flexibility and their portfolio.

In this example Product Lists were implemented without the use of the shopping cart (there isn't actually a checkout process on the site), however they could used for a wedding register, wish list or whatever else you might imagine.

Scriptable Shopping

www.astrolabewines.co.nz

The template API system allows for highly customisable shopping cart experiences.

There are some defaults which can be helpful if you want us to roll a website out fast, but if you wanted an entire shopping experience on one page driven fully by dynamic JavaScript (we're building such a demo in our spare time), it's possible.

The Astrolabe Wines site hints at some of those capabilities with some AJAX based actions to smooth the shopping experience.

Responsive Design

www.stableproperty.co.nz

A good example of a responsive Boss site. To see the responsiveness in action, visit the site and resize your browser window slowly down to cell phone size (if you're on a mobile device this isn't so easy).

In a true sense this isn't a "Boss Feature". But it is a good illustration of the way Boss gets out of the way of the design process and allows for whatever web design/build practice is currently in vogue. The Boss system design was crafted before "Responsive Sites" existed as a concept.
The Verb website is currently also a good example of such responsiveness.

Content Variations

www.ourconstitution.org.nz

Content Variations means that one website can appear as multiple different sites, with major or minor variations of content. This is handy for sites with multiple languages, or where a single website needs to display under multiple brands.

When the New Zealand Government wanted to consult the NZ public on their Constitution, the resulting website was required to present in both the Māori and English languages.

Content Variations trigger off either a domain or a prefix. The prefix model works as follows:

  • .../How-to-make-a-Submission (presents in English)
  • .../mi/How-to-make-a-Submission (presents in Māori)

From a content management perspective, there is only one page structure, and page content can be assigned as global, default, or assigned to a Variation. Each page can have multiple versions that relate to each available variation. This allows for easy site-wide adjustments, content management and robust execution.

Alternative uses could include:

  • Franchises who want to run slightly different content for each franchise but work with a single site structure.
  • Sales sites targeted at different audiences with differing content but the same structure.