Pre-game workflow

[slifty]

With the main game functionality implemented we need to think about user flow BEFORE the game. Feedback is needed.

1. User visits torwolf.com
   See a static landing page (separate from the socketed experience) which contains

• Explanation of Torwolf
• Link to rules
• Link to technologies
• "Play" button

user clicks play button

(sockets begin here)

2. "Step 1: Pick a username" <-- directory.js

3. "Step 2: Join or Create a game" <-- lobby.js

4. "Wait for others to join the game..." <-- storyteller.js

5. The game begins! <-- storyteller.js

New modules that would be created for this to happen:
A) "navigation" -- in charge of displaying messages like "Step 1: Pick a Username" and directing the flow described in here

B) "directory" -- in charge of storing all players and allowing the user to pick a username, etc. Currently communication does some of this, but those things will be moved here.

[slifty]

I think we may avoid having this be handled using sockets, and instead have the basic join happen over HTTP API.

@telrikk correct me if I'm wrong here.