Modify the template to add analytics to all extension docs....

chrome/common/extensions/docs/static/match_patterns.html

 <div id="pageData-title" class="pageData">Match Patterns</div>
 
 <p>
 <a href="content_scripts.html">Content scripts</a> operate on
 a set of URLs defined by match patterns.
 You can put one or more match patterns
 in the <code>"matches"</code> part of
 a content script's section of the manifest.
 This page describes the match pattern syntax &mdash;
 the rules you need to follow when you specify
@@ skipping 41 matching lines @@
 The following table shows some valid patterns.
 </p>
 
 <table>
 <tbody>
 <tr>
   <th>Pattern</th>
   <th>What it does</th>
   <th>Examples of matching URLs</th>
 </tr>
-  
+
 <tr>
   <td>
     <code>http://*/*</code>
   </td>
-    
+
   <td>Matches any URL that uses the <code>http</code> scheme</td>
-  
+
   <td>
     http://www.google.com/<br>
     http://example.org/foo/bar.html
   </td>
 </tr>
-  
+
 <tr>
   <td>
     <code>http://*/foo*</code>
   </td>
-    
+
   <td>
     Matches any URL that uses the <code>http</code> scheme, on any host,
     as long as the path starts with <code>/foo</code>
   </td>
-  
+
   <td>
     http://example.com/foo/bar.html<br>
     http://www.google.com/foo<b></b>
   </td>
 </tr>
-  
+
 <tr>
   <td>
     <code>https://*.google.com/foo*bar </code>
   </td>
-    
+
   <td>
     Matches any URL that uses the <code>https</code> scheme,
     is on a google.com host
     (such as www.google.com, docs.google.com, or google.com),
     as long as the path starts with <code>/foo</code>
     and ends with <code>bar</code>
   </td>
-  
+
   <td>
     http://www.google.com/foo/baz/bar<br>
     http://docs.google.com/foobar
   </td>
 </tr>
-  
+
 <tr>
   <td>
     <code>http://example.org/foo/bar.html </code>
   </td>
-    
+
   <td>Matches the specified URL</td>
-  
+
   <td>
     http://example.org/foo/bar.html
   </td>
 </tr>
-  
+
 <tr>
   <td>
     <code>file:///foo*</code>
   </td>
-    
+
   <td>Matches any local file whose path starts with <code>/foo</code></td>
-  
+
   <td>
     file:///foo/bar.html<br>
     file:///foo
   </td>
 </tr>
-  
+
 <tr>
   <td>
     <code>http://127.0.0.1/*</code>
   </td>
-    
+
   <td>
     Matches any URL that uses the <code>http</code> scheme
     and is on the host 127.0.0.1
   </td>
   <td>
     http://127.0.0.1/<br>
     http://127.0.0.1/foo/bar.html
   </td>
 </tr>
 </tbody>
 </table>
 
 <p>
 Here are some examples of <em>invalid</em> pattern matches:
 </p>
 
 <table>
 <tbody>
 <tr>
   <th>Bad pattern</th>
   <th>Why it's bad</th>
 </tr>
-  
+
 <tr>
   <td><code>http://*</code></td>
   <td>No <em>path</em></td>
 </tr>
-  
+
 <tr>
   <td><code>http://*foo/bar</code></td>
   <td>'*' in the <em>host</em> can be followed only by a '.' or '/'</td>
 </tr>
-  
+
 <tr>
   <td><code>http://foo.*.bar/baz&nbsp; </code></td>
   <td>If '*' is in the <em>host</em>, it must be the first character</td>
   </tr>
-  
+
 <tr>
   <td><code>http:/bar</code></td>
   <td>Missing <em>scheme</em> separator ("/" should be "//")</td>
 </tr>
-  
+
 <tr>
   <td><code>foo://*</code></td>
   <td>Invalid <em>scheme</em></td>
 </tr>
 </tbody>
 </table>