{"action":"created","issue":{"url":"https://api.github.com/repos/TheDetroitZoo/pr-mailchimp-integration/issues/34","repository_url":"https://api.github.com/repos/TheDetroitZoo/pr-mailchimp-integration","labels_url":"https://api.github.com/repos/TheDetroitZoo/pr-mailchimp-integration/issues/34/labels{/name}","comments_url":"https://api.github.com/repos/TheDetroitZoo/pr-mailchimp-integration/issues/34/comments","events_url":"https://api.github.com/repos/TheDetroitZoo/pr-mailchimp-integration/issues/34/events","html_url":"https://github.com/TheDetroitZoo/pr-mailchimp-integration/issues/34","id":189179095,"number":34,"title":"Consistent control of Pre-Header - Possible?","user":{"login":"thisisjoewells","id":9747248,"avatar_url":"https://avatars.githubusercontent.com/u/9747248?v=3","gravatar_id":"","url":"https://api.github.com/users/thisisjoewells","html_url":"https://github.com/thisisjoewells","followers_url":"https://api.github.com/users/thisisjoewells/followers","following_url":"https://api.github.com/users/thisisjoewells/following{/other_user}","gists_url":"https://api.github.com/users/thisisjoewells/gists{/gist_id}","starred_url":"https://api.github.com/users/thisisjoewells/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thisisjoewells/subscriptions","organizations_url":"https://api.github.com/users/thisisjoewells/orgs","repos_url":"https://api.github.com/users/thisisjoewells/repos","events_url":"https://api.github.com/users/thisisjoewells/events{/privacy}","received_events_url":"https://api.github.com/users/thisisjoewells/received_events","type":"User","site_admin":false},"labels":[{"id":442718337,"url":"https://api.github.com/repos/TheDetroitZoo/pr-mailchimp-integration/labels/in%20queue","name":"in queue","color":"0e8a16","default":false},{"id":439118985,"url":"https://api.github.com/repos/TheDetroitZoo/pr-mailchimp-integration/labels/question","name":"question","color":"cc317c","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-11-14T17:49:25Z","updated_at":"2016-11-14T21:16:57Z","closed_at":null,"body":"Hi @brashrebel - I'm not sure of the billing status on PR-SOS.  Every time I go to train (so we can \"launch\") Patricia/Jennie, three times now, they notice things and request changes, despite my attempts to avoid this with email previews, meetings, and whatnot.  I'm sure you agree we want them to like this thing we are building them, so we need to make these legit improvements they point out.  Frustrating workflow though.\r\n\r\nThis may be a small change, I need help, I don't think I can do this one.\r\n\r\n@d4mation, basically they shredded the gray pre-header box today.  They complained that it effectively shows the subject line 3 times in an email, and this looks bad, especially on mobile.  Valid point.   They said for Press Releases no one will ever need to view in a browser, which is arguable.\r\n\r\nI wish, of course, pointed this out 4 months and any time in between, when they might have mentioned this.  They have been reviewing previews.\r\n\r\nSo I just removed this whole darker gray pre-header box/area from the no-buttons template.  But.  PROBLEM.  Things get inconsistent on the little preview that every email client uses a bit differently.\r\n\r\nCan we consistently have the preview-lines of emails display the first few words of the press release (not title/subject line, and not 'For Immediate Release...' which are differnt API items,  I think).  We could put an API call into the template for this?\r\n\r\n\r\n## Example - Outlook 2016 Mac Client - Acceptable\r\nShows first text, though not ideal that it's \"For Immediate release....\"\r\n\r\n![outlook-pre-header1](https://cloud.githubusercontent.com/assets/9747248/20275916/43f14fa8-aa68-11e6-963e-ec6edc2c808a.png)\r\n\r\n## Example - iPhone - BAD\r\nShows image link in text \"https://gallery.mailchimp...\"\r\n\r\n![iphone-pre-header1](https://cloud.githubusercontent.com/assets/9747248/20275982/76f58806-aa68-11e6-9e3f-8688574c3cea.png)\r\n\r\n## Example - Gmail - Acceptable\r\nShows first text, though not ideal that it's \"For Immediate release....\"\r\n\r\n![gmail-pre-header1](https://cloud.githubusercontent.com/assets/9747248/20276070/c10089b4-aa68-11e6-8bea-4b1c87e0ea3e.png)\r\n\r\n\r\n## So, can we either?:\r\n\r\n- Specify an API call somehow that pulls the actual Press Release Text, not sure how to 'hide' it in the main template body?\r\n- Or - at least fix it so iPhone doesn't show link text, not sure best way?\r\n"},"comment":{"url":"https://api.github.com/repos/TheDetroitZoo/pr-mailchimp-integration/issues/comments/260465243","html_url":"https://github.com/TheDetroitZoo/pr-mailchimp-integration/issues/34#issuecomment-260465243","issue_url":"https://api.github.com/repos/TheDetroitZoo/pr-mailchimp-integration/issues/34","id":260465243,"user":{"login":"brashrebel","id":4993131,"avatar_url":"https://avatars.githubusercontent.com/u/4993131?v=3","gravatar_id":"","url":"https://api.github.com/users/brashrebel","html_url":"https://github.com/brashrebel","followers_url":"https://api.github.com/users/brashrebel/followers","following_url":"https://api.github.com/users/brashrebel/following{/other_user}","gists_url":"https://api.github.com/users/brashrebel/gists{/gist_id}","starred_url":"https://api.github.com/users/brashrebel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brashrebel/subscriptions","organizations_url":"https://api.github.com/users/brashrebel/orgs","repos_url":"https://api.github.com/users/brashrebel/repos","events_url":"https://api.github.com/users/brashrebel/events{/privacy}","received_events_url":"https://api.github.com/users/brashrebel/received_events","type":"User","site_admin":false},"created_at":"2016-11-14T21:16:57Z","updated_at":"2016-11-14T21:16:57Z","body":"Mail Chimp emails already default to having a teaser text section at the top specifically to address this problem. When you're creating these campaigns in Mail Chimp you just put something in that text box. So we just need something like that in the template I guess.\r\n\r\nYou could even dynamically take the first sentence from the content, put it up top and then...hide it? Not sure if the email clients would still show it or not. But it would prevent the necessity of creating another field to fill when publishing Press Releases."}}
{"actor":{"display_login":"brashrebel"}}