Extensions Docs Server: Doc conversion script

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

Index: chrome/common/extensions/docs/server2/templates/articles/about_apps.html
diff --git a/chrome/common/extensions/docs/server2/templates/articles/about_apps.html b/chrome/common/extensions/docs/server2/templates/articles/about_apps.html
index 66b218863975569958d0bcc16db514bef071c41e..7724f1b359ab380ec3029404c9a1344f00e1585b 100644
--- a/chrome/common/extensions/docs/server2/templates/articles/about_apps.html
+++ b/chrome/common/extensions/docs/server2/templates/articles/about_apps.html
@@ -1,4 +1,6 @@
+<meta name="doc-family" content="apps">
 <h1 class="page_title">What Are Packaged Apps?</h1>
+<div id="pageData-showTOC" class="pageData">true</div>
 <p>
 Packaged apps deliver an experience as capable as a native app,
 but as safe as a web page.
@@ -8,28 +10,25 @@ 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>
-
 <p>
 <iframe title="YouTube video player" width="610" height="380" src="http://www.youtube.com/embed/lBUGTVIJVfM" frameborder="0" allowfullscreen></iframe>
 </p>
-
 <p>
-With access to Chrome APIs and services
-not available to traditional web apps,
-you can build powerful apps that interact
-with network and hardware devices,
-as well as, media apps.
-Here's a short list of examples:
+Packaged apps have have access to Chrome APIs and services not available to
+traditional web sites. You can build powerful apps that interact with network
+and hardware devices, media tools, and much more. Here's a short list of
+examples:
 </p>
-
 <ul>
 	<li>Shells (VMWare, Citrix, SSH, RDP or VNC clients)</li>
 	<li>Music/video streaming</li>
 	<li>Photo/video/music editing</li>
 </ul>
-
+<p>
+Watch the <a href="http://www.youtube.com/watch?v=j8oFAr1YR-0">Chrome Apps
+Google I/O presentation</a> for an in-depth introduction.
+</p>
 <h2 id="look">How they look</h2>
-
 <p>
 When a user opens a packaged app,
 their focus is specifically on the tasks
@@ -43,14 +42,11 @@ that look like this (and you can style
 your windows in all different ways):
 </p>
 <br>
-
 <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.
@@ -59,34 +55,28 @@ Apps open and close quickly,
 and the system can shut apps down at any time to improve performance.
 Users can fully uninstall apps.
 </p>
-
 <p>
 Without any effort on your part, your apps will launch offline.
 But you will need to put some effort into making sure user data is stored locally while offline
 and then synced back up to your data server once online
 (see <a href="offline_apps.html">Offline First</a>).
 </p>
-
 <h2 id="develop">How to develop them</h2>
-
 <p>
 Packaged apps are modified web apps.
 You use the same code, frameworks, and tools of the web platform to write your apps.
 Some browser features have been removed, other web APIs have been disabled
 or changed to improve security and programming practices.
 </p>
-
 <p>
 New features have been added to help you build more native-like apps.
 The app container and programming models control how packaged apps look and behave.
 These models aim to provide users with a more native experience.
 Powerful APIs have been added so your apps can have native-like capabilities,
 and a serious security model is enforced to make sure these APIs are not abused.</p>
-
 <p>
 To learn more about how to develop packaged apps:
 </p>
-
 <ul>
 	<li>
 		<a href="app_architecture.html">Understanding the Architecture</a>
@@ -108,5 +98,4 @@ To learn more about how to develop packaged apps:
 		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>