Co-branding/whitelabel scheme for 3rd parties running VRMS #300

Dependency

• This issue needs to be updated when the time comes. Right now VRMS is an internal tool and it will take time until we are able to run it for 3rd parties. Not priority right now.

Overview

Other organizations will run VRMS and we need a scheme that lets them brand the app appropriately while still identifying the product as VRMS and giving HfLA credit

Acceptance criteria

• POV on which kinds of screens and where/how to include VRMS branding
• POV on which kinds of screens and where/how to include HfLA branding
• POV on which kinds of screens and where/how to include partner-org branding
• POV on how to handle light and dark BG partner logos
• POV on how to handle various color schemes of partner-org branding
• mockups showing examples of branding (placeholder VRMS logo/icon OK until logo redesign completed)

Background

• I think HfLA branding as in "Built by Hack for LA" is adequate in the footer area on select main pages. -Adam
• VRMS logo presence is striking a balance between taking prominent credit for this amazing piece of software but not hitting users of the head with it too often -Adam
• For where to put partner logo, the user story is primarily around letting them reliably/consistently know which partner org they're logged into. I think a decent test might be to imagine a user who belongs to two orgs (e.g., HackOakland and HackPDX) and where would they want to be able to confirm they were logged into the right organization...similar to how sometimes you're logged into the wrong google account and you want to visually double check whether it's personal or your work org, which you can do by looking for your company's logo somewhere. -Adam
• I think "Powered by VRMS" text below the client logo is one good option to consider for any places we should co-brand, in addition to the design ideas below -Adam
• can use placeholder for VRMS Logo #301 (final logo)
• design ideas explaining concept
• brand document