Skip to content

Commit

Permalink
feat: Hoodie default UI - add numbers to instructions (hoodiehq#494)
Browse files Browse the repository at this point in the history
  • Loading branch information
ArcadiusK authored and gr2m committed May 26, 2016
1 parent f6d240e commit f5f3148
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions public/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -12,13 +12,13 @@ <h1>Hello from Hoodie!</h1>

<h2>Get going with Hoodie</h2>

<p>Your first step should be creating a <code>public</code> folder inside your project folder.</p>
<p>Next up, just create your <strong>index.html</strong> inside that public directory.</p>
<p>We're almost here: Paste this into your <strong>index.html</strong> just before your closing tag for the body: <strong> &lt;script src="hoodie/client.js"&gt;&lt;/script&gt;</strong></p>
<p>1. Your first step should be creating a <code>public</code> folder inside your project folder.</p>
<p>2. Next up, just create your <strong>index.html</strong> inside that public directory.</p>
<p>3. We're almost here: Paste this into your <strong>index.html</strong> just before your closing tag for the body: <strong> &lt;script src="hoodie/client.js"&gt;&lt;/script&gt;</strong></p>
<p>This is necessary for your own javascript files to pick up the hoodie methods.</p>
<p>Now handle it just like you would handle your frontend project, hoodie won't get in your way. </p>
<p>Setup your asset folders and create your .css and .js files.</p>
<p>You’ll need to restart the Hoodie server so it servers assets from your app’s <code>public</code> folder</p>
<p>4. Setup your asset folders and create your .css and .js files.</p>
<p>5. You’ll need to restart the Hoodie server so it servers assets from your app’s <code>public</code> folder</p>

<p>If you want to learn more, check the <a href="http://docs.hood.ie/camp/">work-in-progress documentation</a></p>
<p>Happy coding :)</p>
Expand Down

0 comments on commit f5f3148

Please sign in to comment.