This is a really solid framework. A couple of humble suggestions:
1. Package up your site itself on github as one of the examples. Mixing up some elements of your base site with some of the landing bits would make for a solid base for a lot of people.
2. Get a compatibility table together stat. To help you out, I did a quick test of both your main site and the landing page. Nothing in depth, just the basics. The following browsers worked properly:
On Windows (8.1 unless noted):
Firefox Stable 34.0.5
Firefox ESR 31.3.0
Opera 26.0.1656.32
Google Chrome Stable 39.0.2171.95
Internet Explorer 11
Internet Explorer 10 (Windows 7)
Internet Explorer 9 (Windows Vista)
On Ubuntu 14.0.4:
Firefox Stable 34.0
Chromium 39.0.2171.65
Google Chrome 39.0.2171.95
On Android 4.4:
Google Chrome 39.0.2171.93 (both landscape and portrait, phone and tablet)*
Firefox 34.0 (both landscape and portrait, phone and tablet)*
* Note that the UI navbar didn't stick on the phone for either browser despite the phone having a 1920x1080 resolution vs the tablet's 1024x768 resolution. I think this is by design on your end
The following browsers did not work properly:
Windows XP - Internet Explorer 7 and 8 - Failed to load custom images at top hero secion (custom CSS not contained in skeleton), alignment issues of buttons, full nav list visible (not part of skeleton issues), example grid completely broken (shows as full width divs), very broken visually but still usable
Windows XP - Internet Explorer 6 - issues above plus more visual issues. semi-usable
This is awesome! Browser chart more than just a quick list might be nice. Adding it as an outstanding issue to my long list of improvements. Appreciate the feedback!
You're welcome. Based on my testing, I think you don't even really need a detailed chart, just a compatibility list. You'd be safe listing it as compatible with:
Mozilla Firefox (desktop and mobile)
Google Chrome (desktop and mobile)
Chromium
Internet Explorer 9 and later
Opera (desktop and mobile)
Safari (desktop and mobile) [this is an almost-positive guess but test to be sure]
You could then work backwards a bit on version numbering, trying older versions until you see where it breaks. You could put Firefox 31+ for now (since I tested 31 ESR), but that would be misleading since I'd wager it works quite a ways back on Firefox. Same with Chrome, Opera, and Safari. You could even just leave those versions off as users generally have the latest version of Firefox, Chrome, and Opera. Safari is another story since it's OS-tied like IE is, so you have a lot more users using an outdated version of desktop Mac OS X's Safari than outdated Firefox or Chrome users on the same OS versions. Leopard users are stuck on Safari 5.0.6 and Lion users are stuck on Safari 6.1. If you can get your hands on really just those two versions to double check, you'd be set and could list it as Safari 5+.
I may test back a bit as I'm playing with using Skeleton for an older site using Drupal with a single-page theme. I can drop you a note if I do.
1. Package up your site itself on github as one of the examples. Mixing up some elements of your base site with some of the landing bits would make for a solid base for a lot of people.
2. Get a compatibility table together stat. To help you out, I did a quick test of both your main site and the landing page. Nothing in depth, just the basics. The following browsers worked properly:
On Windows (8.1 unless noted):
Firefox Stable 34.0.5
Firefox ESR 31.3.0
Opera 26.0.1656.32
Google Chrome Stable 39.0.2171.95
Internet Explorer 11
Internet Explorer 10 (Windows 7)
Internet Explorer 9 (Windows Vista)
On Ubuntu 14.0.4:
Firefox Stable 34.0
Chromium 39.0.2171.65
Google Chrome 39.0.2171.95
On Android 4.4:
Google Chrome 39.0.2171.93 (both landscape and portrait, phone and tablet)*
Firefox 34.0 (both landscape and portrait, phone and tablet)*
* Note that the UI navbar didn't stick on the phone for either browser despite the phone having a 1920x1080 resolution vs the tablet's 1024x768 resolution. I think this is by design on your end
The following browsers did not work properly:
Windows XP - Internet Explorer 7 and 8 - Failed to load custom images at top hero secion (custom CSS not contained in skeleton), alignment issues of buttons, full nav list visible (not part of skeleton issues), example grid completely broken (shows as full width divs), very broken visually but still usable
Windows XP - Internet Explorer 6 - issues above plus more visual issues. semi-usable