Doc server manifest page generation

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

Index: chrome/common/extensions/docs/templates/articles/manifest_manifest_version.html
diff --git a/chrome/common/extensions/docs/templates/articles/manifest_manifest_version.html b/chrome/common/extensions/docs/templates/articles/manifest_manifest_version.html
new file mode 100644
index 0000000000000000000000000000000000000000..d95a4dcb820046a72e60bf9c21b30f0534b3ed7f
--- /dev/null
+++ b/chrome/common/extensions/docs/templates/articles/manifest_manifest_version.html
@@ -0,0 +1,31 @@
+<h1 id="manifest_version">manifest_version</h1>
+
+<p>
+One integer specifying the version of the manifest file format your package
+requires. As of Chrome 18, developers <em>should</em> specify <code>2</code>
+(without quotes) to use the format as described by this document:
+</p>
+
+<pre class="prettyprint"><span class="str">"manifest_version"</span><span class="pun">:</span><span class="pln"> </span><span class="lit">2</span></pre>
+
+<p>
+Consider manifest version 1 <em>deprecated</em> as of Chrome 18. Version 2 is
+not yet <em>required</em>, but we will, at some point in the not-too-distant
+future, stop supporting packages using deprecated manifest versions. Extensions,
+applications, and themes that aren't ready to make the jump to the new manifest
+version in Chrome 18 can either explicitly specify version <code>1</code>, or
+leave the key off entirely.
+</p>
+
+<p>
+The changes between version 1 and version 2 of the manifest file format are
+described in detail in <a href="http://developer.chrome.com/extensions/manifestVersion.html">the
+<code>manifest_version</code> documentation.</a>
+</p>
+
+<p class="caution">
+  Setting <code>manifest_version</code> 2 in Chrome 17 or lower is not
+  recommended. If your extension needs to work in older versions of Chrome,
+  stick with version 1 for the moment. We'll give you ample warning before
+  version 1 stops working.
+</p>