Add links for site navigation
Include CSS classes which will be meaningful after we use Bootstrap web design framework
Add an image link on home page

Change-Id: Ic15ded101d330b4cf9a92542ce75f819edac4ee0
Include the Bootstrap gem (rails uses SASS but Bootstrap is using LESS CSS, thus we use bootstrap-sass gem which converts LESS to SASS)

Change-Id: I52a0c3c44327b5a4b1b92affb06c2804c91ca906
Custom CSS

Change-Id: I995f8416ea62fee983009ce9a245bdddf05c5fa3
Re-package the application structure using Partials

Change-Id: Ia3587cc2d2fac5c9127886a6fd8088bdceb4cc64
Add footer using Partial

Change-Id: I7ad5eb2ebff17c0a650b748d530ab87e31d9a306
Refactor the custom css file using SASS feature Nesting & Variables

Change-Id: I22adcaffbd29db0fb06074aed929b1180c25b68d
Further refactor customer css file using variables defined by Bootstrap (http://bootstrapdocs.com/v2.0.4/docs/less.html)

Change-Id: I9ea025cc25218d758ff6fe5223bc3238f0a86677
Test case for named route
Note that URL "/" is now by design point to previously "/static_pages/home"
All test case should fail now because named route is not implemented

Change-Id: I21e8ff9ab1d5d7002ad4055e1a2f236ebf3e1204
Create route for '/about' -> StaticPagesController#about, using the built-in 'match' method in route.rb
It also auto create 'named route' for use in controllers & views:
  about_path -> '/about'
  about_url -> 'http://localhost:3000/about'
Still 3 test cases fail because named route for root is not done

Change-Id: I9137ee0e023f04ddd882948b51920b33a8144df4
Add the route for root: '/' -> StaticPagesController#home
But test cases still fail because named route 'root_path' is not auto created

Change-Id: I6a9d928a4ab93681324f3af476a2ed30cd8aa997
Use built-in method 'root' to map '/' -> StaticPagesController#home
Now test all green

Change-Id: Iff2557ae085fd97591cddddb69089681287c6bc7
Now replace all placeholders (links) in views with named routes

Change-Id: I50bd3e1344d148fb10509a238e7ac1adacc5575c
Pretty RSpec using 'before' 'subject' & helper method 'full_title' (though quite duplicated)

Change-Id: I47d6f6a1636907d3e9071db569d208e3d8483a38
Generate a 2nd controller: UserContoller with 'new' method
We call 'rails generate controller Users new --no-test-framework', thus 'new.html.erb', route '/user/new' & assets are also generated

Change-Id: I5b068aa496e0ad695d194d606918f2f21b3f8795
RSpec for the sign up page: Of course the 2 new cases fail

Change-Id: Ie56a725f9cda61904208ac578ab2b1fe92c7edd3
Add named route for '/signup' so that 'signup_path' will now exist
However the test still fail because it cannot initialize UsersController. What's wrong here is that we called 'rails generate controller User new --no-test-framework' instead of '>>Users<<'. I have to undo the rails command using 'rails destroy' & regenerate with the right command

Change-Id: If3faac1d1c4b1fdb1ddf485ff1761131c83457c2
Destroy & regenerate the UsersController (this time with right name 'Users')
Also update the default route '/user/new' to '/users/new'

Change-Id: I7ce2d0f897f0712ca938e54e50c9b2e5384c6b4f
Add 'sign up' to the title & content of signup page so the tests now pass

Change-Id: I70e536977a874b272b7f837cec77d89d593271df
Link the 'Sign up now' button on home page to named route for '/signup'

Change-Id: I296d9065db7a729fb745e40861fa82bce2aacfc5
Merge branch 'filling-in-layout'