Moving home and pillar pages to public folder

chrome/common/extensions/docs/templates/public/home/pillar.html

Index: chrome/common/extensions/docs/templates/public/home/pillar.html
diff --git a/chrome/docs/platform-pillar.html b/chrome/common/extensions/docs/templates/public/home/pillar.html
similarity index 81%
copy from chrome/docs/platform-pillar.html
copy to chrome/common/extensions/docs/templates/public/home/pillar.html
index 2a0989c099e4f4b8179a8a1c17e8ff03d2364665..371a263b44564c599ed9f696ea4f3455c49520b8 100644
--- a/chrome/docs/platform-pillar.html
+++ b/chrome/common/extensions/docs/templates/public/home/pillar.html
@@ -1,4 +1,3 @@
-{{+content:partials.site}}
 <div class="pillar-content">

[not at google - send to devlin, 2014/01/23 03:38:59]

I don't understand this change. Why did you remove {{+content:partials.site}}
from it? Why did a bunch of the <img> paths change?

[mkearney1, 2014/01/23 04:07:45]

Done.

 
   <h1>Chrome Platform</h1>
@@ -14,7 +13,7 @@
     <a href="http://chrome.blogspot.com/2013/12/a-new-breed-of-chrome-apps-now.html">Chrome App Launcher</a>:
     </p>
     <p><a href="/apps/first_app.html">Learn more</a></p>
-    <img src="{{static}}/images/platform-pillar/chrome_apps.png" alt="500px Chrome App launched from Chrome App Launcher">
+    <img src="{{static}}/images/pillar/chrome_apps.png" alt="500px Chrome App launched from Chrome App Launcher">
     </article>
     
     <article>
@@ -23,7 +22,7 @@
     <p>The goal of this codelab is to get you building Chrome Apps fast.
     Once you've completed this codelab, you will have a simple Todo app.</p>
     <p><a href="/apps/app_codelab1_setup.html">Learn more</a></p>
-    <img src="{{static}}/images/platform-pillar/todo_codelab.png"
+    <img src="{{static}}/images/pillar/todo_codelab.png"
          width="110%"
          alt="Create this simple Todo Chrome App.">
     </article>
@@ -35,7 +34,7 @@
     <a href="https://github.com/GoogleChrome/chrome-app-samples">chrome-apps-samples GitHub repository</a>.
     The <a href="https://github.com/GoogleChrome/chrome-app-samples/blob/master/README.md">README.md</a>
     lists each sample's APIs and provides a link to download in the Chrome Web Store.</p>
-    <img src="{{static}}/images/platform-pillar/chrome_app_samples.png" alt="Chrome apps samples maintained in GitHub repository">
+    <img src="{{static}}/images/pillar/chrome_app_samples.png" alt="Chrome apps samples maintained in GitHub repository">
     </article>
 
     <article>
@@ -63,7 +62,7 @@
     <a href="/apps/syncFileSystem.html">syncFileSystem API</a>
     to save and synchronize caching data in Google Drive.</p>
     <p><a href="/apps/offline_apps.html">Learn more</a></p>
-    <img src="{{static}}/images/platform-pillar/sync_file_system.png" alt="Use Google Drive to store Chrome Apps data in the cloud.">
+    <img src="{{static}}/images/pillar/sync_file_system.png" alt="Use Google Drive to store Chrome Apps data in the cloud.">
     </article>
 
     <article>
@@ -88,7 +87,7 @@ for TCP and UDP connections.</li>
     enhance the functionality of the Chrome browser.
     Write extensions using web technologies: HTML, JavaScript, and CSS.</p>
     <p><a href="/extensions/overview.html">Learn more</a></p>
-    <img src="{{static}}/images/platform-pillar/extensions.png" alt="Browser action and page actions are common extension types.">
+    <img src="{{static}}/images/pillar/extensions.png" alt="Browser action and page actions are common extension types.">
     </article>
 
     <article>
@@ -98,7 +97,7 @@ for TCP and UDP connections.</li>
     of a simple browser action extension.
     Clicking the browser action UI element opens a pop-up window.</p>
     <p><a href="/extensions/getstarted.html">Learn more</a></p>
-    <img src="{{static}}/images/platform-pillar/one_click_kittens.png" alt="One-click kittens tutorial">
+    <img src="{{static}}/images/pillar/one_click_kittens.png" alt="One-click kittens tutorial">
     </article>
 
     <article>
@@ -108,7 +107,7 @@ for TCP and UDP connections.</li>
     each sample lists API methods and links to source files.
     Filter by keyword or API:</p>
     <p><a href="/extensions/samples.html">Learn more</a></p>
