Permalink
Browse files

Merge pull request #28 from retlehs/gh-pages

Don't make the pugs cry.
  • Loading branch information...
2 parents e3d1fcf + 92fad2e commit 28c3fb7e3a85bfc07cc810ef9b0aee756404c2ac @bobthecow bobthecow committed Dec 11, 2012
View
@@ -68,7 +68,7 @@ <h2>Page Not Found (404)</h2>
<h2 class="hfd">Community links</h2>
<ul id="places">
<li data-alt="Follow us on Twitter"><a rel="external" href="https://twitter.com/Modernizr" class="icon twitter">Follow us on Twitter</a></li>
- <li data-alt="Contribute on github"><a rel="external" href="https://github.com/Modernizr/Modernizr" class="icon github">Contribute on github</a></li>
+ <li data-alt="Contribute on GitHub"><a rel="external" href="https://github.com/Modernizr/Modernizr" class="icon github">Contribute on GitHub</a></li>
<li data-alt="Subscribe with RSS"><a rel="external" href="http://feeds.feedburner.com/Modernizr" class="icon rss">Subscribe with RSS</a></li>
<li data-alt="Donate to Modernizr" class="donate"><a href="#donate" class="icon" id="donateLink">Donate to Modernizr</a></li>
<li class="hide-if-js"><input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_SM.gif" name="submit" alt="Love Modernizr? Donate to help the project!"></li>
View
@@ -3,7 +3,7 @@
<h2 class="hfd">Community links</h2>
<ul id="places">
<li data-alt="Follow us on Twitter"><a rel="external" href="https://twitter.com/Modernizr" class="icon twitter">Follow us on Twitter</a></li>
- <li data-alt="Contribute on github"><a rel="external" href="https://github.com/Modernizr/Modernizr" class="icon github">Contribute on github</a></li>
+ <li data-alt="Contribute on GitHub"><a rel="external" href="https://github.com/Modernizr/Modernizr" class="icon github">Contribute on GitHub</a></li>
<li data-alt="Subscribe with RSS"><a rel="external" href="http://feeds.feedburner.com/Modernizr" class="icon rss">Subscribe with RSS</a></li>
<li data-alt="Donate to Modernizr" class="donate"><a href="#donate" class="icon" id="donateLink">Donate to Modernizr</a></li>
<li class="hide-if-js"><input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_SM.gif" name="submit" alt="Love Modernizr? Donate to help the project!"></li>
@@ -32,7 +32,7 @@ Yes, under HTML5—which is what Modernizr is meant to be used under—it is per
**Additional note:**<br />
Modernizr 1.0 also checks for (and if found, removes) the class `no-js` from the `html` element. In its place, it adds the class `js`, which means that if you start your templates with the code `<html class="no-js">` and then include the Modernizr library, you can use the classes `.no-js` and `.js` to respectively determine whether JavaScript is disabled or enabled in the browser.
-**Will Modernizr go on Github / Bitbucket / similar now that it is 1.0?**<br />
+**Will Modernizr go on GitHub / Bitbucket / similar now that it is 1.0?**<br />
Yes, very soon it will get hosted on a public repository so that people can contribute a little more directly. We haven't decided yet which one, but no new releases will be made until it's hosted publicly.
**What do you have planned for the next release?**<br />
@@ -1,16 +1,16 @@
---
layout: post
-title: Modernizr, meet Github
+title: Modernizr, meet GitHub
author: <a href="http://farukat.es/">Faruk Ateş</a>
---
-When Modernizr was originally released in July, requests came in right away for seeing it hosted on code repositories like <a href="http://code.google.com/hosting/">Google Code</a> or <a href="http://github.com/">Github</a>. The promise at the time was: "once it goes 1.0".
+When Modernizr was originally released in July, requests came in right away for seeing it hosted on code repositories like <a href="http://code.google.com/hosting/">Google Code</a> or <a href="http://github.com/">GitHub</a>. The promise at the time was: "once it goes 1.0".
We had only one real reason for not doing so right away: the choice of which public repository service to use. At the time, Modernizr's code base was created and managed pretty much solely by myself, and my experience with these repositories was pretty limited. I didn't want to commit to one only to realize halfway through the next release that I preferred another.
Well, Modernizr has since <a href="http://www.modernizr.com/news/modernizr-goes-1-0">gone 1.0</a> and not only that, but the project has a new code lieutenant. <a href="http://paulirish.com/">Paul Irish</a> will take on the role of governing Modernizr's codebase, with me taking a slightly more backseat spot in overseeing the general direction of the project. In other words, I'll play a more directorial role whilst Paul will deal with the specifics of the library's codebase.
Paul's skill and talent is already widely recognized and we feel he is a great fit for the role of code lieutenant for Modernizr.
-His first assignment was to choose a code repository he felt most appropriate for Modernizr. We discussed the various pros and cons with regards to our needs (codebase, feedback, support tickets and so on) and what each service provides, and the choice has settled on: **<a href="http://github.com/">Github</a>**.
+His first assignment was to choose a code repository he felt most appropriate for Modernizr. We discussed the various pros and cons with regards to our needs (codebase, feedback, support tickets and so on) and what each service provides, and the choice has settled on: **<a href="http://github.com/">GitHub</a>**.
-In the coming days, Modernizr will start living on Github and the Modernizr.com site will be updated to direct visitors there instead. Once there, everyone will be able to contribute to and work on Modernizr directly, making the library even better. Meanwhile, please welcome Paul as formal code lieutenant.
+In the coming days, Modernizr will start living on GitHub and the Modernizr.com site will be updated to direct visitors there instead. Once there, everyone will be able to contribute to and work on Modernizr directly, making the library even better. Meanwhile, please welcome Paul as formal code lieutenant.
@@ -1,6 +1,6 @@
---
layout: post
-title: Github'd
+title: GitHub'd
author: <a href="http://farukat.es/">Faruk Ateş</a>
---
-Just a quick announcement that <a href="http://github.com/Modernizr/Modernizr">Modernizr is now available on Github</a>. Hack away!
+Just a quick announcement that <a href="http://github.com/Modernizr/Modernizr">Modernizr is now available on GitHub</a>. Hack away!
@@ -4,7 +4,7 @@ title: This holiday season, give the gift of progressive enhancement with Moder
author: <a href="http://farukat.es/">Faruk Ateş</a>
---
-We&rsquo;re delighted to bring you <a href="http://www.modernizr.com/releases/#release-1.1">Modernizr 1.1</a>, a handy upgrade to the increasingly popular HTML5 and CSS3 detection toolkit. Now that <a href="http://github.com/Modernizr/Modernizr">Modernizr is on Github</a> we&rsquo;re seeing contributions come in for additional features from many different people. We want to express special thanks to Remy Sharp, Mike Taylor, Jan Lehnardt, Fearphage and Ms2ger for their work pushing Modernizr forward.&nbsp;
+We&rsquo;re delighted to bring you <a href="http://www.modernizr.com/releases/#release-1.1">Modernizr 1.1</a>, a handy upgrade to the increasingly popular HTML5 and CSS3 detection toolkit. Now that <a href="http://github.com/Modernizr/Modernizr">Modernizr is on GitHub</a> we&rsquo;re seeing contributions come in for additional features from many different people. We want to express special thanks to Remy Sharp, Mike Taylor, Jan Lehnardt, Fearphage and Ms2ger for their work pushing Modernizr forward.&nbsp;
All of us who work on and contribute to Modernizr feel that it is _the_ best way to start taking advantage of HTML5 and CSS3 in your websites today, which is why this new release covers even more ground of both specifications. We&rsquo;re heading towards supporting absolutely everything from the next generation of web technologies that is being implemented by any of the major browsers today, so that you as a developer know what you can _and can&rsquo;t_ expect from your visitors&rsquo; browser.
@@ -6,7 +6,7 @@ author: <a href="http://farukat.es/">Faruk Ateş</a>
As you've undoubtedly noticed, it's been relatively quiet on the Modernizr front from our side, with no news or new releases since the start of the year. Nonetheless, everyone else has started getting more and more busy _using_ Modernizr to enhance their sites without sacrificing control over older browsers. Progressive Enhancement is becoming increasingly commonplace and we couldn't be more excited about that.
-So where do things stand? Well, we've been working, <a href="http://github.com/Modernizr/Modernizr">over on Github</a>, at getting the next release of Modernizr ready, version 1.2. We're not quite there yet, but we are setting a planned release date of **Thursday, April 22**. Every time we're almost there another new feature or issue pops up that we have a hard time excluding from the next release, but it's more important to iterate regularly than do big pushes for a tool like this.
+So where do things stand? Well, we've been working, <a href="http://github.com/Modernizr/Modernizr">over on GitHub</a>, at getting the next release of Modernizr ready, version 1.2. We're not quite there yet, but we are setting a planned release date of **Thursday, April 22**. Every time we're almost there another new feature or issue pops up that we have a hard time excluding from the next release, but it's more important to iterate regularly than do big pushes for a tool like this.
Related to all this has been an increasing effort towards realigning Modernizr; the site isn't what it could and should be, the community around Modernizr isn't as cohesive yet which leads to fragmented and overlapping efforts in promoting the tool, and the explanation of what Modernizr is and how it works is still lacking. Clearly, lots of room for improvement&mdash;and we're not just aware of it, we're working to fix it.
@@ -18,7 +18,7 @@ Early on, before Modernizr was released yet, my friend <a href="http://www.mkrie
Then we realized that this brought about a _ton_ of complexity, far too much for the introduction of the library. So, we dropped that idea and instead focused on making a simple, easy to use toolkit without any complexity in how to get it: just download it, include it and you're set.
-Well, turns out that the idea itself wasn't a _bad_ one, it was just too ahead of its time. As the Modernizr library grew its feature-set, it also grew its footprint and execution time. Thanks to the talents of <a href="http://paulirish.com/">Paul</a> and the many contributors committing code over on Github, it has stayed incredibly lean and fast&mdash;but also at the cost of things we'd really like to add, like SVG.
+Well, turns out that the idea itself wasn't a _bad_ one, it was just too ahead of its time. As the Modernizr library grew its feature-set, it also grew its footprint and execution time. Thanks to the talents of <a href="http://paulirish.com/">Paul</a> and the many contributors committing code over on GitHub, it has stayed incredibly lean and fast&mdash;but also at the cost of things we'd really like to add, like SVG.
SVG is an oft-requested feature for Modernizr to test against, and we really want to add it. But, to do it right would involve doing not just a basic one-line test against something like "window.SVG"&mdash;no, you have to do a very large number of tests so you can accurately report what parts of SVG the browser supports. To add that to Modernizr right now would bloat the library and slow it down, even though most users won't make use of it.
@@ -23,9 +23,9 @@ Rather than an incremental upgrade, we've opted to shift into a higher gear and
Then came the discovery that Google Chrome implemented <a target="_blank" href="http://www.quirksmode.org/mobile/tableTouch.html">Touch events</a> even on the desktop (why, Google, why?) paired with the regrettable fact that Palm's WebOS browser _doesn't support common Touch events at all_. For a browser that only exists on touch-based devices, this was too critical an issue for us to ignore. So Touch testing went out again, too.
-We have many more features we'd like to include; please visit the <a href="http://github.com/Modernizr/Modernizr/issues/#list">Github issue tracker</a> to review all the additional tests.
+We have many more features we'd like to include; please visit the <a href="http://github.com/Modernizr/Modernizr/issues/#list">GitHub issue tracker</a> to review all the additional tests.
-For developers, contributors and people looking to learn from Modernizr we now have a set of <a target="_blank" href="http://github.com/Modernizr/Modernizr/tree/master/test/">unit tests available on the Github repository</a>, courtesy of Paul. These help prevent errors and inconsistencies from finding their way into the source code, making Modernizr more robust and reliable. The unit tests also include a second part, which pulls the data tables in from <a target="_blank" href="http://findmebyip.com/">Find Me By IP</a> and creates a feature parity overview for all the browsers.
+For developers, contributors and people looking to learn from Modernizr we now have a set of <a target="_blank" href="http://github.com/Modernizr/Modernizr/tree/master/test/">unit tests available on the GitHub repository</a>, courtesy of Paul. These help prevent errors and inconsistencies from finding their way into the source code, making Modernizr more robust and reliable. The unit tests also include a second part, which pulls the data tables in from <a target="_blank" href="http://findmebyip.com/">Find Me By IP</a> and creates a feature parity overview for all the browsers.
Along with the 1.5 release comes a license upgrade: Modernizr is now <a href="/license/">dual-licensed under BSD and MIT</a>.
@@ -4,7 +4,7 @@ title: Modernizr 1.7 changelog
author: Team Modernizr
---
-We put 1.7 live some time ago but never got around to publishing a changelog. Since people have been asking, below are the core changes. For an exact changelog, see the <a href="https://github.com/Modernizr/Modernizr/compare/v1.6...v1.7">commit log on github between 1.6 and 1.7</a>.
+We put 1.7 live some time ago but never got around to publishing a changelog. Since people have been asking, below are the core changes. For an exact changelog, see the <a href="https://github.com/Modernizr/Modernizr/compare/v1.6...v1.7">commit log on GitHub between 1.6 and 1.7</a>.
At the heart of 1.7 are the following major changes:
@@ -16,4 +16,4 @@ At the heart of 1.7 are the following major changes:
Beyond these main changes, 1.7 fixes lots of small bugs like tiny memory leaks and the occasional false returns in certain browsers.&nbsp;
-A small update on the Modernizr 2 front: we&rsquo;re getting very close to releasing it, so if you encounter any major bugs using either 1.7 or the <a href="http://modernizr.github.com/Modernizr/2.0-beta/">2.0 beta builder</a>, please <a href="https://github.com/Modernizr/Modernizr/issues">report them on github</a>&nbsp;as soon as possible. We already have a lot of issues and features pushed to our planned 2.1 release, but would love to make sure that the 2.0 release is the absolute best version of Modernizr yet.
+A small update on the Modernizr 2 front: we&rsquo;re getting very close to releasing it, so if you encounter any major bugs using either 1.7 or the <a href="http://modernizr.github.com/Modernizr/2.0-beta/">2.0 beta builder</a>, please <a href="https://github.com/Modernizr/Modernizr/issues">report them on GitHub</a>&nbsp;as soon as possible. We already have a lot of issues and features pushed to our planned 2.1 release, but would love to make sure that the 2.0 release is the absolute best version of Modernizr yet.
@@ -6,7 +6,7 @@ author: Modernizr
Sometimes, members of the team get asked how we ascertain and verify that the features we detect are accurately detected. It’s not always a simple process, but over time we’ve put together a test suite that helps us out a lot.
-Paul has recorded a screencast discussing how this test suite for Modernizr was built. The brief summary: initially built with QUnit, the test suite has coverage over the full API surface area of Modernizr, even using kangax’s <a href="https://github.com/kangax/detect-global">detect-global</a> script to assure no globals are introduced beyond `Modernizr` and `yepnope`. After that it gets interesting—as verifying the results from Modernizr’s detection of the current browser’s features isn’t straightforward. We end up using APIs from both Caniuse.com and Github, using projects like Lloyd Hilaiel’s <a href="http://jsonselect.org/">JSONSelect</a>, Lindsey Simon's <a href="https://github.com/tobie/ua-parser">ua-parser</a> (ported to Node by <a href="http://twitter.com/tobie">@tobie</a>), some ES5 polyfills, and some real sexy jQuery Deferred action to elegantly handle a bunch of `$.getScript` calls.
+Paul has recorded a screencast discussing how this test suite for Modernizr was built. The brief summary: initially built with QUnit, the test suite has coverage over the full API surface area of Modernizr, even using kangax’s <a href="https://github.com/kangax/detect-global">detect-global</a> script to assure no globals are introduced beyond `Modernizr` and `yepnope`. After that it gets interesting—as verifying the results from Modernizr’s detection of the current browser’s features isn’t straightforward. We end up using APIs from both Caniuse.com and GitHub, using projects like Lloyd Hilaiel’s <a href="http://jsonselect.org/">JSONSelect</a>, Lindsey Simon's <a href="https://github.com/tobie/ua-parser">ua-parser</a> (ported to Node by <a href="http://twitter.com/tobie">@tobie</a>), some ES5 polyfills, and some real sexy jQuery Deferred action to elegantly handle a bunch of `$.getScript` calls.
20 minutes of javascript and feature detection action below.
@@ -8,7 +8,7 @@ Modernizr 2.0 came out more than eight months ago; we’ve not sat still in the
<h4 id="newin2.5">New in 2.5</h4>
-The <a href="https://github.com/Modernizr/Modernizr/compare/v2.0.6...v2.5.1">list of new things in 2.5</a> is too big for Github to handle, but here are the highlights:
+The <a href="https://github.com/Modernizr/Modernizr/compare/v2.0.6...v2.5.1">list of new things in 2.5</a> is too big for GitHub to handle, but here are the highlights:
* More than 60 new feature detects for emerging browser features; check out <a href="https://gist.github.com/783522a92b79a0868532">the full list</a> or peruse **all** of the community-driven tests in our <a href="https://github.com/Modernizr/Modernizr/tree/master/feature-detects">feature-detects folder</a>.
* We now have a super robust and integrated <a href="http://modernizr.github.com/Modernizr/test/index.html">test suite</a>. Paul did a great video <a href="http://www.youtube.com/watch?feature=player_embedded&amp;v=Mbt6h1BFW8g">detailing how it works</a>.
@@ -23,7 +23,7 @@ The <a href="https://github.com/Modernizr/Modernizr/compare/v2.0.6...v2.5.1">lis
* `Modernizr._domPrefixes` has been renamed to `Modernizr._cssomPrefixes`, and a new, lower-case `Modernizr._domPrefixes` has been introduced.
* We’ve removed KHTML prefix testing, due to lack of usage.
- We encourage all users to upgrade to Modernizr 2.5, as there should be no regressions. If you do happen to encounter issues, please <a href="https://github.com/Modernizr/Modernizr/wiki/Filing-a-bug">file them on github</a>.
+ We encourage all users to upgrade to Modernizr 2.5, as there should be no regressions. If you do happen to encounter issues, please <a href="https://github.com/Modernizr/Modernizr/wiki/Filing-a-bug">file them on GitHub</a>.
<h4 id="thanks">Thanks</h4>
Oops, something went wrong.

0 comments on commit 28c3fb7

Please sign in to comment.