Extension Docs Server: Include a list of samples used in the api reference page.

chrome/common/extensions/docs/server2/templates/private/api_reference.html

Index: chrome/common/extensions/docs/server2/templates/private/api_reference.html
diff --git a/chrome/common/extensions/docs/server2/templates/private/api_reference.html b/chrome/common/extensions/docs/server2/templates/private/api_reference.html
index 29b8ca624485fec324e7ca8d10049d35df918cb1..1c34d5fafc42648aa6f00fb363fa2ba8bcc4b26a 100644
--- a/chrome/common/extensions/docs/server2/templates/private/api_reference.html
+++ b/chrome/common/extensions/docs/server2/templates/private/api_reference.html
@@ -1,3 +1,7 @@
+{{?api.samples}}<h2>Samples Using chrome.{{api.name}}</h2>{{/}}
+{{#api.samples}}
+  <li><code><a href="{{path}}.zip">{{name}}</a></code></li>
+{{/}}

[not at google - send to devlin, 2012/07/30 12:23:03]

I think this should be the last thing on the page, after the API reference. The
API reference is more likely to be what developers are looking for, not samples.

Also, a couple of ways I think it could be nicer:
- title should be "Samples extensions that use chrome.{{api.name}}"
- don't surround in <code></code>, it's not code.
- have the description after it, so like

<b>Stylizr</b> &ndash; blah blah blah.
<b>Other sample</b> &ndash; foo bar baz.

&ndash; cos it's a longer dash than - but I don't know how it'll look. Use your
judgement (there's also &mdash; along with other types of separators).

[chebert, 2012/07/31 22:41:33]

Done.

 <a name="apiReference"></a>
 <h2>API Reference: chrome.{{api.name}}</h2>
 <div class="api_reference">