Write a short introduction. Fixes #11.

Author: annevk

Overview.html

@@ -40,6 +40,7 @@ <h2 class="no-num no-toc" id="table-of-contents">Table of Contents</h2>
 <!--begin-toc-->
 <ul class="toc">
  <li><a class="no-num short" href="#goals">Goals</a></li>
+ <li><a class="no-num short" href="#preface">Preface</a></li>
  <li><a class="short" href="#conformance"><span class="secno">1 </span>Conformance</a></li>
  <li><a href="#infrastructure"><span class="secno">2 </span>Infrastructure</a>
   <ul class="toc">
@@ -120,6 +121,26 @@ <h2 class="no-num short" id="goals">Goals</h2>
 
 
 
+<h2 class="no-num short" id="preface">Preface</h2>
+
+<p>At a high level, fetching a resource is a fairly simple operation. A request goes in, a
+response comes out. <!--You can't explain that! -->The details of that operation are
+however quite involved and used to not be written down carefully and differ from one API
+to the next.
+
+<p>Numerous APIs provide the ability to fetch a resource, e.g. HTML's <code>img</code> and
+<code>script</code> element, CSS' <code>cursor</code> and <code>list-style-image</code>,
+the <code>navigator.sendBeacon()</code> and <code>self.importScripts()</code> JavaScript
+APIs. The Fetch Standard provides a unified architecture for these features so they are
+all consistent when it comes to various aspects of fetching, such as redirects and the
+CORS protocol.
+
+<p>The Fetch Standard also defines the <code title="dom-global-fetch"><a href="#dom-global-fetch">fetch()</a></code>
+JavaScript API, which exposes most of the networking functionality at a fairly low level
+of abstraction.
+
+
+
 <h2 class="short" id="conformance"><span class="secno">1 </span>Conformance</h2>
 
 <p>All diagrams, examples, and notes in this specification are
@@ -4065,6 +4086,7 @@ <h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
 Jesse M. Heines,
 Jonas Sicking,
 Jonathan Kingston,
+Jörn Zaefferer,
 Julian Reschke,
 송정기 (Jungkee Song),
 Jussi Kalliokoski,

Overview.src.html

@@ -68,6 +68,26 @@ <h2 class="no-num short">Goals</h2>
 
 
 
+<h2 class="no-num short">Preface</h2>
+
+<p>At a high level, fetching a resource is a fairly simple operation. A request goes in, a
+response comes out. <!--You can't explain that! -->The details of that operation are
+however quite involved and used to not be written down carefully and differ from one API
+to the next.
+
+<p>Numerous APIs provide the ability to fetch a resource, e.g. HTML's <code>img</code> and
+<code>script</code> element, CSS' <code>cursor</code> and <code>list-style-image</code>,
+the <code>navigator.sendBeacon()</code> and <code>self.importScripts()</code> JavaScript
+APIs. The Fetch Standard provides a unified architecture for these features so they are
+all consistent when it comes to various aspects of fetching, such as redirects and the
+CORS protocol.
+
+<p>The Fetch Standard also defines the <code title=dom-global-fetch>fetch()</code>
+JavaScript API, which exposes most of the networking functionality at a fairly low level
+of abstraction.
+
+
+
 <h2 class="short">Conformance</h2>
 
 <p>All diagrams, examples, and notes in this specification are
@@ -3949,6 +3969,7 @@ <h2 class=no-num>Acknowledgments</h2>
 Jesse M. Heines,
 Jonas Sicking,
 Jonathan Kingston,
+Jörn Zaefferer,
 Julian Reschke,
 송정기 (Jungkee Song),
 Jussi Kalliokoski,