Extensions Docs Server: Doc conversion script - SVN

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

 <meta name="doc-family" content="apps">
-<div id="pageData-name" class="pageData">Understand the Architecture</div>
-<div id="pageData-showTOC" class="pageData">true</div>
+<h1>Understand the Architecture</h1>
+
 
 <p>
 Packaged apps integrate closely with a user’s operating system.
 They are designed to be run outside of a browser tab,
 to run robustly in offline and poor connectivity scenarios and
 to have far more powerful capabilities than are available
 in a typical web browsing environment.
 The app container, programming, and security models
 support these packaged app requirements.
 </p>
@@ skipping 17 matching lines @@
 HTML documents with CSS and JavaScript;
 however, a packaged app is loaded in the app container,
 not in the browser tab.
 Also, the app container must load the main document
 of the packaged app from a local source.
 This forces all packaged apps to be at least minimally functional
 when offline and it provides a place
 to enforce stricter security measures.
 </p>
 
-<img src="../images/container.png"
+<img src="{{static}}/images/container.png"
      width="671"
      height="172"
      alt="how app container model works">
 
 
 <h2 id="programming">Programming model</h2>
 
 <p>
 The programming model describes the lifecycle
 and window behavior of packaged apps.
@@ skipping 111 matching lines @@
 they can only be used to load other app pages.
 You can use the <code>object</code> tag to
 <a href="app_external.html">embed external content</a>;
 this content runs in a separate process from the app.
 </p>
 
 <p>
 <iframe title="YouTube video player" width="610" height="380" src="http://www.youtube.com/embed/EDtiWN42lHs" frameborder="0" allowfullscreen></iframe>
 </p>
 
-<p class="backtotop"><a href="#top">Back to top</a></p>
+<p class="backtotop"><a href="#top">Back to top</a></p>