-    <img src="{{static}}/images/platform-pillar/extension_samples.png" alt="Extension samples page">
+    <img src="{{static}}/images/pillar/extension_samples.png" alt="Extension samples page">
     </article>
 
     <article>
@@ -139,7 +138,7 @@ for TCP and UDP connections.</li>
     New feature! You can now
     <a href="/webstore/payments-otp">monetize your extensions</a>!</p>
     <p><a href="/extensions/hosting.html">Learn more</a></p>
-    <img src="{{static}}/images/platform-pillar/upload_extensions.png" alt="Upload extensions on chrome://extensions page.">
+    <img src="{{static}}/images/pillar/upload_extensions.png" alt="Upload extensions on chrome://extensions page.">
     </article> 
     <article>
     <h4 class="label">Extensions</h4>
@@ -151,7 +150,7 @@ for TCP and UDP connections.</li>
     <a href="https://chrome.google.com/webstore/category/themes">Chrome Web Store</a>.
     </p>
     <p><a href="/extensions/themes.html">Learn more</a></p>
-    <img src="{{static}}/images/platform-pillar/theme.png" alt="Grass theme">
+    <img src="{{static}}/images/pillar/theme.png" alt="Grass theme">
     </article>
 
     <article class="new">
@@ -160,8 +159,8 @@ for TCP and UDP connections.</li>
     <p>Native Client is a sandbox for running compiled C and C++ code in the browser.
     Portable Native Client extends that technology with architecture independence,
     letting developers compile their code once to run in any website and on any architecture.</p>
-    <p><a href="/native-client/index.html">Learn more</a></p>
-    <img src="{{static}}/images/platform-pillar/pnacl_intro.png" alt="Watch a live recorded conversation on Native Client.">
+    <p><a href="/native-client/dev/index.html">Learn more</a></p>
+    <img src="{{static}}/images/pillar/pnacl_intro.png" alt="Watch a live recorded conversation on Native Client.">
     </article>
 
     <article>
@@ -170,15 +169,15 @@ for TCP and UDP connections.</li>
     
     <p>This multi-part tutorial explains how to get started developing applications with Native Client.</p>
 
-    <p><a href="/native-client/devguide/tutorial/tutorial-part1">Part one</a>
+    <p><a href="/native-client/dev/devguide/tutorial/tutorial-part1">Part one</a>
     shows how to build and run a simple web application
     using Portable Native Client (PNaCl).</p>
     
-    <p><a href="/native-client/devguide/tutorial/tutorial-part2">Part two</a>
+    <p><a href="/native-client/dev/devguide/tutorial/tutorial-part2">Part two</a>
     shows how to convert the finished PNaCl web application
     to use the Native Client SDK build system and common JavaScript files.
     </p>
-    <p><a href="/native-client/devguide/tutorial/tutorial-part1">Learn more</a></p>
+    <p><a href="/native-client/dev/devguide/tutorial/tutorial-part1">Learn more</a></p>
     </article>
 
     <article>
@@ -193,7 +192,7 @@ for TCP and UDP connections.</li>
       to download particular bundles that are available.</li>
     </ol>
     </p>
-    <p><a href="/native-client/sdk/download">Learn more</a></p>
+    <p><a href="/native-client/dev/sdk/download">Learn more</a></p>
     </article>
 
     <article>
@@ -201,14 +200,14 @@ for TCP and UDP connections.</li>
     <h2>Development Cycle</h2>
     <p>End-to-end native client development workflow:
     <ul>
-    <li><a href="/native-client/devguide/devcycle/building.html">Build</a>
+    <li><a href="/native-client/dev/devguide/devcycle/building.html">Build</a>
 Native Client modules.</li>
-    <li><a href="/native-client/devguide/devcycle/running.html">Run</a>
+    <li><a href="/native-client/dev/devguide/devcycle/running.html">Run</a>
 Native Client applications during development.</li>
-    <li><a href="/native-client/devguide/devcycle/debugging.html">Debug, monitor, and measure</a>
+    <li><a href="/native-client/dev/devguide/devcycle/debugging.html">Debug, monitor, and measure</a>
 Native Client application performance.</li>
     </ul></p>
-    <p><a href="/native-client/devguide/devcycle/building.html">Learn more</a></p>
+    <p><a href="/native-client/dev/devguide/devcycle/building.html">Learn more</a></p>
     </article>
 
     <article>
