list apis by channel info, e.g. dev, stable

chrome/common/extensions/docs/templates/articles/api_index.html

 <h1 class="page_title">Chrome Platform APIs</h1>
 {{?is_apps}}
 <p class="doc-family apps">
 Chrome provides many special-purpose APIs like
 <code>chrome.runtime</code> and <code>chrome.alarms</code>
 to Chrome Apps.
 </p>
 {{:is_apps}}

[not at google - send to devlin, 2013/10/31 00:05:26]

with respect to the comment below: just delete the second case here and always
show chrome.runtime and chrome.alarms (no is_apps check ever).

[hukun, 2013/11/01 09:31:52]

Done

 <p class="doc-family extensions">
 Chrome provides APIs such as
 <code>chrome.bookmarks</code> and <code>chrome.tab</code>
 so that extensions can interact with the browser.
 </p>
 {{/is_apps}}
 
 <h2 id="supported">Supported APIs</h2>
 
 <p>
 Here are the supported chrome.* APIs:
 </p>
 
-<ul>
+<p>
+Stable APIs

[not at google - send to devlin, 2013/10/31 00:05:26]

h2 not p

[hukun, 2013/11/01 09:31:52]

Done

+</p>
+<table>
+  <tr><td>API Name</td><td>API Description</td><td>Chrome Version</td></tr>

[not at google - send to devlin, 2013/10/31 00:05:26]

use th here. Also I'd just go with "Name" and "Description", the "API" is
implicit.

[hukun, 2013/11/01 09:31:52]

Done

   {{?is_apps}}
-  {{#api_list.apps.chrome}}
-  <li><a href="{{name}}.html">{{name}}</a></li>
-  {{/api_list.apps.chrome}}
+  {{#api_list.apps.chrome.stable}}

[not at google - send to devlin, 2013/10/31 00:05:26]

cleanup: change templates/public/apps/api_index.html and
templates/public/extensions/api_index.html to inject variables "stable_apis",
"beta_apis", and "dev_apis" rather than "is_apps". Then use those here.

For example, converting public/apps/api_index:

{{+partials.standard_apps_article article:intros.api_index is_apps:true}}

would change to

{{+partials.standard_apps_article article:intros.api_index
                                  stable_apis:api_list.apps.stable
                                  beta_apis:api_list.apps.beta
                                  dev_apis:api_list.apps.dev}}

then here

{{stable_apis}}
  <tr>..</tr>
{{/stable_apis}}

[hukun, 2013/11/01 09:31:52]

Done

+   <tr>
+     <td><a href="{{name}}.html">{{name}}</a></td>
+     <td>{{{description}}}</td>
+     <td>{{version}}</td>
+   </tr>
+  {{/api_list.apps.chrome.stable}}
   {{:is_apps}}
-  {{#api_list.extensions.chrome}}
-  <li><a href="{{name}}.html">{{name}}</a></li>
-  {{/api_list.extensions.chrome}}
+  {{#api_list.extensions.chrome.stable}}
+   <tr>
+     <td><a href="{{name}}.html">{{name}}</a></td>
+     <td>{{{description}}}</td>
+     <td>{{version}}</td>
+   </tr>
+  {{/api_list.extensions.chrome.stable}}
   {{/is_apps}}
-</ul>
+</table>
+
+
+<p>
+Beta APIs
+</p>
+<table>
+  <tr><td>API Name</td><td>API Description</td></tr>
+  {{?is_apps}}
+  {{#api_list.apps.chrome.beta}}
+   <tr>
+     <td><a href="{{name}}.html">{{name}}</a></td>
+     <td>{{{description}}}</td>
+   </tr>
+  {{/api_list.apps.chrome.beta}}
+  {{:is_apps}}
+  {{#api_list.extensions.chrome.beta}}
+   <tr>
+     <td><a href="{{name}}.html">{{name}}</a></td>
+     <td>{{{description}}}</td>
+   </tr>
+  {{/api_list.extensions.chrome.beta}}
+
+  {{/is_apps}}
+</table>
+
+<p>
+Dev APIs
+</p>
+<table>
+  <tr><td>API Name</td><td>API Description</td></tr>
+  {{?is_apps}}
+  {{#api_list.apps.chrome.dev}}
+   <tr>
+     <td><a href="{{name}}.html">{{name}}</a></td>
+     <td>{{{description}}}</td>
+   </tr>
+  {{/api_list.apps.chrome.dev}}
+  {{:is_apps}}
+  {{#api_list.extensions.chrome.dev}}
+   <tr>
+     <td><a href="{{name}}.html">{{name}}</a></td>
+     <td>{{{description}}}</td>
+   </tr>
+  {{/api_list.extensions.chrome.dev}}
+  {{/is_apps}}
+</table>
 
 <h2 id="experimental">Experimental APIs</h2>
 
 <p>
 Chrome also has
 <a href="experimental.html">experimental APIs</a>,
 some of which will become supported APIs
 in future releases of Chrome.
 </p>

[not at google - send to devlin, 2013/10/31 00:05:26]

hrm maybe we should move the trunk and experimental lists into this file too.

[hukun, 2013/11/01 09:31:52]

I will listen to your decision to go ahead.

 
 <h2 id="conventions">API conventions</h2>
 
 <p>
 Unless the doc says otherwise,
 methods in the chrome.* APIs are <b>asynchronous</b>:
 they return immediately,
 without waiting for the operation to finish.
 If you need to know the outcome of an operation,
 then you pass a callback function into the method.
 For more information, watch this video:
 </p>
 
 <p class="doc-family extensions">
 <iframe title="YouTube video player" width="640" height="390" src="//www.youtube.com/embed/bmxr75CV36A?rel=0" frameborder="0" allowfullscreen></iframe>
 </p>