Rework API reference pages

chrome/common/extensions/docs/templates/private/api_summary.html

Index: chrome/common/extensions/docs/templates/private/api_summary.html
diff --git a/chrome/common/extensions/docs/templates/private/api_summary.html b/chrome/common/extensions/docs/templates/private/api_summary.html
new file mode 100644
index 0000000000000000000000000000000000000000..c9e1264ab4ed98d4842cce447f53166b767ffed8
--- /dev/null
+++ b/chrome/common/extensions/docs/templates/private/api_summary.html
@@ -0,0 +1,38 @@
+<section id="toc">
+<h2>Summary</h2>
+<table class="api-summary">
+  <tr>
+  {{?api.types}}
+    <tr><th colspan="2">Types</th></tr>

[Jeffrey Yasskin, 2014/02/07 02:40:03]

This table only has one column.

+    {{#t:api.types}}
+      <tr><td><a href="#{{t.id}}">{{t.name}}</a></td></tr>
+    {{/}}
+  {{/api.types}}
+  {{?api.properties}}
+    <tr><th colspan="2">Properties</th></tr>
+    {{#p:api.properties}}
+      <tr><td><a href="#{{p.id}}">{{p.name}}</a></td>

[Jeffrey Yasskin, 2014/02/07 02:40:03]

Why do we list just the basename of the properties and events, but spell out
chrome.namespace.function?

[Jeffrey Yasskin, 2014/02/07 02:40:03]

This row is missing its </tr>. It's not required by HTML, but we should be
consistent.

+    {{/}}
+  {{/api.properties}}
+  {{?api.functions}}
+    <tr><th colspan="2">Methods</th></tr>
+    {{#f:api.functions}}
+      <tr><td><a href="#{{f.id}}">
+        {{+partials.function_signature function:f api:api disableLink:f.id/}}
+      </a></td></tr>
+    {{/}}
+  {{/api.functions}}
+  {{?api.events}}
+    <tr><th colspan="2">Events</th></tr>
+    {{#e:api.events}}
+      <tr><td><a href="#{{e.id}}">{{e.name}}</a></td></tr>
+    {{/}}
+  {{/api.events}}
+  {{?api.domEvents}}
+    <tr><th colspan="2">DOM Events</th></tr>
+    {{#e:api.domEvents}}
+      <tr><td><a href="#{{e.id}}">{{e.name}}</a></td></tr>
+    {{/api.domEvents}}
+  {{/api.domEvents}}
+</table>
+</section>