bump

Author: jonathanong

api.html

@@ -107,6 +107,9 @@ <h3 id="nlz-build-nlz-watch">nlz build, nlz watch</h3>
 as well as CSS and HTML file support.</p>
 <p>Most of these parameters and options can be set via <code>.nlzrc</code>,
 allowing developers to simply run <code>nlz build --watch</code>.</p>
+<p>Note that the builder <strong>does not support buildilng web components!</strong>
+This is essentially impossible to do.
+Only use web components in a SPDY environment.</p>
 <h4 id="entry-points">Entry Points</h4>
 <pre><code class="lang-bash">nlz build [entrypoints...]
 

api/nlz.md

@@ -42,6 +42,10 @@ as well as CSS and HTML file support.
 Most of these parameters and options can be set via `.nlzrc`,
 allowing developers to simply run `nlz build --watch`.
 
+Note that the builder __does not support buildilng web components!__
+This is essentially impossible to do.
+Only use web components in a SPDY environment.
+
 #### Entry Points
 
 ```bash

guide.html

@@ -36,6 +36,11 @@ <h4 id="prepend-relative-urls-with-if-it-contains-a-">Prepend relative URLs with
 To avoid this confusion, just prepend it with a <code>./</code>:</p>
 <pre><code class="lang-css"><span class="hljs-attribute">background-image</span>: <span class="hljs-string">url('./images/[email protected]')</span>
 </code></pre>
+</div></section><section><div class="container"><h2 id="authoring-html">Authoring Web Components</h2><h3 id="only-use-web-components-in-a-spdy-environment">Only use web components in a SPDY environment</h3>
+<p>Normalize does not support creating bundles with web components.
+Doing so in an unopinionated manner is very difficult.
+Instead, you should only use web components with a SPDY push server
+(or allow your users to suffer the latency).</p>
 </div></section><section><div class="container"><h2 id="bundling">Bundling</h2><p>As shown via <code>nlz build(1)</code>,
 you can build multiple entry points, whether <code>.js</code> or <code>.css</code>,
 all at the same time.</p>

guide/html.md

@@ -0,0 +1,7 @@
+
+### Only use web components in a SPDY environment
+
+Normalize does not support creating bundles with web components.
+Doing so in an unopinionated manner is very difficult.
+Instead, you should only use web components with a SPDY push server
+(or allow your users to suffer the latency).

guide/index.jade

@@ -18,6 +18,10 @@ block main
     h2(id='authoring-css') Authoring CSS
     include:markdown css.md
 
+  section: .container
+    h2(id='authoring-html') Authoring Web Components
+    include:markdown html.md
+
   section: .container
     h2(id='bundling') Bundling
     include:markdown bundling.md

index.html

@@ -19,6 +19,8 @@
 There are no more JSON files to declare dependencies in - just inline them in your code.
 If you wish to use private modules, simply setup your own proxy!</p>
 <h3 id="no-concatenation-step">No Concatenation Step with SPDY Push</h3><p>SPDY push allows websites to avoid a concatenation step - just SPDY push all your assets!
+Previously, concatenation steps were required to avoid unnecessary HTTP roundtrips,
+but this latency is nonexistent with SPDY push!
 However, <a href="https://github.com/normalize/nlz"><code>nlz(1)</code></a> still includes a concatenation step if you still wish to create bundles.</p>
 <ul>
 <li><a href="https://github.com/normalize/koa.js">koa-normalize</a> - a SPDY push server for <a href="https://koajs.com">koa</a></li>

index/index.jade

@@ -50,6 +50,8 @@ block main
     h3(id='no-concatenation-step') No Concatenation Step with SPDY Push
     :markdown
       SPDY push allows websites to avoid a concatenation step - just SPDY push all your assets!
+      Previously, concatenation steps were required to avoid unnecessary HTTP roundtrips,
+      but this latency is nonexistent with SPDY push!
       However, [`nlz(1)`](https://github.com/normalize/nlz) still includes a concatenation step if you still wish to create bundles.
 
       - [koa-normalize](https://github.com/normalize/koa.js) - a SPDY push server for [koa](https://koajs.com)