-
Notifications
You must be signed in to change notification settings - Fork 65
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
Port "This Week in Wagtail" to wagtail-newsletter #481
Comments
I think a good plan is to:
|
Hi @mgax. This sounds like a solid plan to me. Honestly, the last few issues use varied content in them. Here are some links: https://mailchi.mp/wagtail/twiw-11032065?e=[UNIQID] I can give you access to MailChimp, if needed. One ask for the template. MailChimp doesn't offer the ability to add BlueSky or Mastodon links without custom code in the social media bar and I never was able to Outlook-proof that code. It kept breaking in Litmus tests and so I abandoned it and reverted to using the default. We don't use Twitter anymore, so we'll want to include Mastodon, Bluesky, YouTube, and LinkedIn. We still have a Litmus account at Torchbox it looks like. The login is in Bitwarden. Whatever template you set up, we should make sure to run tests with Litmus too because the last time we had a custom template, Outlook kept breaking it. |
@mgax It just occurred to me that you already created a template for some of the demos you presented. Is there a reason that template code could not be used for doing the actual update? At the very least, I think it would be helpful for someone taking this on to have access to your demo. It might speed things up. |
@vossisboss good point! The template is actually part of the demo project that is part of the wagtail-newsletter repo: https://github.com/wagtail/wagtail-newsletter/blob/main/demo/templates/demo/article_page_newsletter.html. |
The newsletter used to be content-managed in wagtail.org until July 2023 (the latest page is https://wagtail.org/this-week-in-wagtail/issue-136/). Content display issues on Outlook prompted a move to a content template in Mailchimp.
Since https://github.com/wagtail/wagtail-newsletter is released, and it comes with MJML support, we can reimplement the current Mailchimp template as MJML, and move back to Wagtail-managed newsletters.
The text was updated successfully, but these errors were encountered: