feat(content): Add external communications page #79
Conversation
clarified governance to be governance handbook, and corrected the link to point to the new handbook URL (was pointing to /governance)
Update README.md
…into ext-comms-email
|
pre-commit.ci autofix |
There was a problem hiding this comment.
This is a great start jesse.
I left some comments inline.
id like for each platform to have a section on
- goals (you have a nice section for the blog but not for other sections)
- metrics of success
- example content that shows tone and strategy.
The other meta topic is - mailchimp.
|
|
||
| pyOpenSci does not send unsolicited bulk emails, and all emails contain an unsubscribe link. Emails from pyOpenSci are sent to communicate with potential volunteers, share the monthly version of the newsletter, and to keep registered event participants up-to-date on logistics. pyOpenSci will also reach out to event attendees with pre- and/or post-surveys, along with follow-up reminders, as needed. | ||
|
|
||
| ### Mailchimp |
There was a problem hiding this comment.
In our August 14 check-in, we discussed canceling MailChimp. Did that decision change?
There was a problem hiding this comment.
it didn't - this PR went up before then! I'll go through and make adjustments.
|
|
||
| ### HubSpot | ||
|
|
||
| [HubSpot](https://hubspot.com/) is pyOpenSci's customer relationship management (CRM) platform. Although HubSpot has email capabilities, pyOpenSci does not currently use this functionality. |
There was a problem hiding this comment.
I thought we discussed using this platform for email instead of mailchimp as a way to consolidate.
There was a problem hiding this comment.
yep! related to the above, the PR was written and submit before we discussed these changes.
|
|
||
| ## Linktree | ||
|
|
||
| All of our active sites, platforms, and social media accounts are located in a Linktr.ee account, which is shared in the Description of our social media sites where applicable. |
There was a problem hiding this comment.
Please explain what linktree is and why we use it. then you can talk about the how after.
| All of our active sites, platforms, and social media accounts are located in a Linktr.ee account, which is shared in the Description of our social media sites where applicable. | ||
|
|
||
| Accessing and editing Linktr.ee: | ||
| * Login at linktr.ee (credentials are in Bitwarden) |
There was a problem hiding this comment.
Since we mention Bitwarden here, I suggest adding a section on what Bitwarden is and how we use it to the guide in this pr. Then you can link to that section here.
|
|
||
| We publish two newsletters: | ||
| * A weekly newsletter on LinkedIn, published on Thursdays | ||
| * A monthly newsletter published on LinkedIn and sent to all Mailchimp subscribers |
There was a problem hiding this comment.
Flaggin mailchimp. If we made a decision after august 14 that i've forgotten you can remind me!
| * A weekly newsletter on LinkedIn, published on Thursdays | ||
| * A monthly newsletter published on LinkedIn and sent to all Mailchimp subscribers | ||
|
|
||
| The weekly LinkedIn newsletter has three main categories: |
There was a problem hiding this comment.
This is great! Please add an example of how each of these posts is structured .
then please also add what metrics are used to track success of these items. each section should include goals of the platform, target audience, metrics of success.
lwasser
changed the title
Co-authored-by: Leah Wasser <[email protected]>
Co-authored-by: Leah Wasser <[email protected]>
Co-authored-by: Leah Wasser <[email protected]>
Co-authored-by: Leah Wasser <[email protected]>
Co-authored-by: Leah Wasser <[email protected]>
Co-authored-by: Leah Wasser <[email protected]>
Co-authored-by: Leah Wasser <[email protected]>
Co-authored-by: Leah Wasser <[email protected]>
Co-authored-by: Leah Wasser <[email protected]>
Co-authored-by: Leah Wasser <[email protected]>
|
closing this PR in favor of #92. all updates from this review have been incorporated into the new PR. |
Incorporating feedback on the draft from @lwasser, this page includes information on: