Doc server manifest page generation

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

 <h1>Tutorial: Migrate to Manifest V2</h1>
 
 <p>
 Manifest version 1 was deprecated in Chrome 18,
 and support will be phased out according to the
 <a href="manifestVersion.html#manifest-v1-support-schedule">manifest version 1 support schedule</a>.
 The changes from version 1 to version 2
 fall under two broad categories:
 API changes and Security changes. 
 </p>
@@ skipping 65 matching lines @@
   <li>Are you using inline event handlers (like onclick, etc)?</li>
     <ul>
       <li>Remove them from the HTML code,
         move them into an external JS file and
         use <code>addEventListener()</code> instead.</li>
     </ul>
   <li>Does your extension inject content scripts into Web pages
     that need to access resources (like images and scripts)
     that are contained in the extension’s package?</li>
     <ul>
-      <li>Define the <a href="manifest.html#web_accessible_resources">web_accessible_resources</a>
+      <li>Define the <a href="manifest/web_accessible_resources.html">web_accessible_resources</a>
         property and list the resources
         (and optionally a separate Content Security Policy for those resources).</li>
     </ul>
   <li>Does your extension embed external Web pages?</li>
     <ul>
-      <li>Define the <a href="manifest.html#sandbox">sandbox</a> property.</li>
+      <li>Define the <a href="manifest/sandbox.html">sandbox</a> property.</li>
     </ul>
   <li>Is your code or library using <code>eval()</code>, new <code>Function()</code>,
     <code>innerHTML</code>, <code>setTimeout()</code>, or otherwise passing strings
     of JS code that are dynamically evaluated?</li>
     <ul>
       <li>Use <code>JSON.parse()</code>
         if you’re parsing JSON code into an object.</li>
       <li>Use a CSP-friendly library,
         for example, <a href="http://angularjs.org/">AngularJS</a>.</li>
       <li>Create a sandbox entry in your manifest and
@@ skipping 154 matching lines @@
 <p>
 There are some scenarios where your extension might embed content
 that can be used externally or come from an external source. 
 </p>
 
 <p>
 <strong>Extension content in web pages:</strong><br>
 If your extension embeds resources (like images, script, CSS styles, etc)
 that are used in content scripts that are injected into web pages,
 you need to use the
-<a href="manifest.html#web_accessible_resources">web_accessible_resources</a> property
+<a href="manifest/web_accessible_resources.html">web_accessible_resources</a> property
 to whitelist these resources so that external Web pages can use them:
 </p>
 
 <pre>
 { // manifest file
 ...
   "<strong>web_accessible_resources</strong>": [
     "images/image1.png",
     "script/myscript.js"
   ],
@@ skipping 71 matching lines @@
 For more information about using sandboxing to isolate unsafe code,
 read the <a href="sandboxingEval.html">sandboxing eval</a> article.
 You can learn more about Content Security Policy
 by visiting our extensions-related tutorial and a
 <a href="http://www.html5rocks.com/en/tutorials/security/content-security-policy/">good introduction on HTML5Rocks</a>.
 </p>