Doc server manifest page generation

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

 <h1>What's New in Extensions?</h1>
 <!--  -->
 
 <p>
 This page lists the API and manifest changes
 made in recent releases.
 </p>
 
 <h2 id="26"> Google Chrome 26 </h2>
 
@@ skipping 48 matching lines @@
       non-persistent, using a feature we call
       <a href="event_pages.html">event pages</a>.
       Event pages run only while they're being used,
       and will unload when idle to save resources.
   </ul>
 
 <h2 id="21"> Google Chrome 21 </h2>
 
 <h4> New Features </h4>
   <ul>
-    <li>The <a href="manifest.html#sandbox">sandbox manifest entry</a> allows
+    <li>The <a href="manifest/sandbox.html">sandbox manifest entry</a> allows
       you to define some pages within your extension that are automatically run
       in a low-privilege sandbox. This sandbox is not bound by the
       <a href="contentSecurityPolicy.html">content_security_policy</a>.
     <li>The <a href="input.ime.html">IME</a> API allows extensions to implement
       <a href="http://en.wikipedia.org/wiki/Input_method">input method
       editors</a> on Chrome OS.
   </ul>
 
 <h4> Additions to Existing Features </h4>
   <ul>
@@ skipping 117 matching lines @@
     <li>The <a href="pageCapture.html">page capture API</a>
       lets you save a tab as MHTML.
     <li> The <a href="privacy.html">privacy API</a>
       lets you control usage of the features
       in Chrome that can affect a user's privacy policy.
   </ul>
 
 <h4> Manifest changes </h4>
   <ul>
     <li>The new
-      <a href="manifest.html#manifest_version">manifest version</a>
+      <a href="manifest/manifest_version.html">manifest version</a>
       field specifies the version of the manifest that your package requires.
       As of Chrome 18, you should use
       <a href="manifestVersion.html">manifest version 2</a>.
     <li>The new
       <a href="contentSecurityPolicy.html">Content Security Policy (CSP)</a>
       field is used to define an extension's policies
       towards the types of content
       that can be loaded and executed by the extension.
     <li>Most background pages only include a list of script files.
       For these background pages,
       you can use the new
       <a href="background_pages.html">background.scripts</a> property
       and Chrome will generate a background page for you.
     <li>The new
-      <a href="manifest.html#web_accessible_resources">web_accessible_resources</a>
+      <a href="manifest/web_accessible_resources.html">web_accessible_resources</a>
       field specifies the paths of packaged resources
       that are expected to be usable in the context of a web page.
   </ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
     <li>The <code>chrome.tabs</code>
     $ref:tabs.create and
     $ref:tabs.update methods
     now have an <code>openerTabId</code> parameter.
@@ skipping 23 matching lines @@
     <li>The management API's
     $ref:management.ExtensionInfo object
     now has a <code>disabledReason</code> property.
   </ul>
 
 <h4> Changes to existing APIs </h4>
 
   <ul>
     <li>The <a href="omnibox.html">omnibox API</a>
     now works in
-    <a href="manifest.html#incognito">split incognito mode</a>.
+    <a href="manifest/incognito.html">split incognito mode</a>.
   </ul>
 
 <h2 id="16"> Google Chrome 16 </h2>
 
 <h4> New APIs </h4>
   <ul>
     <li>The
       <a href="webNavigation.html">web navigation API</a>
       lets extensions receive notifications about the status
       of navigation requests.
       You can use this API to track navigation events.
     <li>The
       <a href="permissions.html">optional permissions API</a>
       lets you control when users are presented with permission requests.
     <li>The
       <a href="contentSettings.html">content settings API</a>
       lets extensions customize Chrome’s behavior
       on a per-site basis instead of globally.
       You can use this API to control whether websites can use features
       such as cookies, JavaScript, and plug-ins.
   </ul>
 
 <h4> Manifest changes </h4>
   <ul>
     <li>The new
-      <a href="manifest.html#requirements">requirements</a> field
+      <a href="manifest/requirements.html">requirements</a> field
       allows you to declare extension requirements up front.
       For example, you can use this field
       to specify that your app requires 3D graphics support
       in order to use features such as CSS 3D Tranforms or WebGL.
   </ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
     <li>The new
     $ref:tabs.query method
