Browse files

bootstrap file is no more hosted on but on previ…

  • Loading branch information...
steren committed May 28, 2012
1 parent 0ecd845 commit f5ef502b5b231156e0ff321ffd2a37319d8919cb
Showing with 8 additions and 8 deletions.
  1. +8 −8 public/content/dev/develop/start.html
@@ -65,7 +65,7 @@ <h3 id="bootstrap-new">How to create the bootstrap script for a new template</h3
<li>Click on the arrow on the right, this should open the preview in a dedicated tab.</li>
<li>Using "view source", extract the link to the bootstrap script. It should look like:
<br/><code class="javascript">&lt;script data-joshfire-bootstraped src="/bootstrap/4f2958a5f83d5b3b52000087/4f2973fb89ec2f9d65000077/phone/"&gt;&lt;/script&gt;</code></li>
- <li>Prefix the address with <code></code> and add it to your template entry point</li>
+ <li>Prefix the address with <code></code> and add it to your template entry point</li>
<p>That's it. Now open your template's entry point in a Web browser to test its functionality.</p>
@@ -75,19 +75,19 @@ <h3 id="update">How to test a template update</h3>
<p>If the template you'd like to test is an update to an existing template, and provided the update does not change the manifest file, you do not need to go through the exercise explained above. Instead, you may use the factory to create an application that uses the original template and link to the generated bootstrap script to test the update on your local machine.</p>
<p>Replacing <code><em>[appid]</em></code> with the ID of your application (which appears in the link to the application in the applications list page), the bootstrap script for your template and application is available at:</p>
-<pre><code class="uri"><em>[appid]</em>/auto/auto/</code></pre>
+<pre><code class="uri"><em>[appid]</em>/auto/auto/</code></pre>
<p>You can then use the <code>src</code> attribute in the reference to the bootstrap script to test the template locally, for instance:</p>
<pre><code class="html">&lt;script data-joshfire-bootstrap
- src=""&gt;
+ src=""&gt;
<p>The factory also allows users to configure templates parameters differently for different families of devices. For instance, factory users may want to bind one of the template's datasources inputs with an RSS feed that only contains smaller images and shorter abstracts on mobile phones, while they may prefer to see more content on desktops.</p>
<p>From a template perspective, the existence of different configuration settings is entirely transparent: the bootstrap script that gets loaded when the Web application starts already exposes the right information for the user's device. To test this possibility during template development, you may replace the last <code>auto</code> in the above mentioned bootstrap generator address with the family name of the device whose configuration settings you'd like to test, for instance:</p>
-<pre><code class="uri"><em>[appid]</em>/auto/<strong>phone</strong>/
+<pre><code class="uri"><em>[appid]</em>/auto/<strong>phone</strong>/

0 comments on commit f5ef502

Please sign in to comment.