Skip to content
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

feat(content): Add external communications page #79

Open
wants to merge 18 commits into
base: main
Choose a base branch
from

Conversation

kierisi
Copy link
Collaborator

@kierisi kierisi commented Aug 13, 2024

Incorporating feedback on the draft from @lwasser, this page includes information on:

  • External communications platforms
  • The pyOS blog, including how to submit a guest post
  • pyOS newsletters
  • YouTube
  • Discourse
  • Zenodo

@kierisi
Copy link
Collaborator Author

kierisi commented Aug 13, 2024

pre-commit.ci autofix

Copy link
Member

@lwasser lwasser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In our August 14 check-in, we discussed canceling MailChimp. Did that decision change?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought we discussed using this platform for email instead of mailchimp as a way to consolidate.


## 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

organization/external-communications.md Outdated Show resolved Hide resolved
organization/external-communications.md Outdated Show resolved Hide resolved
Comment on lines +62 to +82
**A note on guest blog posts**

Anyone who has had their package accepted into the pyOpenSci ecosystem is encouraged to submit a blog post (or series of blog posts) about their review experience and/or their package. When submitting your blog post, please include the following YAML elements:

```
layout: single
title: "The title of your blog post"
excerpt: "One to five sentences summarizing your post. This text will appear on our [blog landing page](https://pyopensci.org/blog)"
author: "Your name"
permalink: /blog/url-for-your-post.html
header:
overlay_image: images/headers/your-blog-post-header-image.png
overlay_filter: rgba(20, 13, 36, 0.8)
categories:
- blog-post
- community
classes: wide
toc: true
comments: true
---
```
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**A note on guest blog posts**
Anyone who has had their package accepted into the pyOpenSci ecosystem is encouraged to submit a blog post (or series of blog posts) about their review experience and/or their package. When submitting your blog post, please include the following YAML elements:
```
layout: single
title: "The title of your blog post"
excerpt: "One to five sentences summarizing your post. This text will appear on our [blog landing page](https://pyopensci.org/blog)"
author: "Your name"
permalink: /blog/url-for-your-post.html
header:
overlay_image: images/headers/your-blog-post-header-image.png
overlay_filter: rgba(20, 13, 36, 0.8)
categories:
- blog-post
- community
classes: wide
toc: true
comments: true
---
```
:::{admonition} Yaml elements required for blog posts
:class: tip
All package authors, maintainers (and users) of a pyOpenSci-accepted package are welcome and encourage to submit a blog post (or series of blog posts) about their review experience and/or the use of the package. When submitting your blog post, please include the following YAML elements:

layout: single
title: "The title of your blog post"
excerpt: "One to five sentences summarizing your post. This text will appear on our blog landing page"
author: "Your name"
permalink: /blog/url-for-your-post.html
header:
overlay_image: images/headers/your-blog-post-header-image.png
overlay_filter: rgba(20, 13, 36, 0.8)
categories:

  • blog-post
  • community
    classes: wide
    toc: true
    comments: true

:::

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i just made this correction here - please check the build to ensure it's correct!

Comment on lines +95 to +96
In addition to pyOpenSci promotions, we monitor social media for any personal posts authors have created to promote their post, boost accordingly.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In addition to pyOpenSci promotions, we monitor social media for any personal posts authors have created to promote their post, boost accordingly.
In addition to pyOpenSci social outreach, we monitor social media for any personal posts that authors have created. To promote these posts, we will repost.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i'm not sure the intent of this sentence but I tried to rewrite. Please rewrite as you see fit.


We publish two newsletters:
* A weekly newsletter on LinkedIn, published on Thursdays
* A monthly newsletter published on LinkedIn and sent to all Mailchimp subscribers
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 lwasser changed the title [ENTRY] External communications page feat(content): Add external communications page Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants