Doc server manifest page generation

chrome/common/extensions/docs/templates/articles/manifest/requirements.html

Index: chrome/common/extensions/docs/templates/articles/manifest/requirements.html
diff --git a/chrome/common/extensions/docs/templates/articles/manifest/requirements.html b/chrome/common/extensions/docs/templates/articles/manifest/requirements.html
new file mode 100644
index 0000000000000000000000000000000000000000..da7f0fe6e28d4cea7f2147d832d2e3220055dc10
--- /dev/null
+++ b/chrome/common/extensions/docs/templates/articles/manifest/requirements.html
@@ -0,0 +1,47 @@
+<h1 id="requirements">Manifest - Requirements</h1>
+
+<p>
+Technologies required by the app or extension.
+Hosting sites such as the Chrome Web Store may use this list
+to dissuade users from installing apps or extensions
+that will not work on their computer.
+Supported requirements currently include "3D" and "plugins";
+additional requirements checks may be added in the future.
+</p>
+
+<p>
+The "3D" requirement denotes GPU hardware acceleration.
+The "webgl" requirement refers to the
+<a href="http://www.khronos.org/webgl/">WebGL API</a>.
+For more information on Chrome 3D graphics support,
+see the help article on
+<a href="http://www.google.com/support/chrome/bin/answer.py?answer=1220892">WebGL and 3D graphics</a>.
+You can list the 3D-related features your app requires,
+as demonstrated in the following example:
+</p>
+
+<pre class="prettyprint"><span class="str">"requirements"</span><span class="pun">:</span><span class="pln"> </span><span class="pun">{</span><span class="pln">
+  </span><span class="str">"3D"</span><span class="pun">:</span><span class="pln"> </span><span class="pun">{</span><span class="pln">
+    </span><span class="str">"features"</span><span class="pun">:</span><span class="pln"> </span><span class="pun">[</span><span class="str">"webgl"</span><span class="pun">]</span><span class="pln">
+  </span><span class="pun">}</span><span class="pln">
+</span><span class="pun">}</span></pre>
+
+<p>
+The "plugins" requirement indicates
+if an app or extension requires NPAPI to run.
+This requirement is enabled by default
+when the manifest includes the
+<a href="http://developer.chrome.com/extensions/npapi.html">"plugins" field</a>.
+For apps and extensions that still work when plugins aren't available,
+you can disable this requirement
+by setting NPAPI to false.
+You can also enable this requirement manually,
+by setting NPAPI to true,
+as shown in this example:
+</p>
+
+<pre class="prettyprint"><span class="str">"requirements"</span><span class="pun">:</span><span class="pln"> </span><span class="pun">{</span><span class="pln">
+  </span><span class="str">"plugins"</span><span class="pun">:</span><span class="pln"> </span><span class="pun">{</span><span class="pln">
+    </span><span class="str">"npapi"</span><span class="pun">:</span><span class="pln"> </span><span class="kwd">true</span><span class="pln">
+  </span><span class="pun">}</span><span class="pln">
+</span><span class="pun">}</span></pre>