add svelte newsletter signup sidebar #6163
Conversation
|
If it's an unofficial newsletter I don't think we want to be linking to it from the official site. (And I don't think we want to have an official newsletter.) |
|
@Conduitry updated this PR to point to the issue/proposal. Definitely happy to have a conversation around this since there seems to be a desire from the community to leverage a newsletter for engagement, announcements and as an alternative to RSS. |
|
Has a newsletter been discussed internally and is the decision been "no"? I've offered before to help set a proper emailing solution up if the maintainers don't have time and energy to do this. We do however need some sort of help with the DNS and, I guess, some funds to pay for the email service if the amount of people subscribing/amount of emails gets too large. I don't know who to ping about this but could we have some sort of Discord meeting about this, maybe? Let's get the ball rolling! An official newsletter would do good for the community! |
|
@kevmodrome what would that look like? I'm not really sure how we can have blog updates automatically emailed and I think we're all a bit hesitant to take on more infrastructure that needs to be maintained |
|
@benmccann One alternative I was thinking about was setting up a https://listmonk.app instance and use that. However, recently I found buttondown.email. Since it uses markdown to write the email it would be as simple as just copy over the raw file and hit send. It's a bit expensive at $5 per 1000 emails sent, however I've reached out to the guy to see if it's possible to push the cost down a bit, this being Open Source. I'll comment again when I get a response. |
|
Just stumbled upon this. @kevmodrome, listmonk now supports Markdown: knadh/listmonk@1e59d53 |
|
Thanks so much for the offer to help with this and all the work already done on the email list and blog posts. I think the general consensus is that it's best to keep the status quo. While I agree the discoverability may be slightly lacking right now, there's a bit of an aversion to being responsible for a newsletter. Even if it doesn't require much forseeable work from the maintainers, it's still another thing to be ultimately responsible for in the case that Daniel stepped away or anything else unforseen happened and everyone's plates are already pretty full Thanks again for all the efforts! |
|
Works for me! Thanks for reviewing :) Should we close out the related issue as well? #5578 |
Context
#5578 discusses how we should go about sending out a monthly newsletter with Svelte news. There was a strong leaning toward leveraging some existing newsletter tooling run by the community so it doesn't become a maintenance burden for the core contributors/maintainers.
The goal of this PR is to introduce a signup form onto the main blog site so that folks who come to the blog can be notified.Substack's built-in signup embed lets us do this easily. We are getting content into substack by copying and pasting the monthly blog post into the substack WYSIWYG editor. We could possibly use this same approach to notify subscribers of other blog posts.
There are currently ~300 subscribers on the substack newsletter and we've been cross-posting the content from the svelte.dev blog for the past few months.
Todo
Screenshots
If the person is already logged into substack:
If the person is not logged in to substack (signup does not require a substack account):
On mobile, the signup appears at the bottom of the blogs posts:
Questions