Extensions Docs Server: Split apps from extensions

chrome/common/extensions/docs/server2/templates/articles/experimental_apps.html

+<h1 class="page_title">chrome.experimental.* APIs</h1>
+
+<h2 id="overview">
+List of APIs
+</h2>
+
+<ul>
+  {{#api_list.apps.experimental}}
+  <li><a href="{{name}}.html">{{name}}</a></li>
+  {{/}}
+</ul>
+
+<p class="warning">
+<b>Caution:</b>
+Don't depend on these experimental APIs.
+They might disappear,
+and they <em>will</em> change.
+Also, the Chrome Web Store doesn't allow you to
+upload items that use experimental APIs.
+</p>
+
+
+<h2 id="using">How to use experimental APIs</h2>
+
+<ol>
+  <li>
+    Specify the "experimental"
+    <a href="manifest.html#permissions">permission</a>
+    in your manifest, like this:
+<pre>
+"permissions": [
+  <b>"experimental"</b>,
+  ...
+],
+</pre>
+  </li>
+  <li>
+    Enable the experimental API in your browser.
+    You can do this in either of two ways:
+    <ul>
+      <li> Go to <b>chrome://flags</b>,
+        find "Experimental Extension APIs",
+        click its "Enable" link,
+        and restart Chrome.
+        From now on,
+        unless you return to that page and disable experimental APIs,
+        you'll be able to run extensions and apps that use experimental APIs.
+      </li>
+      <li> Specify the <b>--enable-experimental-extension-apis</b> flag
+        each time you launch the browser.
+        On Windows, you can do this by modifying
+        the properties of the shortcut that you use to launch Google Chrome.
+        For example:
+
+<pre>
+<em>path_to_chrome.exe</em> <b>--enable-experimental-extension-apis</b></pre>
+      </li>
+    </ul>
+  </li>
+
+</ol>
+
+<h2 id="other">More APIs</h2>
+
+<p>
+For information on the standard APIs that packaged apps can use, see
+<a href="api_index.html">chrome.* APIs</a> and
+<a href="api_other.html">Other APIs</a>.
+</p>