@@ -218,26 +217,26 @@ Native Client application performance.</li>
     Learn:
     <ul>
     <li>How Native Client applications are
-    <a href="/native-client/devguide/coding/application-structure.html">structured</a></li>
+    <a href="/native-client/dev/devguide/coding/application-structure.html">structured</a></li>
     <li>Which classes and functions to implement in your
-<a href="/native-client/devguide/coding/native-client-modules.html">Native Client module</a> for Chrome to load, initialize, and run it</li>
+<a href="/native-client/dev/devguide/coding/native-client-modules.html">Native Client module</a> for Chrome to load, initialize, and run it</li>
     <li>How to use the
-    <a href="/native-client/devguide/coding/message-system.html">messaging system</a>
+    <a href="/native-client/dev/devguide/coding/message-system.html">messaging system</a>
     to communicate between the JavaScript code and
     the Native Client module's C or C++code</li>
     </ul>    
     And much more!</p>
-    <p><a href="/native-client/devguide/coding/application-structure.html">Learn more</a></p>
+    <p><a href="/native-client/dev/devguide/coding/application-structure.html">Learn more</a></p>
     </article>
 
     <article>
     <h4 class="label">Native Client</h4>
-    <h2>Pepper API</h2>
-    <p>The Pepper API lets Native Client modules communicate
+    <h2>Pepper API Reference</h2>
+    <p>The Pepper API reference lets Native Client modules communicate
     with the hosting browser and access system-level functions in a safe and portable way.
     Pepper has both a
-    <a href="/native-client/pepperc/index.html">C API</a> and a
-    <a href="/native-client/peppercpp/index.html">C++ API</a>.</p>
+    <a href="/native-client/dev/pepperc/index.html">C API</a> and a
+    <a href="/native-client/dev/peppercpp/index.html">C++ API</a>.</p>
 
     <p>These APIs are generally divided into two parts:
     <ul><li>Functions implemented in the browser
@@ -247,7 +246,7 @@ Native Client application performance.</li>
     </li>
     </ul>
     </p>
-    <p><a href="/native-client/overview.html#pepper-plugin-api">Learn more</a></p>
+    <p><a href="/native-client/dev/pepperc/index.html">Learn more</a></p>
     </article>
 
     <article>
@@ -258,7 +257,7 @@ Native Client application performance.</li>
     your Chrome Apps, Extensions, and Themes
     where Chrome users can easily find them.</p>
     <p><a href="/webstore/index.html">Learn more</a></p>
-    <img src="{{static}}/images/platform-pillar/chrome_web_store.png" alt="Publish apps, extensions, and themes in Chrome Web Store.">
+    <img src="{{static}}/images/pillar/chrome_web_store.png" alt="Publish apps, extensions, and themes in Chrome Web Store.">
     </article>
 
     <article>
@@ -284,7 +283,7 @@ Native Client application performance.</li>
     <p>Follow the Chrome Web Store branding guidelines
 for supplying images and promotional assets.</p>
     <p><a href="/webstore/branding.html">Learn more</a></p>
-    <img src="{{static}}/images/platform-pillar/ChromeWebStore_BadgeWBorder_v2_206x58.png" alt="Using the Chrome Web Store badge">
+    <img src="{{static}}/images/pillar/ChromeWebStore_BadgeWBorder_v2_206x58.png" alt="Using the Chrome Web Store badge">
     </article>
 
     <article class="new">
@@ -296,7 +295,7 @@ for supplying images and promotional assets.</p>
     <a href="/apps/google_wallet.html">Google Wallet for Digital Goods</a>
     to sell digital or virtual goods in your Chrome Apps or Extensions.</p>
     <p><a href="/webstore/money.html">Learn more</a></p>
-    <img src="{{static}}/images/platform-pillar/wallet-review.png"
+    <img src="{{static}}/images/pillar/wallet-review.png"
          width="250px"
          alt="Using Google Wallet in apps and extensions">
     </article>
@@ -310,7 +309,7 @@ for supplying images and promotional assets.</p>
     Uploading generates an app ID,
     which you may need to complete your application code.</p>
     <p><a href="/webstore/publish.html">Learn more</a></p>
-    <img src="{{static}}/images/platform-pillar/store_developer_dashboard.png" alt="Chrome Web Store Developer Dashboard">
+    <img src="{{static}}/images/pillar/store_developer_dashboard.png" alt="Chrome Web Store Developer Dashboard">
     </article>
 
     <article>
@@ -372,4 +371,3 @@ for supplying images and promotional assets.</p>
   </section>
 
 </div>
-{{/partials.site}}