Update pages to link to the next chapter

coffeescript/01_introduction.html

@@ -74,8 +74,8 @@ <h2>Initial setup</h2>
 <p>As you can see above, the default extension of CoffeeScript files is <code>.coffee</code>. Amongst other things, this will allow text editors like <a href="http://macromates.com/">TextMate</a> to work out which language the file contains, giving it the appropriate syntax highlighting. By default, TextMate doesn't include support for CoffeeScript, but you can easily install the <a href="https://github.com/jashkenas/coffee-script-tmbundle">bundle to do so</a>.</p>
 
 <p>If all this compilation seems like a bit of an inconvenience and bother, that's because it is. We'll be getting onto ways to solve this by automatically compiling CoffeeScript files, but first lets take a look at the language's syntax.</p>
-
+    <div class="back"><a href="02_syntax.html">Chapter 2 (CoffeeScript Syntax) &raquo;</a></div>
   </div>
 </div>
 </body>
-</html>
+</html>

coffeescript/02_syntax.html

@@ -410,8 +410,8 @@ <h2>Aliases &amp; the Existential Operator</h2>
 
 <pre><code>blackKnight.getLegs().kick?()
 </code></pre>
-
+  `<div class="back"><a href="03_classes.html">Chapter 3 (Classes) &raquo;</a></div>
   </div>
 </div>
 </body>
-</html>
+</html>

coffeescript/03_classes.html

@@ -246,8 +246,8 @@ <h2>Extending classes</h2>
 </code></pre>
 
 <p>Super simple and elegant!</p>
-
+    <div class="back"><a href="04_idioms.html">Chapter 4 (Idioms) &raquo;</a></div>
   </div>
 </div>
 </body>
-</html>
+</html>

coffeescript/04_idioms.html

@@ -279,8 +279,8 @@ <h2>Private variables</h2>
 </code></pre>
 
 <p>In other words, <code>classToType</code> is completely private, and can never again be referenced outside the executing anonymous function. This pattern is a great way of encapsulating scope and hiding variables.</p>
-
+    <div class="back"><a href="05_compiling.html">Chapter 5 (Compiling) &raquo;</a></div>
   </div>
 </div>
 </body>
-</html>
+</html>

coffeescript/05_compiling.html

@@ -126,8 +126,8 @@ <h2>Server side support</h2>
 <p>Django also has <a href="http://pypi.python.org/pypi/django-coffeescript/">support for CoffeeScript</a> through special template tags. It works with both inline code and external files.</p>
 
 <p>Both Ruby and Python pipe out to Node and the CoffeeScript lib behind the scenes when compiling CoffeeScript, so you'll need to have those installed during development. If you're using Node directly as a backend for your site, CoffeeScript integration is even simpler and you can use it for both the backend and frontend code. We're going to talk more about this in the next chapter, using <a href="https://github.com/sstephenson/stitch">Stitch</a> to serve all our client-side CoffeeScript.</p>
-
+    <div class="back"><a href="06_applications.html">Chapter 6 (Applications) &raquo;</a></div>
   </div>
 </div>
 </body>
-</html>
+</html>

coffeescript/06_applications.html

@@ -290,8 +290,8 @@ <h2>Additional libraries</h2>
 <p>As for serving up application, <a href="http://github.com/maccman/hem">Hem</a> is a great choice, supporting both CommonJS and NPM modules and integrating seamlessly with the CoffeeScript MVC framework <a href="http://spinejs.com">Spine</a>. <a href="https://github.com/substack/node-browserify">node-browsify</a> is another similar project. Or if you want to go lower level with <a href="http://expressjs.com/">express</a> integration, there's Trevor Burnham's <a href="https://github.com/TrevorBurnham/connect-assets">connect-assets</a></p>
 
 <p>You can find a full list of CoffeeScript web framework plugins, on the <a href="https://github.com/jashkenas/coffee-script/wiki/Web-framework-plugins">project's wiki</a>.</p>
-
+    <div class="back"><a href="07_the_bad_parts.html">Chapter 7 (The Bad Parts) &raquo;</a></div>
   </div>
 </div>
 </body>
-</html>
+</html>