1) Gutting the web service; post-login data that needs to get passed to the client will be done in a hash on the query string
2) Adding Path.js, which is a lightweight router for the client.
3) Nuking the templates directory and moving the client-starting code into a static "index.html" file. Routes are defined here with Path.js. 
4) Modifying link to "PUBLIC" project sent in email to use new client-side route. This sorta sucks, but I didn't want to add a route handler to the web server.
5) Client needs to update hash before reloading page after changing user settings.
6) Client needs to return false (or otherwise stop the click event) in "Log Out" button click handler to prevent the default Path.js route from being hit (if redirecting to "#")