Initial cut of routes and controllers

[brehaut]

The UI will need to handle routing and history changes to provide a good UI experience for browser based users. This should be handled by some kind of routing and controller dispatch scheme. This task is to create the basic stubs we know we will need to get off the ground:

• [ ] Homepage / Search page
• [ ] Search page with results: Note this may look like a variant of the homepage
• [ ] Details view page
• [ ] User pages (coordinate with backend team)
  • [ ] Log in.
  • [ ] Sign up.
  • [ ] Account preferences.
  • [ ] Sign out
  • [ ] Entry add and edit

Depends on #3

[templetonpr]

RE: Routing, we should be pretty much covered by react-router. Basically, once we make the pages, they're pretty simple to hook up.There's some fancy stuff we can do with react-router if/when we need to, but for now the basic routing functionality should be fine.

RE: Controllers, we may want to think about adding redux ( or some other flux implementation? ). We don't need it right now, but once we implement the login functionality, the app might get complex enough to warrant adding it.