A better way of handling login/authentication

[jenbennings]

Problem

We currently rely on simple http auth for users to access the page, which results in this undesirable experience:

Solution

We need to signify to users that they are handing over sensitive information to a trustworthy service. We do that by providing context.

10 second mock-up™:

This raises the question: are both username and password entirely necessary? Thinking ahead, there may need to be a distinction between those who simply need to access content, and those who need to edit it. Should there be a separate entry point for both? Not sure.

[haustraliaer]

User & Pw

Cons:

• Have to remember both
• Potentially more development work (see below).

Pros:

• Clients on the books are kept private
• Single login point can yield multiple brandguides
• Potentially less development work, if rails has this in it's default helpers

---

For me it kind of comes down to how we think accounts should work:

a) One account with multiple brands. b) Every brand has it's own account.

How would we prefer to manage our multiple clients? How would a studio (aka: potential customer of this as a product)? But also, in the initial stages development time for either option is a factor.