bkardell · December 28, 2013 22:10
diff --git a/projects.html b/projects.html
 <!DOCTYPE>
 <html>
  <head>
    <meta charset='utf-8'>
    <meta http-equiv="X-UA-Compatible" content="chrome=1">
    <link href='https://fonts.googleapis.com/css?family=Chivo:900' rel='stylesheet' type='text/css'>
    <link rel="stylesheet" type="text/css" href="/stylesheets/stylesheet.css" media="screen" />
    <link rel="stylesheet" type="text/css" href="/stylesheets/pygment_trac.css" media="screen" />
    <link rel="stylesheet" type="text/css" href="/stylesheets/print.css" media="print" />
    <!--[if lt IE 9]>
    <script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
    <![endif]-->
    <title>Extensible Web Projects</title>
  </head>
  <body>
      <div id="container">
        <div class="inner">
  
          <header>
            <h1>Extensible Web Manifesto Projects</h1>
            <h2>#extendthewebforward</h2>
          </header>
          <p>
            Wondering what Extensible Web members are watching/contributing to and helping to keep in the
            Extensible Web spirit?  Below is a partial list.
          </p>  
          
          <hr>
  
          <section id="main_content">
            <ul>

              <li>
                <h3>Promises</h3>
                <p>Promises provide a critically missing primitive for dealing with asynchronous APIs, especially in a single-threaded world, that have
                  plagued JavaScript APIs for a long time.  Numerous members of TC39, W3C TAG, the CommonJS and the Extensible Web communities worked together to 
                  define a universal standard that can be used in asynchronous API specifications in TC39, WHATWG and W3C specifications.  Developers created prollyfills 
                  and collected feedback in the process.  Further, W3C TAG member co-authors of the Extensible Web Manifesto helped to review numerous upcomming specifications, and introduce Promise-based APIs. 
                </p>
              </li>


              <li>
                <h3>Streams</h3>
                <p>Streams are a missing fundamental primitive in the browser - it's important that we have an 
                  interface for creating, composing, consuming and working with streams of data moving forward.
                  The W3C had several groups working on streams of some kind, most recently the 
                  <a href="https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm" target="_blank">W3C Streams API</a> was 
                  presented.  Members proviced a lot of feedback on the mailing list and <a href="https://twitter.com/domenic" target="_blank">Domenic Denicola</a>
                  created the <a href="https://github.com/whatwg/streams/">WHATWG Streams API</a> proposal.  Work continues toward 
                  a unified API proposal and it's looking better all the time.
                </p>
              </li>

              <li>
                <h3>ServiceWorkers</h3>
                <p><a href="https://twitter.com/slightlylate">Alex Russell</a> began work on an idea for providing appropriate 
                  primitives that "make it possible for application developers to build URL-friendly, always-available applications in a sane and layered way.".  With help and discussion from other members, <a href="https://github.com/slightlyoff/ServiceWorker" target="_blank">ServiceWorkers</a> were born, 
                  providing necessary primitives to fulfill all manners of offline use-cases and open new doors.</p>
              </li>

              <li>
                <h3>Bundle URLs</h3>
                <p>Description...</p>
              </li>

              <li>
                <h3>HTML Imports / ES6 Modules</h3>
                <p>The Extensible Web community has been actively working with the public webapps group, TC39 members, the Polymer team and others to 
                  answer questions about the nature and value of HTML Imports and their relationship with the pre-loader, blocking and the ES6 module loader.  
                  We've helped to generate several ideas to improve the system and the prollyfill.  These two specifications will provide necessary 
                  fundamental primives and answers to a host of questions that developers have been facing for some time.
                </p>
              </li>
              
              <li>
                <h3>Async Local Storage</h3>
                <p><a href="https://github.com/slightlyoff/async-local-storage" target="_blank">Async Local Storage</a>Description...</p>
              </li>

              <li>
                <h3>Archives as First Class Citizens</h3>
                <p><a href="http://lists.w3.org/Archives/Public/public-whatwg-archive/2013Aug/0278.html" target="_blank">List discussions</a>, 
                  <a href="http://www.w3.org/wiki/TAG/Planning/Sept-2013-F2F">W3C TAG topic</a>
                  Description...</p>
              </li>

              <li>
                <h3>Web Components</h3>
                <p>
                  Description...
                </p>
              </li>




              <li>
                <h3>Web Audio / Web Midi</h3>
                <p><a href="http://www.w3.org/TR/webaudio/" target="_blank">W3C Web Audio</a> <a href="http://www.w3.org/TR/webmidi/" target="_blank">W3C Web Midi</a>

                  <a href="https://github.com/cwilso/WebMIDIAPIShim/" target="_blank">prollyfill</a>

                  <a href="http://webaudiodemos.appspot.com/slides/index.html" target="_blank">Presentation</a>

                  relationship with &lt;audio&gt; and &lt;Web RTC&gt;</p>
              </li>

              <li>
                <h3>Ping / sendBeacon</h3>
                <p>Consideration/prioritization in the relationships between and <a href="https://twitter.com/BrendanEich/status/414274857912639488" target="_blank">what to choose to implement and when...</a></p>
              </li>


              <li>
                <h3>Element queries</h3>

              </li>

              <li>
                <h3>Misc CSS-Related</h3>
                  <p>
                    <h4>Element Queries</h4>
                  <a href="http://ianstormtaylor.com/media-queries-are-a-hack/" target="_blank">IAN STORM TAYLOR</a>
                  <a href="http://www.xanthir.com/b4PR0">Tab's response</a>  <a href="http://fremycompany.com/BG/2013/Element-Media-Queries-min-width-883/" target="_blank">Francois Remy's post</a>
                  <a href="http://coding.smashingmagazine.com/2013/06/25/media-queries-are-not-the-answer-element-query-polyfill/" target="_blank">Piece in smashing magazine</a>
                  </p>

                  <p>
                    <h4>CSS Pseudo-classes</h4>
                    <a href="https://github.com/bkardell/selectors-L4-link-prollyfills">Level 4 - link</a>
                    <a href="http://hitchjs.wordpress.com/2012/08/23/about-time-taming-the-standards-process/" target="_blank">Level >4 :time pseudo element</a>
                  </p>

                  <p>
                    <h4>CSS Pseudo-elements++</h4>
                    <a href="https://github.com/adobe/css-pseudo-elements" target="_blank">More CSS Pseudo-Elements</a></p>
                  </p>

                  <p>
                    <h4>Regions</h4>
                    <a href="https://github.com/adobe-webplatform/css-regions-polyfill" target="_blank">CSS Regions</a>
                  </p>
              <li>





            </ul>
          
          </section>
        </div>
      </div>
  </body>
 </html>
	<!DOCTYPE>
	<html>
	<head>
	<meta charset='utf-8'>
	<meta http-equiv="X-UA-Compatible" content="chrome=1">
	<link href='https://fonts.googleapis.com/css?family=Chivo:900' rel='stylesheet' type='text/css'>
	<link rel="stylesheet" type="text/css" href="/stylesheets/stylesheet.css" media="screen" />
	<link rel="stylesheet" type="text/css" href="/stylesheets/pygment_trac.css" media="screen" />
	<link rel="stylesheet" type="text/css" href="/stylesheets/print.css" media="print" />
	<!--[if lt IE 9]>
	<script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
	<![endif]-->
	<title>Extensible Web Projects</title>
	</head>
	<body>
	<div id="container">
	<div class="inner">

	<header>
	<h1>Extensible Web Manifesto Projects</h1>
	<h2>#extendthewebforward</h2>
	</header>
	<p>
	Wondering what Extensible Web members are watching/contributing to and helping to keep in the
	Extensible Web spirit? Below is a partial list.
	</p>

	<hr>

	<section id="main_content">
	<ul>

	<li>
	<h3>Promises</h3>
	<p>Promises provide a critically missing primitive for dealing with asynchronous APIs, especially in a single-threaded world, that have
	plagued JavaScript APIs for a long time. Numerous members of TC39, W3C TAG, the CommonJS and the Extensible Web communities worked together to
	define a universal standard that can be used in asynchronous API specifications in TC39, WHATWG and W3C specifications. Developers created prollyfills
	and collected feedback in the process. Further, W3C TAG member co-authors of the Extensible Web Manifesto helped to review numerous upcomming specifications, and introduce Promise-based APIs.
	</p>
	</li>


	<li>
	<h3>Streams</h3>
	<p>Streams are a missing fundamental primitive in the browser - it's important that we have an
	interface for creating, composing, consuming and working with streams of data moving forward.
	The W3C had several groups working on streams of some kind, most recently the
	<a href="https://dvcs.w3.org/hg/streams-api/raw-file/tip/Overview.htm" target="_blank">W3C Streams API</a> was
	presented. Members proviced a lot of feedback on the mailing list and <a href="https://twitter.com/domenic" target="_blank">Domenic Denicola</a>
	created the <a href="https://github.com/whatwg/streams/">WHATWG Streams API</a> proposal. Work continues toward
	a unified API proposal and it's looking better all the time.
	</p>
	</li>

	<li>
	<h3>ServiceWorkers</h3>
	<p><a href="https://twitter.com/slightlylate">Alex Russell</a> began work on an idea for providing appropriate
	primitives that "make it possible for application developers to build URL-friendly, always-available applications in a sane and layered way.". With help and discussion from other members, <a href="https://github.com/slightlyoff/ServiceWorker" target="_blank">ServiceWorkers</a> were born,
	providing necessary primitives to fulfill all manners of offline use-cases and open new doors.</p>
	</li>

	<li>
	<h3>Bundle URLs</h3>
	<p>Description...</p>
	</li>

	<li>
	<h3>HTML Imports / ES6 Modules</h3>
	<p>The Extensible Web community has been actively working with the public webapps group, TC39 members, the Polymer team and others to
	answer questions about the nature and value of HTML Imports and their relationship with the pre-loader, blocking and the ES6 module loader.
	We've helped to generate several ideas to improve the system and the prollyfill. These two specifications will provide necessary
	fundamental primives and answers to a host of questions that developers have been facing for some time.
	</p>
	</li>

	<li>
	<h3>Async Local Storage</h3>
	<p><a href="https://github.com/slightlyoff/async-local-storage" target="_blank">Async Local Storage</a>Description...</p>
	</li>

	<li>
	<h3>Archives as First Class Citizens</h3>
	<p><a href="http://lists.w3.org/Archives/Public/public-whatwg-archive/2013Aug/0278.html" target="_blank">List discussions</a>,
	<a href="http://www.w3.org/wiki/TAG/Planning/Sept-2013-F2F">W3C TAG topic</a>
	Description...</p>
	</li>

	<li>
	<h3>Web Components</h3>
	<p>
	Description...
	</p>
	</li>




	<li>
	<h3>Web Audio / Web Midi</h3>
	<p><a href="http://www.w3.org/TR/webaudio/" target="_blank">W3C Web Audio</a> <a href="http://www.w3.org/TR/webmidi/" target="_blank">W3C Web Midi</a>

	<a href="https://github.com/cwilso/WebMIDIAPIShim/" target="_blank">prollyfill</a>

	<a href="http://webaudiodemos.appspot.com/slides/index.html" target="_blank">Presentation</a>

	relationship with <audio> and <Web RTC></p>
	</li>

	<li>
	<h3>Ping / sendBeacon</h3>
	<p>Consideration/prioritization in the relationships between and <a href="https://twitter.com/BrendanEich/status/414274857912639488" target="_blank">what to choose to implement and when...</a></p>
	</li>


	<li>
	<h3>Element queries</h3>

	</li>

	<li>
	<h3>Misc CSS-Related</h3>
	<p>
	<h4>Element Queries</h4>
	<a href="http://ianstormtaylor.com/media-queries-are-a-hack/" target="_blank">IAN STORM TAYLOR</a>
	<a href="http://www.xanthir.com/b4PR0">Tab's response</a> <a href="http://fremycompany.com/BG/2013/Element-Media-Queries-min-width-883/" target="_blank">Francois Remy's post</a>
	<a href="http://coding.smashingmagazine.com/2013/06/25/media-queries-are-not-the-answer-element-query-polyfill/" target="_blank">Piece in smashing magazine</a>
	</p>

	<p>
	<h4>CSS Pseudo-classes</h4>
	<a href="https://github.com/bkardell/selectors-L4-link-prollyfills">Level 4 - link</a>
	<a href="http://hitchjs.wordpress.com/2012/08/23/about-time-taming-the-standards-process/" target="_blank">Level >4 :time pseudo element</a>
	</p>

	<p>
	<h4>CSS Pseudo-elements++</h4>
	<a href="https://github.com/adobe/css-pseudo-elements" target="_blank">More CSS Pseudo-Elements</a></p>
	</p>

	<p>
	<h4>Regions</h4>
	<a href="https://github.com/adobe-webplatform/css-regions-polyfill" target="_blank">CSS Regions</a>
	</p>
	<li>





	</ul>

	</section>
	</div>
	</div>
	</body>
	</html>