@@ skipping 44 matching lines @@
 <ul>
  <li>The <a href="webstore.html">webstore API</a>
  lets you initiate app and extensions installations
  <a href="http://code.google.com/chrome/webstore/docs/inline_installation.html">"inline"</a>
  from your site.
 </ul>
 
 <h4> Manifest changes </h4>
   <ul>
     <li>The new
-      <a href="manifest.html#offline_enabled">offline_enabled</a> field
+      <a href="manifest/offline_enabled.html">offline_enabled</a> field
       lets you specify that your app works well even without an internet
       connection.
   </ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
     <li>You can retrieve permission warnings using the new management API methods
       $ref:management.getPermissionWarningsById
       and
       $ref:management.getPermissionWarningsByManifest.
@@ skipping 28 matching lines @@
       <a href="http://code.google.com/chrome/nativeclient/">Native Client documentation</a>.
   </ul>
 
 <h4> Manifest changes </h4>
   <ul>
     <li>The new
       <a href="contentSecurityPolicy.html">content_security_policy</a> field
       can help prevent
       <a href="http://blog.chromium.org/2011/07/writing-extensions-more-securely.html">cross-site scripting vulnerabilities</a>
       in your extension.
-    <li>The new <a href="manifest.html#nacl_modules">nacl_modules</a> field
+    <li>The new <a href="manifest/nacl_modules.html">nacl_modules</a> field
       lets you register Native Client modules
       as content handlers for MIME types.
   </ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
     <li><a href="contextMenus.html">Context menu</a> items
       can now appear even in documents
       that have file:// or chrome:// URLs.
       Previously, they were restricted to documents with
@@ skipping 139 matching lines @@
 <h2 id="9"> Google Chrome 9 </h2>
 
 <h4> New APIs </h4>
   <ul>
     <li>The <a href="omnibox.html">omnibox API</a> allows you to
       register a keyword with Chrome's address bar.
   </ul>
 
 <h4> Manifest changes </h4>
   <ul>
-    <li>The <a href="manifest.html#homepage_url">homepage_url</a> field
+    <li>The <a href="manifest/homepage_url.html">homepage_url</a> field
       lets you specify the extension or app's homepage.
   </ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
     <li>The $ref:tabs.Tab object
       now has a <code>pinned</code> property
       that's reflected in various <code>chrome.tabs</code> methods.
       For example,
       you can $ref:tabs.create
@@ skipping 21 matching lines @@
   <ul>
     <li>All users can now install
       <a href="http://code.google.com/chrome/apps/index.html">apps</a>;
       packaged apps can use extension APIs.
     <li>The <a href="management.html">management API</a>
       lets you work with installed apps and extensions.
   </ul>
 
 <h4> Manifest changes </h4>
   <ul>
-    <li>Introduced <a href="manifest.html#incognito">split incognito</a>
+    <li>Introduced <a href="manifest/incognito.html">split incognito</a>
       mode as the default for installable web apps
       (also available to extensions).
     <li>The <a href="tabs.html">tabs API</a>
       <code>create()</code> and <code>update()</code> methods
       no longer require the "tabs" permission, removing one common cause of
       <a href="permission_warnings.html">scary dialogs</a>.
   </ul>
 
 
 <h2 id="6">Google Chrome 6</h2>
@@ skipping 16 matching lines @@
     <li>A new 
       $ref:windows.WINDOW_ID_NONE constant
       identifies when focus shifts away from the browser.
     <li>The new 
       $ref:tabs.getCurrent method
       returns the tab associated with the currently executing script.
   </ul>
 
 <h4> Manifest changes </h4>
   <ul>
-    <li>The <a href="manifest.html#geolocation">geolocation</a> permission
+    <li>The <a href="manifest/geolocation.html">geolocation</a> permission
       gives an extension access to the user's physical location.
     <li><a href="match_patterns.html">Match patterns</a> can now select all
       schemes or all URLs.
     <li>Access to file:/// URLs no longer triggers the "access to your machine"
       security warning, but now requires user opt-in from the extensions
       management page.
   </ul>