Extensions Docs Server: Doc conversion script - SVN

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

 <meta name="doc-family" content="apps">
-<div id="pageData-name" class="pageData">What Are Packaged Apps?</div>
-<div id="pageData-showTOC" class="pageData">true</div>
+<h1>What Are Packaged Apps?</h1>
+
 
 <p>
 Packaged apps deliver an experience as capable as a native app,
 but as safe as a web page.
 Just like web apps,
 packaged apps are written in HTML5, JavaScript, and CSS.
 But packaged apps look and behave like native apps,
 and they have native-like capabilities
 that are much more powerful than those available to web apps.
 </p>
@@ skipping 29 matching lines @@
 Packaged apps have no traditional chrome:
 the omnibox (address bar), tab strip,
 and other browser interface elements no longer appear.
 Like native apps, they don’t live within the browser.
 When launched, packaged apps can open in windows
 that look like this (and you can style
 your windows in all different ways):
 </p>
 <br>
 
-<img src="../images/editor.png"
+<img src="{{static}}/images/editor.png"
      width="770"
      height="586"
      alt="Text editor packaged app in a standalone window">
 
 <h2 id="behave">How they behave</h2>
 
 <p>
 Packaged app pages always load locally.
 This allows apps to be less dependent on the network.
 Once a user installs an app, they have full control over the app's lifecycle.
@@ skipping 44 matching lines @@
                 shows how to use the powerful network and hardware APIs,
                 and how to connect your app to other apps using web intents.
         </li>
         <li>
                 <a href="app_deprecated.html">Disabled Features</a>
                 describes the web features that have been disabled
                 and what to use in their place, where relevant.
         </li>
 </ul>
 
-<p class="backtotop"><a href="#top">Back to top</a></p>
+<p class="backtotop"><a href="#top">Back to top</a></p>