Homepage, Get Started and Shop cut-up
Merge branch 'tk/website-prototype' of github.com:azurestandard/website into working
app/scripts/services.js: Add config factory

Collect the hardcoded URLs in one place so it's easy to change them
for testing.
app/scripts/services.js: Use our four-space indentation convention
app/scripts/controllers.js: Hit /person to get a session cookie

Instead of keeping basic-auth credentials around, take advantage of
Django's session cookie:

  $ wget -S --header 'Authorization: Basic ...' https://api.azurestandard.com/person
  ...
  Connecting to api.azurestandard.com|72.14.190.253|:443... connected.
  HTTP request sent, awaiting response...
    HTTP/1.1 200 OK
    ...
    Vary: Cookie
    Set-Cookie: sessionid=...; expires=Tue, 16-Dec-2014 19:13:54 GMT; httponly; Max-Age=1209600; Path=/
    ...

We'll use the cookie for future authentication, and it will persist
between page reloads and browser restarts, as long as you hit another
api.a.c endpoint before it expires.  That's safer than caching the
quasi-permanent username/password credentials locally.

There are some unresolved issues with swagger-js-codegen, so I'm using
$http calls directly here [1].  You could have the /person endpoint
behind a custom action of a $resource instance [2], but the auth
handling is different than other calls (e.g. we're using basic auth to
get a cookie, while other calls will just use that cookie), so I
thought it made more sense to use the lower level interface.

I don't set withCredentials for the initial "are you logged in"
request for /person.  Ideally, there would be a way to pass any
existing cookie along, but *not* have Firefox pop up the basic-auth
dialog.  There are some workarounds [3], but none of them are
particularly elegant, and I'm not excited about making major changes
to API to work around a client-side quirk.

I'm using window.btoa() to perform the base-64 encoding.  It's
supported in all major browsers since time immemorial, with the
exception of Internet Explorer, which only added support in v10 [4].
We'll likely need an alternative approach for folks with older version
of IE, but I'll deal with that after I have basic auth working.

[1]: https://docs.angularjs.org/api/ng/service/$http
[2]: https://docs.angularjs.org/api/ngResource/service/$resource
[3]: http://stackoverflow.com/questions/9859627/
[4]: https://developer.mozilla.org/en-US/docs/Web/API/WindowBase64.btoa