Linking AvailabilityFinder with APIDataSource and intro-table templates.

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

Index: chrome/common/extensions/docs/templates/private/intro_table.html
diff --git a/chrome/common/extensions/docs/templates/private/intro_table.html b/chrome/common/extensions/docs/templates/private/intro_table.html
new file mode 100644
index 0000000000000000000000000000000000000000..ec141dd24e633050c2b7bcb57d0dba7deaa4a96d
--- /dev/null
+++ b/chrome/common/extensions/docs/templates/private/intro_table.html
@@ -0,0 +1,25 @@
+<table class="intro">
+  {{#api.intro_list}}
+    <tr>
+      <td>
+        <strong>{{title}}:</strong>
+      </td>
+      <td>
+        {{#content}}
+          {{?link}}
+            <a href="{{link}}">{{text}}</a>
+          {{:link}}
+            {{?perm}}
+              <code>"{{perm}}"{{?text}}: [{{text}}]{{/text}}</code>
+            {{:perm}}
+              {{?text}}
+                {{{text}}}

[not at google - send to devlin, 2013/07/09 23:11:55]

so regarding your thing about not needing {{{ }}} - yes, it would be great not
to need it and to encode any styling into the model.

I think I made some comments earlier which allude to you hopefully not needing
the "perm" special case at all.

can this look like:

{{#content}}
  {{?link}}<a href="{{link}}">{{/}}
  {{?class}}<span class="{{class}}">{{/}}
  {{text}}
  {{?class}}</span>{{/}}
  {{?link}}</a>{{/}}
{{/content}}

it would be much simpler... though maybe it would look better expanded, dunno.

{{#content}}
  {{?link}}
    <a href="{{link}}">
  {{/link}}
  {{?class}}
    <span class="{{class}}">
  {{/class}}
  {{text}}
  {{?class}}
    </span>
  {{/class}}
  {{?link}}
    </a>
  {{/link}}
{{/content}}

maybe not.

[epeterson, 2013/07/16 00:28:23]

The "perm" special case is gone.

I think the {{{ }}}'s are going to be hard to avoid, at least with this model.

Currently, each node represents a piece of text wrapped in a span or link.

We'd need to be able to put text both before and after a link or span, and we'd
need to be able to do it multiple times for one block of text, as with an API
description, where there could be multiple spans or links present.

+              {{/text}}
+            {{/perm}}
+          {{/link}}
+          <br>
+        {{/content}}
+      </td>
+    </tr>
+  {{/api.intro_list}}
+</table>