-
-
Notifications
You must be signed in to change notification settings - Fork 552
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Create newsletter #179
Comments
Hi @shahednasser, I came to your repo from GitHub search page. I believe this can be achieved using @mailchimp. I am not very much sure about this but I have heard a few times that developers can use Mailchimp's embedded forms to offer a '#' feature on their GitHub pages and I am happy to try this if you see any benefit in this. However, I'd also say that using Mailchimp will only create the form to collect subscriptions, it'll still require some external mechanism for you to be able to send them weekly updates/resources that are added here on GitHub. |
Also, do you need any help/contribution in adding new resources? Thanks, |
perhaps we could take advantage of the webhooks |
Hi @moingshaikh thank you for your input. I don't think the problem is with the # form as I know of a lot of services that offer that. I'm just looking for a way to automate the newsletter based on the resources being added weekly.
Sure! Check the contributing guidelines for qualified resources and how to contribute. |
That's a good idea @diangogav . I'll have to look more through it and see the best way to do this. If you have additional ideas on how we can benefit from it or you would like to work on this issue let me know. |
@shahednasser for automating the newletter (uff manual is boring process) mailchip is the best and popular way and the easy way to make it happen kindly check this blog (since the details are not enough from your side i can't able to make it like daily update,weekly update ...) and if possible share us some more about the issue |
Hello @srinivasthedeveloper the problem isn't with sending the email in particular, the problem is extracting the newly added resources weekly and making them the content of the newsletter. Since the resources are just added in the README it's harder to track the newer ones |
maybe you could make a bot which collects some resources after you merge some pull requests and then send them to the the subscribers? just an idea |
Yes @murtuzaalisurti that's the plan but I think we need to find an email service that we can post these resources to and this email service needs to send the newsletter weekly when there are new resources. Let me know if you have any ideas regarding that. |
Another idea I'm having is creating an RSS feed that is updated every time a PR is merged, which is probably the best direction to go in. That way an email service can get updates from the RSS feed and send them to subscribers |
Yes, I think that's a better option. |
have did any thing regarding this newsletter etc ??? just curious to know about it |
Hello @kshitijmishra27 no unfortunately. I haven't had the time to work on it. If anyone would like to work on it let me know! |
I am interested in contributing. Is this still open to work on? |
Yes it is! @BhumikaJena |
Please assign me |
Hi Iam intrested in cotributing to it , can you please assign me..? |
I think creating a newsletter where people can # and receive weekly any new resources added would be helpful. However, I'm not sure the best way to do this since the resources are just added in the README.
Opening this for ideas if anyone has any.
The text was updated successfully, but these errors were encountered: