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

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

 <div id="pageData-title" class="pageData">Overview</div>
 <div id="pageData-showTOC" class="pageData">true</div>
 
 <p>
 Please read this page;
 it has vital information about the extension architecture.
 If you get bored or restless,
 take a break!
 We suggest bouncing between this page
 and tutorials
@@ skipping 15 matching lines @@
 from XMLHttpRequest to JSON to localStorage.
 </p>
 
 <p>
 Extensions can add UI to Google Chrome,
 in the form of
 <a href="toolstrip.html">toolstrips</a> (toolbar additions)
 and <a href="pageActions.html">page actions</a>
 (clickable badges in the address bar).
 Extensions can also interact programmatically
-with browser features such as 
+with browser features such as
 <a href="bookmarks.html">bookmarks</a>
 and <a href="tabs.html">tabs</a>.
 </p>
 
 <p>
 To find a complete list of extension features,
 with implementation details
 for each one,
 see the <a href="devguide.html">Developer's Guide</a>.
 </p>
@@ skipping 286 matching lines @@
     Once you have references to an extension's pages,
     you can manipulate the DOM for each page.
   </li>
   <li>
     You can also make direct function calls to the pages,
     as shown in the following example.
   </li>
 </ul>
 
 <p>
-Here's an example of 
+Here's an example of
 communication between toolstrips and the background page.
 </p>
 
 <pre>
 //In background_page.html:
 function updateUI(checked) {
   var toolstrips = chrome.extension.getToolstrips();
   for (var i in toolstrips) {
     if (toolstrips[i].enableCheckbox)
       toolstrips[i].enableCheckbox(checked);
@@ skipping 16 matching lines @@
 <h2> Summary </h2>
 
 <p class="tbd">
 [
 PENDING: summarize, suggest where to go next. Probably:
 <a href="getstarted.html">Getting Started</a>,
 <a href="tut_debugging.html">Debugging</a>,
 <a href="devguide.html">Developer's Guide</a>.
 ]
 </p>