Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out mailchimp preview text #34

Open
dellsystem opened this issue May 1, 2020 · 11 comments
Open

Figure out mailchimp preview text #34

dellsystem opened this issue May 1, 2020 · 11 comments
Labels
enhancement Improvement or fix

Comments

@dellsystem
Copy link
Collaborator

No description provided.

@dellsystem dellsystem added the enhancement Improvement or fix label May 1, 2020
dellsystem added a commit that referenced this issue May 2, 2020
This is a step toward issue #34. Currently, only issue 1 of volume 2
has the preview text, but eventually all past issues should have it.
@jessesquires jessesquires self-assigned this May 3, 2020
@jessesquires
Copy link
Member

I just realized that 3cfa0dd didn't update this in every spot. I'll fix

@jessesquires
Copy link
Member

nevermind lol. i just saw 986b40b

@anaulin
Copy link
Member

anaulin commented May 3, 2020

In #37, @jessesquires said:

Did we vote on not just using the excerpt text for this?
EDIT: I'm fine either way, but I think the excerpt method is a bit simpler. Less front-matter to worry about.

I don't know if there was a deeper discussion or vote, but I got the impression from @stationaery and @dellsystem 's comments that there was a desire to have the MailChimp "email preview" to be a short pithy sentence, different from the excerpt (which is typically much longer), and also to use that in social card previews (which was done already).

@anaulin
Copy link
Member

anaulin commented May 3, 2020

Right now the preview text is not set to anything in MailChimp:
Screen Shot 2020-05-02 at 7 06 03 PM

@stationaery
Copy link
Collaborator

stationaery commented May 3, 2020 via email

@jessesquires
Copy link
Member

@anaulin Ahh I see. I think I can fix this.

@stationaery No problem! Let's stick with the preview text.

@jessesquires
Copy link
Member

Figured this out. According to these docs:

Use this merge tag to generate preview text in a custom-coded campaign. Insert *|MC_PREVIEW_TEXT|* just after the opening < body > tag in your HTML. To ensure the preview text isn’t visible in the body of your campaign, wrap the merge tag in a hidden < span > element.

Locate or add < style type= "text / css" > < /style> to your HTML, and add this code to the "style type" value:

.mcnPreviewText{display: none !important;}

After the opening < body > tag, add:

<!--*|IF:MC_PREVIEW_TEXT|*--> 
<!--[if !gte mso 9]><!----><span class="mcnPreviewText" style="display:none; font-size:0px; line-height:0px; max-height:0px; max-width:0px; opacity:0; overflow:hidden; visibility:hidden; mso-hide:all;">*|MC_PREVIEW_TEXT|*</span><!--<![endif]--> 
<!--*|END:IF|*-->

Seems pretty gross. But 🤷

@jessesquires
Copy link
Member

My original thought was to use the RSS summary for the preview. We might still be able to do that if there is a merge tag for that, but I couldn't find one in the docs. (But there are different options when editing the template.)

Currently we have:

<summary type="html">{{ post.excerpt | escape }}</summary>

in feed.xml

@anaulin
Copy link
Member

anaulin commented May 3, 2020

Nice. (And, I mean, HTML email is pretty gross, as is MailChimp HTML, so, I feel like we're committed to the grossness here...)

@jessesquires
Copy link
Member

Ah, here's what I had seen before: https://mailchimp.com/help/rss-merge-tags/

However, I'm not sure if we can use *|RSSITEM:CONTENT|* for the email preview?

Screen Shot 2020-05-02 at 7 46 00 PM

@anaulin
Copy link
Member

anaulin commented May 3, 2020

I couldn't find any good documentation about RSS merge tags in the "preview" field. We might need to just test it.

@jessesquires jessesquires removed their assignment May 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement or fix
Projects
None yet
Development

No branches or pull requests

4 participants