search

measured / brandguide

BMS engine for brandguide
admin.brandguide.io
0 stars 0 forks source link

Email links #6

Open haustraliaer opened 10 years ago

haustraliaer commented 10 years ago

Expanding this into it's own issue from matt's comment.

Should be a key feature to V1 of this project. Easy access on mobile to forward a file (or multiple files) via email to some marketing manager who needs it ASAP.

Considerations:

  1. Should a project have emails pre-associated so you don't need to type them all the time?
  2. Will it open an email app (I think this would be cumbersome) .. and if not, then you should be able to write a short message to send as well.
  3. Link should be a long hash (private-ish) link that auto authenticates for a set period of time?
jenbennings commented 10 years ago

Should a project have emails pre-associated so you don't need to type them all the time?

Probably not. I think it's more likely that you would need to send it to someone who does not have access to the brandguide. Contacts may be a nice feature to think about in the future, but for now let's keep it simple.

Will it open an email app (I think this would be cumbersome) .. and if not, then you should be able to write a short message to send as well.

Avoid opening up the email app at all costs, if possible. I would imagine we use a pre-generated template. Something along the lines of:

Hi recipient,

sender has sent you the following clientname asset(s):

filename.eps filename.eps filename.eps

Click here to download them: link goes here

Regards, Monsieur Brandguide

haustraliaer commented 10 years ago

(good excuse for me to play with sketch)

Pretty much riffing off your earlier work...

email

Could have a pre-defined template if that's easier... but always nice to add a short personal message.

jenbennings commented 10 years ago

Sure, you'd probably want to work the message in the template—although my experience with using services like WeTransfer is that often you're repeating stuff that is already mentioned and/or implied.

On the idea of changing content within the asset module based on state—it suggests that we're going to have to devise a robust way of handling a variety of content types and sizes. My first idea was to treat it like a card, however that doesn't take varying heights into consideration: