Skip to content

Minor editing in index.html #58

Merged
merged 2 commits into from Dec 15, 2011
View
86 index.html
@@ -58,10 +58,10 @@ <h1 class="hed">Learn</h1>
<h2 id="how_do_i_keep_up_with_what8217s_landing_in_browsers" class="subhed">How do I keep up with what&#8217;s landing in browsers?</h2>
<ul>
- <li><a href="http://updates.html5rocks.com/2011/10/Keeping-up-with-HTML5-and-browser-support">Keeping up with HTML5 and browser support</a> - a list of resources that capture all of these changing things.</li>
+ <li><a href="http://updates.html5rocks.com/2011/10/Keeping-up-with-HTML5-and-browser-support">Keeping up with HTML5 and browser support</a> - a list of resources that capture all of these changing things</li>
<li><a href="http://peter.sh/">Peter Beverloo&#8217;s Blog</a> - weekly updates of WebKit and Chrome</li>
<li><a href="http://blog.whatwg.org/">The WHATWG Blog</a> - summaries of weekly web standards activity</li>
- <li><a href="http://www.w3.org/QA/archive/open_web/">W3C&#8217;s open web</a> - weekly updates about the Open Web Platform.</li>
+ <li><a href="http://www.w3.org/QA/archive/open_web/">W3C&#8217;s open web</a> - weekly updates about the Open Web Platform</li>
<li><a href="http://my.opera.com/ODIN/blog/">Opera Developer News</a> - tracks changes to Opera's web platform
<li><a href="http://updates.html5rocks.com">HTML5 Rocks updates</a> - HTML5 and Chrome breaking news
@@ -71,7 +71,7 @@ <h2 id="how_do_i_keep_up_with_what8217s_landing_in_browsers" class="subhed">How
<h3 id="follow_them_on_twitter" class="subhed">Follow them on Twitter</h3>
<p>
- You should probably follow: <a href="http://twitter.com/oDevRel">@oDevRel</a> (Opera developer relations), <a href="http://twitter.com/ChromiumDev">@ChromiumDev</a> (Chrome developer relations), <a href="http://twitter.com/mozhacks">@mozhacks</a> (Mozilla's web developer outpost) & <a href="http://twitter.com/ie">@IE</a> (Internet Explorer Team)
+ You should probably follow: <a href="http://twitter.com/oDevRel">@oDevRel</a> (Opera developer relations), <a href="http://twitter.com/ChromiumDev">@ChromiumDev</a> (Chrome developer relations), <a href="http://twitter.com/mozhacks">@mozhacks</a> (Mozilla's web developer outpost) & <a href="http://twitter.com/ie">@IE</a> (Internet Explorer Team).
</p>
<h2 id="how_do_i_understand_how_browsers_work" class="subhed">How do I understand how browsers work?</h2>
@@ -89,17 +89,17 @@ <h2 id="other_learning_resources" class="subhed">Other learning resources</h2>
<li><a href="http://diveintohtml5.info/">Dive into HTML5</a> - takes an in depth look at a selection of HTML5 features.</li>
<li><a href="http://addyosmani.com/blog/">Addy Osmani&#8217;s blog</a> - tons of great articles for people who want to learn more about jQuery, JavaScript, HTML5, and CSS3.</li>
<li><a href="http://paulirish.com">Paul Irish&#8217;s blog</a> - all about helping you build cool websites and keeping you up to date on the latest news.</li>
- <li><a href="http://dev.opera.com">Dev.Opera</a> - Articles for learning about HTML5 features.</li>
+ <li><a href="http://dev.opera.com">Dev.Opera</a> - articles for learning about HTML5 features.</li>
<li><a href="http://paulirish.com/2011/web-browser-frontend-and-standards-feeds-to-follow/">Web browser, frontend and standards feeds to follow</a> </li>
- <li><a href="http://yuilibrary.com/theater/">YUI Theater</a> - Videos of talks about frontend engineering and web technologies given at Yahoo! over the years (many of them unrelated to YUI).</li>
- <li><a href="http://www.adobe.com/devnet/html5.html">Adobe Developer Connection</a> - Articles and videos for learning about HTML5, CSS3 and mobile development.</li>
+ <li><a href="http://yuilibrary.com/theater/">YUI Theater</a> - videos of talks about frontend engineering and web technologies given at Yahoo! over the years (many of them unrelated to YUI).</li>
+ <li><a href="http://www.adobe.com/devnet/html5.html">Adobe Developer Connection</a> - articles and videos for learning about HTML5, CSS3 and mobile development.</li>
</ul>
<h2 id="reference_docs_wikis" class="subhed">Reference docs/wikis</h2>
<ul>
<li><a href="https://developer.mozilla.org/en-US/">Mozilla&#8217;s MDN</a> - awesome documentation regarding HTML, CSS, JavaScript, the DOM, and more. It&#8217;s also a great place to contribute! Read <a href="https://developer.mozilla.org/Project:en/How_to_Help">How to help</a> and learn how to <a href="https://developer.mozilla.org/Project:en/Getting_started">get started</a>.</li>
- <li><a href="http://dochub.io/">dochub.io</a> - Quick access to MDN-docs, includes HTML, CSS, JavaScript, and DOM.</li>
+ <li><a href="http://dochub.io/">dochub.io</a> - quick access to MDN-docs, includes HTML, CSS, JavaScript, and DOM.</li>
<li><a href="https://developer.mozilla.org/Writing_Forward_Compatible_Websites">Forward-compatible websites</a> - list of best practices for creating websites that won&#8217;t break when browsers are updated.</li>
</ul>
</div>
@@ -118,7 +118,7 @@ <h2 class="subhed">Itching to learn?</h2>
<section id="meetups" class="col-ab">
<div class="col-a">
<h1 class="hed">Meet like-minded folks</h1>
- <p>Attending local meetups and conferences is a great way to connect with other developers to learn, share resources, and bring new ideas and collaborations to life. Sites like <a href="http://meetup.com">Meetup.com</a> and <a href="http://lanyrd.com">Lanyrd</a> can help you find events in your neighborhood.</p>
+ <p>Attending local meetups and conferences is a great way to connect with other developers to learn, share resources, and bring new ideas and collaborations to life. Sites like <a href="http://meetup.com">Meetup</a> and <a href="http://lanyrd.com">Lanyrd</a> can help you find events in your neighborhood.</p>
</div>
</section>
<section id="askhelp" class="col-ab">
@@ -134,9 +134,9 @@ <h2 id="answer_questions_and_participate_in_conversations_on_irc" class="subhed"
<h2 id="how_to_ask_for_help" class="subhed">How to ask for help</h2>
<ol class="tasks">
<li>You&#8217;ll probably want to <a href="http://css-tricks.com/13414-seriously-just-make-a-jsfiddle/">make a jsfiddle first</a>.</li>
- <li><a href="http://css-tricks.com/6263-reduced-test-cases/">Create a reduced test case</a></li>
+ <li><a href="http://css-tricks.com/6263-reduced-test-cases/">Create a reduced test case</a>.</li>
<li>Remember: be specific!</li>
- <li>Ask on IRC, <a href="http://stackoverflow.com">StackOverflow</a> (even its <a href="http://chat.stackoverflow.com/rooms/17/javascript">javascript chatroom</a>), or a group of friends
+ <li>Ask on IRC, <a href="http://stackoverflow.com">StackOverflow</a> (even its <a href="http://chat.stackoverflow.com/rooms/17/javascript">javascript chatroom</a>), or a group of friends.
</ol>
</div>
@@ -160,8 +160,8 @@ <h2 class="subhed">You clearly know your way around. Now it's time to show it.</
</div>
<section id="helpothers" class="col-ab">
<div class="col-a">
- <h1 class="hed">Help Others</h1>
- <p>We've all got to start somewhere! Helping others reassures your knowledge, and also broadens the amount of concepts you're exposed to. Below are some great Open-Source projects that are always looking for help. Remember - no patch is too small!</p>
+ <h1 class="hed">Help others</h1>
+ <p>We've all got to start somewhere! Helping others reassures your knowledge, and also broadens the amount of concepts you're exposed to. Below are some great open-source projects that are always looking for help. Remember - no patch is too small!</p>
<h2 id="open_source_projects_worth_your_time" class="subhed">Open-Source projects worth your time</h2>
<ul>
@@ -195,25 +195,25 @@ <h2 class="subhed">Pass it on!</h2>
<section id="specs" class="col-ab">
<div class="col-a">
- <h1 class="hed">Give Feedback on Specifications</h1>
+ <h1 class="hed">Give feedback on specifications</h1>
- <p>Specs codify the expected behavior. They are developed by Working Groups (WG) along with active discussion on mailing lists. While we can’t always be certain that all browser vendors will adhere to the rules set forth in a spec they provide us with something that we, as developers, can standardize against.</p>
+ <p>Specs codify the expected behavior. They are developed by Working Groups (WG) along with active discussion on mailing lists. While we can’t always be certain that all browser vendors will adhere to the rules set forth in a spec, they provide us with something that we, as developers, can standardize against.</p>
<ul>
- <li>Learn the <a href="http://diveintohtml5.info/past.html">history of HTML</a></li>
- <li>Take an <a href="http://fantasai.inkedblade.net/weblog/2011/inside-csswg/">inside look at how the CSS WG works</a></li>
+ <li>Learn the <a href="http://diveintohtml5.info/past.html">history of HTML</a>.</li>
+ <li>Take an <a href="http://fantasai.inkedblade.net/weblog/2011/inside-csswg/">inside look at how the CSS WG works</a>.</li>
<li>Subscribe to these mailing lists to follow and contribute to the discussions that drive the web:
<ul class="resources">
<li><a href="http://lists.w3.org/Archives/Public/public-webapps/">public-webapps</a> - technical discussion for the Web Applications Working Group</li>
<li><a href="http://lists.w3.org/Archives/Public/www-style/">www-style</a> - technical discussion on Cascading Style Sheets (CSS) and its specifications</li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/">whatwg</a> - WHATWG's mailing list</li>
<li><a href="http://lists.w3.org/Archives/Public/public-html/">public-html</a> - W3C HTML Working Group</li>
- <li><a href="http://lists.w3.org/Archives/Public/www-dom/">www-dom</a> - where the DOM is improved
+ <li><a href="http://lists.w3.org/Archives/Public/www-dom/">www-dom</a> - where the DOM is improved</li>
<li><a href="http://lists.w3.org/Archives/Public/public-fx/">public-fx</a> - issues affecting the CSS and SVG Working Groups</li>
</ul>
</li>
- <li>Read through the <a href="http://developers.whatwg.org/">HTML5 Spec for developers</a> (the implementor stuff removed, formatted beautifully for you)</li>
- <li>The easiest way to comment or give feedback on the contents of the <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/">HTML specification</a>, you can select the text you want to comment on and leave a message from the form at the bottom of the page.</li>
+ <li>Read through the <a href="http://developers.whatwg.org/">HTML5 Spec for developers</a> (the implementor stuff removed, formatted beautifully for you).</li>
+ <li>The easiest way to comment or give feedback on the contents of the <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/">HTML specification</a> is to select the text you want to comment on and leave a message using the form at the bottom of the page.</li>
<li>
See the latest commits to the HTML and CSS specs by following their respective working groups on Twitter:
<ul class="resources">
@@ -237,7 +237,7 @@ <h2 class="subhed">Are you specced out?</h2>
<section id="explore" class="col-ab">
<div class="col-a">
- <h1 class="hed">Explore Frontend Features</h1>
+ <h1 class="hed">Explore frontend features</h1>
<p>Once you&#8217;ve picked up the basics, it&#8217;s time to dive a bit deeper into the current (and future) state of web standards! Get excited, because here, we check out advanced CSS, brand-new HTML5 features/APIs, and even what the future of these languages are expected to be. Several new capabilities are now available in browsers, and exploring these new capabilities will help us push the web forward!</p>
<h2 id="examples_of_how_to_explore_features_well" class="subhed">Examples of how to explore features well</h2>
@@ -256,7 +256,7 @@ <h2 id="examples_of_how_to_explore_features_well" class="subhed">Examples of how
<h2 id="cool_ideas_to_explore_more" class="subhed">Cool features to explore more (and write about)</h2>
- <p>Browsers ship new CSS features all the time. The vendor prefixes we love to hate are actually there so we developers can provide feedback on if the feature meets our needs. Encourage yourself to investigate if they do! This <a href="http://peter.sh/experiments/vendor-prefixed-css-property-overview/">vendor-prefixed CSS property overview</a>, by Peter Beverloo, has a lot of experimental CSS mentioned; much of which is not well understood. Consider writing about them and the items below:
+ <p>Browsers ship new CSS features all the time. The vendor prefixes we love to hate are actually there so we developers can provide feedback on whether the feature meets our needs. Encourage yourself to investigate if they do! This <a href="http://peter.sh/experiments/vendor-prefixed-css-property-overview/">vendor-prefixed CSS property overview</a>, by Peter Beverloo, has a lot of experimental CSS mentioned; much of which is not well understood. Consider writing about them and the items below:
<ul>
<li><a href="https://developer.mozilla.org/En/CSS/%3Achecked">The :checked selector</a> / <a href="http://dev.w3.org/csswg/css3-images/#object-fit">object-fit</a> / <a href="https://developer.mozilla.org/en/CSS/background-clip">background-clip</a> / <a href="https://dvcs.w3.org/hg/FXTF/raw-file/tip/filters/index.html">fx blur css filter</a> / <a href="http://dropshado.ws/post/1015351370/webkit-line-clamp">-webkit-line-clamp</a> / <a href="https://developer.mozilla.org/en/CSS/text-overflow">text-overflow</a> / <a href="https://developer.mozilla.org/En/CSS/Box-sizing">box-sizing</a> / <a href="https://developer.mozilla.org/en/CSS3_Columns">CSS columns</a></li>
@@ -297,7 +297,7 @@ <h2 class="subhed">Explore the unknown!</h2>
<h1 class="hed">Write</h1>
<p>Publish what you learn and don&#8217;t be afraid to make mistakes. Publish to your personal blog and keep your posts updated. Be sure to speak with your own voice! Remember that it is okay to not be an absolute authority on a subject to author a post! Always ask questions and prompt conversations. There is seldom a wrong question or a wrong answer.</p>
- <p>Teaching is a great learning tool as well. So, even if you are getting started in an area, you’re helping yourself by writing about it as well. You can always consider asking a mentor or friend for a technical review. (Addy&#8217;s done that with aplomb)</p>
+ <p>Teaching is a great learning tool as well. So, even if you are getting started in an area, you’re helping yourself by writing about it as well. You can always consider asking a mentor or friend for a technical review. (Addy&#8217;s done that with aplomb.)</p>
<h2 id="what_should_you_start_to_learn_about" class="subhed">What should you write about?</h2>
@@ -307,13 +307,13 @@ <h2 id="what_should_you_start_to_learn_about" class="subhed">What should you wri
<li>Why do the <code>&lt;br&gt;</code> and <code>&lt;hr&gt;</code> elements (or any element) exist?</li>
<li>How to create a slideshow with the least amount of code?</li>
<li>What is the DOM? Why does it exist?</li>
- <li>Check how browsers implement a specific property and compare it to the spec. </li>
- <li>How a popular website implements their homepage (with suggestions for improvement)</li>
- <li>How you would fix a popular website's faults (long load-time, invalid JS, etc...)
+ <li>Check how browsers implement a specific property and compare it to the spec.</li>
+ <li>How a popular website implements its homepage (with suggestions for improvement).</li>
+ <li>How you would fix a popular website's faults (long load-time, invalid JS, etc.).</li>
<li>Take a popular demo and make it something else (or use it practically).</li>
- <li>Make a summary of popular ideas around the web lately</li>
- <li>Your experience contributing to an open source project.</li>
- <li>How CSS preprocessors can lead to stringy and bad code if not managed correctly</li>
+ <li>Make a summary of popular ideas around the web lately.</li>
+ <li>Your experience contributing to an open-source project.</li>
+ <li>How CSS preprocessors can lead to stringy and bad code if not managed correctly.</li>
<li>If you are a native speaker of a language other than English:
<ul class="resources">
<li>Translate some popular English web dev posts.</li>
@@ -336,13 +336,13 @@ <h2 class="subhed">Write this down!</h2>
<section id="filebugs" class="col-ab">
<div class="col-a">
<h1 class="hed">File bugs</h1>
- <p>Seriously, all browser vendors would much rather you file tickets with them than tweet about bugs. =D In fact, IE10's platform previews is a great opportunty to file bug reports so things are fixed before they freeze the browser.</p>
+ <p>Seriously, all browser vendors would much rather you file tickets with them than tweet about bugs. =D In fact, <a href="http://msdn.microsoft.com/library/hh673549.aspx">IE10's platform previews</a> provide a great opportunty to file bug reports so things are fixed before the browser is released.</p>
<ul>
<li><a href="http://coding.smashingmagazine.com/2011/09/07/help-the-community-report-browser-bugs/">Help the Community: Report Browser Bugs</a> by Lea Verou</li>
<li><a href="http://ejohn.org/blog/a-web-developers-responsibility/">A Web Developer&#8217;s Responsibility</a> by John Resig</li>
<li><a href="http://a11ybugs.org/">Help prioritize browser accessibility bugs</a> by Vlad Alexander</li>
<li>
- <p>Browser issue trackers - search for existing bug reports or submit new ones</p>
+ <p>Browser issue trackers - search for existing bug reports or submit new ones:</p>
<ul class="resources">
<li><a href="https://bugzilla.mozilla.org/">Mozilla's bugzilla</a></li>
<li><a href="https://bugs.webkit.org/">WebKit bugs</a></li>
@@ -373,7 +373,7 @@ <h2 class="subhed">You've come a long way; you clearly know your stuff! May we s
<section id="hack" class="col-ab">
<div class="col-a">
<h1 class="hed">Hack!</h1>
- <p>Push the web to its limits! Hack on CSS, advanced HTML, and JavaScript. Hack on the browser's rendering engine. Fork github repos, dig through the code, and keep on learning. Let's make the web more awesome. There are so many ways</p>
+ <p>Push the web to its limits! Hack on CSS, advanced HTML, and JavaScript. Hack on the browser's rendering engine. Fork github repos, dig through the code, and keep on learning. Let's make the web more awesome. There are so many ways:</p>
<h2 id="contribute_to_browsers" class="subhed">Contribute to browsers</h2>
<ul>
<li>Help build devtools like <a href="http://trac.webkit.org/wiki/WebInspector">WebKit Inspector</a> and <a href="https://bitbucket.org/scope/dragonfly-stp-1/">Dragonfly</a>.
@@ -397,25 +397,25 @@ <h2 id="contribute_to_testsuites" class="subhed">Contribute to Test Suites</h2>
<p>Test cases are fundamental to standards and to browsers. They assure things work the same across browsers. Yet right now, the W3C test suites don't have nearly as many tests as they need. Tests are written in the languages of web developers: HTML, CSS, and JavaScript. </p>
<ul>
- <li>Get the overview of the
+ <li>Get overviews of the
<a href="http://www.w3.org/2008/webapps/wiki/Testing">w3c webapps test suite</a>, the
<a href="http://www.w3.org/html/wg/wiki/Testing">w3c HTML5 test suite</a>,
- and the <a href="http://wiki.csswg.org/test">CSSWG test suite</a>
+ and the <a href="http://wiki.csswg.org/test">CSSWG test suite</a>.
</li>
- <li>Look into <a href="http://www.w3.org/html/wg/wiki/Testing#New_tests">upstreaming some existing tests</a> into the W3C Test suite</li>
- <li>Upstream <a href="http://trac.webkit.org/browser/trunk/LayoutTests">WebKit&#8217;s LayoutTests</a>. <span>Also see the LayoutTests <a href="http://www.webkit.org/blog/1452/layout-tests-theory/">theory</a> & <a href="http://www.webkit.org/blog/1456/layout-tests-practice/">practice</a></span></li>
- <li>Upstream <a href="https://developer.mozilla.org/en/Mochitest">Mozilla&#8217;s Mochitests</a></li>
- <li>Join the convo on <a href="http://lists.w3.org/Archives/Public/public-webapps-testsuite/">public-webapps-testsuite</a>, <a href="http://lists.w3.org/Archives/Public/public-html-testsuite/">public-html-testsuite</a>, and <a href="http://lists.w3.org/Archives/Public/public-css-testsuite/">public-css-testsuite</a>.</li>
- <li>Contribute to HTML5 Audio on <a href="http://areweplayingyet.org">the AreWePlayingYet? test suite</a></li>
+ <li>Look into <a href="http://www.w3.org/html/wg/wiki/Testing#New_tests">upstreaming some existing tests</a> into the W3C Test suite.</li>
+ <li>Upstream <a href="http://trac.webkit.org/browser/trunk/LayoutTests">WebKit&#8217;s LayoutTests</a>. <span>Also see the LayoutTests <a href="http://www.webkit.org/blog/1452/layout-tests-theory/">theory</a> & <a href="http://www.webkit.org/blog/1456/layout-tests-practice/">practice</a>.</span></li>
+ <li>Upstream <a href="https://developer.mozilla.org/en/Mochitest">Mozilla&#8217;s Mochitests</a>.</li>
+ <li>Join the conversation on <a href="http://lists.w3.org/Archives/Public/public-webapps-testsuite/">public-webapps-testsuite</a>, <a href="http://lists.w3.org/Archives/Public/public-html-testsuite/">public-html-testsuite</a>, and <a href="http://lists.w3.org/Archives/Public/public-css-testsuite/">public-css-testsuite</a>.</li>
+ <li>Contribute to HTML5 Audio on <a href="http://areweplayingyet.org">the AreWePlayingYet? test suite</a>.</li>
</ul>
<h2 id="contribute_to_specs" class="subhed">Contribute to specifications</h2>
<ul>
- <li>Review existing bugs on <a href="http://www.w3.org/Bugs/Public/">W3C bugzilla</a> <span>- and learn <a href="http://wiki.whatwg.org/wiki/Bugzilla_conventions">Bugzilla conventions</a></span>
- <li>Particpate in <a href="http://www.whatwg.org/mailing-list">WHATWG</a> / <a href="http://lists.w3.org/Archives/Public/public-webapps/">public-webapps</a> / <a href="http://lists.w3.org/Archives/Public/www-style/">www-style</a> / <a href="http://lists.w3.org/Archives/Public/public-fx/">public-fx</a> discussions</li>
- <li><a href="http://dev.chromium.org/developers/how-tos/make-a-web-standards-proposal">Make a web standards proposal</a> <span>(this guide tells you how!)</span>
- <li><a href="http://wiki.whatwg.org/wiki/How_to_write_a_spec">Write Specs!</a> <span>we could certainly use more spec writers</span></li>
+ <li>Review existing bugs on <a href="http://www.w3.org/Bugs/Public/">W3C bugzilla</a> <span>- and learn <a href="http://wiki.whatwg.org/wiki/Bugzilla_conventions">Bugzilla conventions</a>.</span>
+ <li>Particpate in <a href="http://www.whatwg.org/mailing-list">WHATWG</a> / <a href="http://lists.w3.org/Archives/Public/public-webapps/">public-webapps</a> / <a href="http://lists.w3.org/Archives/Public/www-style/">www-style</a> / <a href="http://lists.w3.org/Archives/Public/public-fx/">public-fx</a> discussions.</li>
+ <li><a href="http://dev.chromium.org/developers/how-tos/make-a-web-standards-proposal">Make a web standards proposal</a>. <span>(this guide tells you how!)</span>
+ <li><a href="http://wiki.whatwg.org/wiki/How_to_write_a_spec">Write specs!</a> <span>we could certainly use more spec writers.</span></li>
</ul>
<h2 id="contribute_to_validators" class="subhed">Contribute to validators</h2>
<ul>
@@ -431,7 +431,7 @@ <h2 id="contribute_to_validators" class="subhed">Contribute to validators</h2>
<section class="getinvolved">
<h2 class="subhed">I&#8217;m in your codez!</h2>
<div class="task" data-hashtag="#hack">
- <p>Just build stuff. Experiment, fork repos, dig through code. Contribute to the browsers, specs, validators, or great <a href="#open_source_projects_worth_your_time">Open-Source projects</a>!</p>
+ <p>Just build stuff. Experiment, fork repos, dig through code. Contribute to the browsers, specs, validators, or great <a href="#open_source_projects_worth_your_time">open-source projects</a>!</p>
<a href="#" class="pledge">Yes, I want to do this!</a>
<div class="pledges"><p>Here are some developers who want to do this too:</p></div>
</div>
Something went wrong with that request. Please try again.