-
Notifications
You must be signed in to change notification settings - Fork 4
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
Newsletter capabilities #14
Comments
Is this an email newsletter? If so, HubSpot will likely be the best tool for those. |
I think @cjyabraham is correct in that we might need some tools for the sending of the newsletter, but I do see how newsletters could be written in markdown and sent over email when released but ALSO available on the website afterwards. But we would need to figure out a good approach here. Will appreciate recommendations. |
A common pattern within other projects is to use HubSpot to manage forms, lists, newsletters etc. You can then link to the sent newsletters. See this Kubeweekly newsletter page for example. It lists all sent newsletters with each linking directly to the HubSpot email. It has a HubSpot form to allow people to sign up. HubSpot has a nice email editor which provides a lot of benefits over writing the email in html/markdown yourself in addition to providing analytics. |
We didn’t talk about this today, but here is my concern.
I would like different members of the community to be able to contribute to a newsletter. The problem I have found with LF related applications is that you actually have to be an LF employee, such as being listed as a co-host for a zoom meeting. That is not scalable to a broader community. I also inherently don’t like
complicated interfaces, such as I see with Wordpress.
I don’t know about hubspot, but wonder if putting these types of things in a version controlled markdown file would make more sense for the technical community to be able to update and maintain, and hence publish under our website. I’m open to conversation on this and what others think, but just sharing my thoughts.
Rob
From: Chris Abraham ***@***.***>
Date: Thursday, January 26, 2023 at 22:42
To: chipsalliance/chips-alliance-website ***@***.***>
Cc: robmains ***@***.***>, Author ***@***.***>
Subject: Re: [chipsalliance/chips-alliance-website] Newsletter capabilities (Issue #14)
A common pattern within other projects is to use HubSpot to manage forms, lists, newsletters etc. You can then link to the sent newsletters.
See this Kubeweekly newsletter page<https://www.cncf.io/kubeweekly/> for example. It lists all sent newsletters with each linking directly to the HubSpot email. It has a HubSpot form to allow people to sign up.
HubSpot has a nice email editor which provides a lot of benefits over writing the email in html/markdown yourself in addition to providing analytics.
—
Reply to this email directly, view it on GitHub<#14 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASMW7DXPOYPHINIJTF4DFNDWUNU5FANCNFSM6AAAAAAUFWNUDI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I want to create an entry for newsletters, perhaps quarterly initally. Unsure how this will be structured in terms of writeup, but something we owe to the community
The text was updated successfully, but these errors were encountered: