shibori 1.0.0.beta1

data/public/data/annotations.js

@@ -0,0 +1,109 @@
+var comments = {
+"comments" : [
+	{
+		"el": "header[role=banner]",
+	 	"title" : "Masthead",
+	 	"comment": "The main header of the site doesn't take up too much screen real estate in order to keep the focus on the core content. It's using a linear CSS gradient instead of a background image to give greater design flexibility and reduce HTTP requests."
+	},
+	{
+		"el": ".logo",
+	 	"title" : "Logo",
+	 	"comment": "The logo image is an SVG file, which ensures that the logo displays crisply even on high resolution displays. A PNG fallback is provided for browsers that don't support SVG images.</p><p>Further reading: <a href=\"http://bradfrostweb.com/blog/mobile/hi-res-optimization/\">Optimizing Web Experiences for High Resolution Screens</a></p>"
+	},
+	{
+	 	"el": "#nav",
+	 	"title" : "Navigation",
+	 	"comment": "<p>Navigation for adaptive web experiences can be tricky. Top navigations are typical on desktop sites, but mobile screen sizes don't give us the luxury of space. We're dealing with this situation by creating a simple menu anchor that toggles the main navigation on small screens. This is just one method. <a href=\"http://bagcheck.com/\">Bagcheck</a> and <a href=\"http://contentsmagazine.com/\">Contents Magazine</a> add an anchor in the header that jumps users to the navigation which is placed in the footer. This solution works well because it doesn't require any Javascript in order to work. Other methods exist too. For example, <a href=\"http://m.espn.com\">ESPN's mobile navigation</a> overlays the main content of the page.</p><p>The nav is only hidden when a certain level of javascript is supported in order to ensure that users with little/poor javascript support can still access the navigation. Once the screen size is large enough to accommodate the nav, we show the main navigation links and hide the menu anchor.<p><p>See also: <a href=\"http://bradfrostweb.com/blog/web/responsive-nav-patterns/\">Responsive Navigation Patterns</a></p>"
+	},
+	{
+		"el": "input[type=search]",
+	 	"title" : "Search",
+	 	"comment": "<p>Search is an incredibly important priority, especially for mobile. It is a great idea to give users the ability to jump directly to what they are looking for without forcing them to wade through your site's navigation. Check out the <a href=\"http://burton.com\">Burton</a> and <a href=\"http://yelp.com\">Yelp</a> mobile sites for great examples of experiences that prioritize search.</p><p>We're also using the <a href=\"http://dev.w3.org/html5/markup/input.search.html\">HTML5 search input type</a>, which is great for mobile devices that can <a href=\"http://diveintohtml5.info/forms.html\">bring up the appropriate virtual keyboard</a> for many smartphones. And like the main header navigation, we're hiding the search form on small screens to save space. Clicking the search anchor toggles the form. </p>"
+	},
+	{
+		"el": "#product-img nav",
+	 	"title" : "Image Navigation",
+	 	"comment": "<p>Instead of providing bullets, pagination or text-based image navigation, it's good e-commerce practice to show a preview of the various product views. By default the images simply link through to their larger counterparts, and if adequate javascript support exists, the images get loaded into the main image container.</p>"
+	},
+	{
+		"el": "#img-container",
+	 	"title" : "Product Image",
+	 	"comment": "<p>The product image is the focal point of the page for good reason. It's typically what the user is there to see. The default markup simply includes the main product image, but that gets replaced with an image gallery if adequate javascript support exists.</p><p>We're also using <a href=\"http://www.modernizr.com/\">Modernizr</a> to detect if the browser supports <a href=\"https://developer.mozilla.org/en/DOM/Touch_events\">touch events</a> and if it does, we load in an excellent lightweight script called <a href=\"http://swipejs.com/\">Swipe.js</a> to create a touch-friendly image carousel. This allows users to swipe between product photos in a touch-friendly way. Because gestures are invisible, they might get overlooked, but clicking on the image navigation thumbnails animates the  slideshow and hints to the user gestural interaction is available.</p>"
+	},
+	{
+		"el": ".product-main header",
+	 	"title" : "Product Overview",
+	 	"comment": "The product overview appears in the markup before the image container in order to provide the user with the product name, how much it costs and how popular it is. Providing this information as soon as possible can help the user determine whether or not this is the product they're looking for without having to wait for the rest of the page to load."
+	},
+	{
+		"el": ".star",
+	 	"title" : "Rating Stars",
+	 	"comment": "<p>We're using HTML special characters to display the product rating stars. We're using HTML characters instead of images to reduce the amount of images we're requesting and also maintaining crispness on high resolution screens. Not every device supports HTML special characters (Blackberry <=5.0 for example), but support is strong enough and the benefits are many.</p><p>See also: <a href=\"http://bradfrostweb.com/blog/mobile/hi-res-optimization/\">Optimizing Web Experiences for High Resolution Screens</a></p>"
+	},
+	{
+		"el": ".review-count",
+	 	"title" : "Review Count",
+	 	"comment": "This is a simple anchor link that points to the review section of the page. This may seem like a small detail, but consider a mobile use case. Users can be in stores looking at the physical product, and <a href=\"http://googlemobileads.blogspot.com/2011/04/smartphone-user-study-shows-mobile.html\">79% of smartphone consumers use their phones to help with shopping</a>. They might be interested in buying in-store but turn to their phones to verify its popularity and quality. Making it easy for uses to read product reviews on small screens can help drive more sales, both online and offline.</p><p>While not incorporated yet, it would be easy to load the reviews for small screens on demand, thereby saving a step.</p>"
+	},
+	{
+		"el": ".qty-field",
+	 	"title" : "Quantity Field",
+	 	"comment": "We're using the HTML5 number input type, which <a href=\"http://diveintohtml5.info/forms.html\">brings up the appropriate virtual keyboard</a> for many mobile browsers. To increase usability, the input labels are using the \"for\" attribute, which focuses the cursor in the form field when clicked. However, iOS doesn't honor \"for\" default functionality, so we're adding \"cursor: pointer\" to the labels to get Mobile Safari to behave properly."
+	},
+	{
+		"el": ".size-field",
+	 	"title" : "Size Dropdown",
+	 	"comment": "We're using a basic select menu to choose the size, which is commonplace for any e-commerce site. Select menus can be especially difficult to style and can vary greatly in behavior between platforms. Keep this in mind when creating "
+	},
+	{
+		"el": ".submit-form",
+	 	"title" : "Add to Cart button",
+	 	"comment": "The add to cart button is the primary user action on the page. That's why it's large and in charge and very prominently placed on the page. The button is using box-shadows and rounded corners to create an attractive button that will hopefully get plenty of clicks."
+	},
+	{
+		"el": ".share-btn",
+	 	"title" : "Share button",
+	 	"comment": "It seems like everything has a share button on it these days. And for good reason. Sharing content and products on social networks can be a great way to increase exposure. However, tacking on tons of social widgets adds a lot of overhead, which can be extremely <a href=\"http://www.strangeloopnetworks.com/web-performance-optimization-hub/topics/third-party-content/\">detrimental to the site's performance</a>. Including a simple share link that loads the heavy widgets only when requested is one way to keep pages fast and social. Check out <a href=\"http://target.com\">Target's mobile site</a> for an example of a site that isolates share functionality in a separate page fragment."
+	},
+	{
+		"el": ".find-nearby",
+	 	"title" : "Geolocation",
+	 	"comment": "One of the most important aspects of the mobile context is location. We carry our mobile devices with us everywhere. Using <a href=\"http://dev.w3.org/geo/api/spec-source.html\">geolocation</a> we can tap into the user's location to deliver an enhanced experience. In this case we're giving them a chance to check out what stores nearby might sell this product. The geolocation API is well supported in mobile browsers as well as desktop browsers. We're using <a href=\"http://modernizr.com\">Modernizr</a> to detect for geolocation support and if its support, we ask the user for their latitude and longitude. If the browser does not support geolocation, the default experience could take the user to a simple web form asking for a ZIP code. Check out <a href=\"http://m.tiffany.com\">Tiffany's mobile site</a> store locator for an example of geolocation in action."
+	},
+	{
+		"el": "#p-desc",
+	 	"title" : "Product Description",
+	 	"comment": "A product description is an essential part of any e-commerce experience. Descriptions offer tangible details that inform and persuade, and the tone can help support the physical product. Provide relevant information clearly and concisely. Check out the <a href=\"http://developer.android.com/design/style/writing.html\">Android design guide</a> for some tips on how to keep copy short and extremely effective."	
+	},
+	{
+		"el": "#related-products",
+	 	"title" : "Related Products",
+	 	"comment": "<p>Related products are obviously an important aspect of e-commerce sites as they drive awareness of other similar products and can lead to more purchases. However, including a lot of auxiliary content can bog down the site performance, which is especially crucial on mobile. On slow connections, the presence of this extra content might slow down the user experience enough that the user gives up.</p><p>We're handling the issue by <a href=\"http://24ways.org/2011/conditional-loading-for-responsive-designs\">conditionally loading</a> the auxiliary content.</p><p>By default, the related item link simply clicks through to an HTML fragment containing the related products. The content is still accessible, even on devices with poor or no javascript support. When the user clicks on the related products on small screens, the content gets dynamically loaded inline and the link becomes a toggler for the content. Once the experience reaches a certain width breakpoint, we then load in the content. However, screen size != fast connection, so we should keep our eyes on the emerging <a href=\"http://davidbcalhoun.com/2010/using-navigator-connection-android\">navigator.connection</a> to better gauge real connection speed.</p><p>See also: <a href=\"http://filamentgroup.com/lab/ajax_includes_modular_content/\">An Ajax-Include Pattern for Modular Content</a></p><p>All these wonderful t-shirts are retired/rejected <a href=\"http://bustedtees.com\">Busted Tees</a>, graciously donated to this demo by <a href=\"http://www.willschneidblog.com/\">Will Schneider</a>.</p>"
+	},
+	{
+		"el": "#reviews",
+	 	"title" : "Reviews",
+	 	"comment": "Reviews are incredibly influential on a user's decision to purchase a product or pass on it. Also, because we carry our mobile phones with us everywhere, we use them to inform our in-store purchased. <a href=\"http://googlemobileads.blogspot.com/2011/04/smartphone-user-study-shows-mobile.html\">70% of smartphone owners use them while in brick and mortar stores</a>, and often times they're looking for reviews to give them the green light to buy.</p><p>Only the primary product content gets loaded by default, and the reviews exist as their own separate HTML fragment. The reviews remain accessible and don't get loaded until we <a href=\"http://24ways.org/2011/conditional-loading-for-responsive-designs\">conditionally load</a> them when the screen is large enough or small screen users click the reviews link.  This keeps things nimble while still providing access to the valuable reviews.</p><p>See also: <a href=\"http://filamentgroup.com/lab/ajax_includes_modular_content/\">An Ajax-Include Pattern for Modular Content</a></p>"
+	},
+	{
+		"el": "#p-reviews .btn",
+	 	"title" : "More Reviews Button",
+	 	"comment": "<p>All reviews aren't loaded by default in order to keep the site performance in top shape. Ultimately, this button could be replaced with a <a href=\"http://www.infinite-scroll.com/\">lazy-loading</a> solution to remove the need for the button.</p>"
+	},
+	{
+		"el": ".footer .nav",
+	 	"title" : "Footer Nav",
+	 	"comment": "<p>Repetition of elements isn't a bad thing, especially with potentially long scrolling pages on mobile. Providing access to the main site navigation is a good way for the user to jump off to another section and avoids leaving them with a dead end. Also, some mobile sites like <a href=\"http://bagcheck.com/\">Bagcheck</a> and <a href=\"http://contentsmagazine.com/\">Contents Magazine</a> keep the primary navigation at the footer and simply link to it with an anchor in the header. That way the nav stays accessible but the focus stays on on the core page content.</p>"
+	},
+	{
+		"el": ".tel",
+	 	"title" : "Customer Service Number",
+	 	"comment": "<p>We sometimes forget that <a href=\"http://bradfrostweb.com/blog/mobile/a-tel-tale-sign/\">mobile phones can make phone calls</a>. Whether a user is having trouble with the site or simply has some questions about the product he's about to buy, it's a smart decision to provide a clickable phone number to facilitate that call. What happens when desktops and other non-phone devices click on the <a href=\"http://www.mobilexweb.com/blog/click-to-call-links-mobile-browsers\">tel link</a>? Well, some devices (like iPads and other tablets) ask the user if they'd like to add the number to their contact list, other desktops open 3rd party VoIP programs like Skype, and others simply give an error message.</p>"
+	},
+	{
+		"el": ".top",
+	 	"title" : "Back to Top Link",
+	 	"comment": "<p>Back to top links are simple yet underrated. They provide users with an easy way back up to the top of the page with minimum effort. This is especially helpful on mobile devices, which tend to have long scrolling pages.</p><p>We're using an HTML character for the back to top arrow in order to reduce image elements and keep things looking crisp on high res displays.</p>"
+	}
+]
+};

data/public/styleguide/css/static.css

@@ -0,0 +1,458 @@
+@charset "UTF-8";
+/*
+colors
+red: $orange; rgb(229,24,55)
+gray: #808080;
+*/
+/************Reset**************/
+* {
+  -moz-box-sizing: border-box;
+  -webkit-box-sizing: border-box;
+  box-sizing: border-box;
+}
+
+html, body, div, object, iframe, fieldset {
+  margin: 0;
+  padding: 0;
+  border: 0;
+}
+
+ol, ul {
+  list-style: none;
+  margin: 0;
+  padding: 0;
+}
+
+table {
+  border-collapse: collapse;
+  border-spacing: 0;
+}
+
+header, footer, nav, section, article, hgroup, figure {
+  display: block;
+}
+
+legend {
+  display: none;
+}
+
+/************End Reset**************/
+/************Global**************/
+body {
+  background: #fff;
+  color: #000;
+  font: 100%/1.4 "HelveticaNeue", "Helvetica", "Arial", sans-serif;
+  padding: 0;
+  -webkit-text-size-adjust: 100%;
+  border-top: 20px solid #000;
+  border-bottom: 20px solid #000;
+}
+
+a {
+  color: #808080;
+  text-decoration: none;
+}
+
+a:hover, a:focus {
+  color: #bededf;
+}
+
+p {
+  margin: 0 0 1em;
+}
+
+img, object, video {
+  max-width: 100%;
+  border: 0;
+}
+
+a img {
+  border: 0;
+  outline: 0;
+}
+
+h1 {
+  font-size: 3em;
+  line-height: 1;
+  letter-spacing: -0.02em;
+  margin-bottom: 0.2em;
+}
+
+h2 {
+  font-size: 2em;
+  line-height: 1.1;
+  margin-bottom: 0.2em;
+}
+
+h3 {
+  font-weight: normal;
+  line-height: 1.1;
+  padding-bottom: 0.4em;
+  border-bottom: 1px solid #ccc;
+}
+
+h1 a, h2 a, h3 a {
+  display: block;
+  color: #000;
+}
+
+h1 a:hover, h2 a:hover, h3 a:hover {
+  color: #bededf;
+}
+
+blockquote {
+  border-left: 0.5em solid #ddd;
+  padding-left: 1em;
+  margin-left: 1em;
+}
+
+small {
+  color: #bededf;
+}
+
+input[type=search] {
+  -webkit-appearance: none;
+  border-radius: 0;
+}
+
+::-webkit-input-placeholder {
+  color: #808080;
+}
+
+:-moz-placeholder {
+  color: #808080;
+}
+
+/************End Global**************/
+/************Classes**************/
+.inactive {
+  color: #ddd;
+}
+
+/************End Classes**************/
+/************Structure**************/
+.container {
+  max-width: 60em;
+  margin: 0 auto;
+  padding: 0 1em;
+  overflow: hidden;
+}
+
+[role=main] {
+  padding-bottom: 1em;
+}
+
+/*Footer*/
+[role=contentinfo] {
+  color: #fff;
+  background: #000;
+  margin: 0 -1em;
+  position: relative;
+  z-index: 2;
+}
+
+[role=contentinfo] > div {
+  max-width: 60em;
+  padding: 0 1em;
+  margin: 0 auto;
+  overflow: hidden;
+}
+
+/*End Footer*/
+/*Grid*/
+.grid {
+  margin: 0 -1em;
+  overflow: hidden;
+}
+
+.grid:target {
+  -webkit-animation: fadeout 5s 1 ease-out;
+  -moz-animation: fadeout 5s 1 ease-out;
+  -o-animation: fadeout 5s 1 ease-out;
+  animation: fadeout 5s 1 ease-out;
+}
+
+.grid > h2 {
+  margin-left: 0.45em;
+}
+
+.grid > section {
+  padding: 1em 1em 0.5em;
+}
+
+.grid > section:target {
+  -webkit-animation: fadeout 5s 1 ease-out;
+  -moz-animation: fadeout 5s 1 ease-out;
+  -o-animation: fadeout 5s 1 ease-out;
+  animation: fadeout 5s 1 ease-out;
+}
+
+.grid ul {
+  overflow: hidden;
+}
+
+.grid ul li {
+  margin-bottom: 0.3em;
+}
+
+.featured:after {
+  content: "*";
+  color: #bededf;
+}
+
+/*Fluid*/
+.fluid {
+  display: block;
+  margin: 0 auto;
+  max-width: 40em;
+}
+
+/*Homepage*/
+.home h1 {
+  margin-bottom: 0.2em;
+}
+
+.intro {
+  font-size: 1.8em;
+  line-height: 1.2;
+  margin: 0 auto;
+}
+
+.intro a:hover, .intro a:focus {
+  color: #000;
+  border-bottom-color: #000;
+}
+
+.ani {
+  position: relative;
+  height: 15em;
+  margin: 1em 0 0;
+  width: 100%;
+  z-index: 0;
+}
+
+.ani div {
+  width: 100%;
+}
+
+.ani div b {
+  display: block;
+  position: absolute;
+  top: 5%;
+  right: 5%;
+  bottom: 5%;
+  left: 5%;
+  background: rgba(229, 24, 55, 0.22);
+}
+
+/*Patterns*/
+.mod {
+  padding: 1em;
+}
+
+.pattern {
+  background: #f7f7f7;
+  border-bottom: 1px solid #808080;
+  margin-bottom: 1em;
+  overflow: hidden;
+}
+
+.pattern-description h1 {
+  font-size: 3.4em;
+  margin-bottom: 0.5em;
+}
+
+.pattern-description {
+  max-width: 40em;
+  margin: 0 auto;
+}
+
+.pattern-description ul, .pattern-description ol {
+  margin-bottom: 2em;
+}
+
+.pattern-description li {
+  margin-bottom: 1em;
+}
+
+/*Blog*/
+/*Blog Header*/
+.blog .container {
+  max-width: 62em;
+}
+
+.blog header[role=banner] {
+  overflow: hidden;
+  margin-bottom: 2em;
+  padding: 2em 0 1em;
+  border-bottom: 1px solid #000;
+}
+
+.blog-logo {
+  font-weight: normal;
+  font-size: 1.2em;
+  margin: 0 0 1em;
+}
+
+.blog-logo img {
+  width: 3.3em;
+}
+
+.blog-logo a {
+  color: #000;
+}
+
+.search-form {
+  width: 100%;
+  margin-bottom: 1em;
+}
+
+.search-field {
+  width: 100%;
+  padding: 0.5em 0;
+  border: 0;
+  border-bottom: 1px solid #808080;
+  outline: none;
+}
+
+.search-field:focus {
+  background: #bededf;
+  color: #fff;
+}
+
+.search-field:focus::-webkit-input-placeholder {
+  color: #fff;
+}
+
+.search-field:focus :-moz-placeholder {
+  color: #fff;
+}
+
+.blog .nav {
+  clear: both;
+}
+
+.blog .nav a {
+  display: block;
+  font-weight: bold;
+  color: #000;
+}
+
+.blog .nav a:hover {
+  color: #bededf;
+}
+
+/*Posts*/
+.posts ol > li {
+  padding-bottom: 1em;
+  border-bottom: 1px solid #ccc;
+  margin-bottom: 1em;
+  overflow: hidden;
+}
+
+.posts h2 {
+  font-size: 1.4em;
+  margin: 0.28em 0 0.1em;
+  font-weight: normal;
+}
+
+.posts h2 a {
+  color: #000;
+}
+
+.posts h2 a:hover, .posts h2 a:focus {
+  color: #bededf;
+}
+
+.permalink {
+  display: block;
+  font-size: 0.8em;
+  margin-bottom: 1.2em;
+}
+
+.post-body a {
+  border-bottom: 1px solid #ccc;
+}
+
+.posts blockquote {
+  margin: 0 0 1em;
+  color: #666;
+  border-left: 0.25em solid #ccc;
+  padding-left: 1em;
+}
+
+.tags {
+  float: left;
+}
+
+.tags li {
+  display: inline-block;
+  font-size: 0.8em;
+  margin-right: 0.5em;
+}
+
+.posts ol > li .tags a, .permalink {
+  color: #ccc;
+  -webkit-transition: color 0.3s ease-out;
+  -moz-transition: color 0.3s ease-out;
+  -ms-transition: color 0.3s ease-out;
+  -o-transition: color 0.3s ease-out;
+  transition: color 0.3s ease-out;
+}
+
+.posts ol > li:hover .tags a, .posts ol > li:hover .permalink {
+  color: #808080;
+}
+
+.blog-nav {
+  text-align: center;
+  overflow: hidden;
+  padding: 1em 0;
+}
+
+.posts .blog-nav a {
+  border: 0;
+}
+
+.nav-next {
+  float: right;
+}
+
+.nav-prev {
+  float: left;
+}
+
+/* Sidebar */
+.sidebar {
+  font-size: 0.8em;
+  padding-bottom: 1.4em;
+}
+
+.sidebar div {
+  margin-bottom: 2em;
+}
+
+.sidebar h3 {
+  font-weight: bold;
+  font-size: 0.9em;
+  line-height: 1;
+  border-bottom: 1px solid #000;
+}
+
+.sidebar a {
+  color: #808080;
+}
+
+.sidebar a:hover, .sidebar a:focus {
+  color: #bededf;
+}
+
+.top {
+  clear: both;
+  display: block;
+  padding: 1em 0;
+}
+
+.top:before {
+  content: '▲';
+}