incorporated feedback from PR review

organization/external-communication.md

@@ -139,13 +139,17 @@ These posts are all structured as blog posts, using appropriate heading and subh
 
 When a newsletter post is a re-post from the pyOpenSci blog, it's important to include text and a link back to the original blog post, indicating where the post was originally published. This prevents link cannibalisation, where different links with the same content compete for keyword rankings. We want all keyword rankings to be directed back to the pyOpenSci website wherever possible.
 
+There are instances in which we publish content from another individual on our website, for example, Eric Ma's upcoming blog post for the [pyOpenSci Open Science Fall Festival 2024](https://www.pyopensci.org/events/pyopensci-2024-fall-festival.html). In these cases we'd want to include a canonical meta element in the HTML for the version being posted on the pyOpenSci blog. This can be accomplished by including the `<link rel="canonical" href="www.original-post-web-url.com">` tag in the header of the post.  
+
 ### Newsletter success metrics
 
 Because pyOpenSci is still in the early days of its newsletter, our success metrics are focused primarily on growth and engagement rate. We are currently aiming for:
 
 * 1.0% (or higher) monthly increase in newsletter subscribers
 * 3.0% (or higher) average monthly engagement rates
 
+This data is obtained through the LinkedIn Analytics dashboard, which is accessed from the pyOpenSci LinkedIn account. Within the Newsletter tab, you can filter the dates and also view engagement and follower metrics.  
+
 ## YouTube
 
 The [pyOpenSci YouTube channel](https://youtube.com/@pyopensci) is still under development, and currently only has one published video. While we are still in the process of developing a YouTube strategy, the best practices for YouTube videos include the following:
@@ -165,4 +169,12 @@ pyOpenSci is currently in the process of sunsetting Discourse as it has not prov
 
 ## Zenodo
 
-Zenodo is a general-purpose research repository where any research output can be shared by its users, where pyOpenSci maintains a [community group](https://zenodo.org/communities/pyopensci?q=&l=list&p=1&s=10&sort=newest). When pyOpenSci staff give a presentation, they will update the community group with their talk materials. In addition, when community members give presentations, they have the option of adding them to the pyOpenSci Zenodo community group.
+Zenodo is a general-purpose research repository where any research output can be shared by its users, where pyOpenSci maintains a [community group](https://zenodo.org/communities/pyopensci?q=&l=list&p=1&s=10&sort=newest). When pyOpenSci staff give a presentation, they will update the community group with their talk materials. In addition, when community members give presentations, they have the option of adding them to the pyOpenSci Zenodo community group.  
+
+pyOpenSci uses Zenodo as a way to provide citable entities for its GitHub org repos. pyOpenSci uses adds the Zenodo citation badge to the README of each repo, then adds the badge to the home page of content that is being tracked in Zenodo.  
+
+When there are major updates to content such as the packaging guide, we create a new release, and Zenodo provides and updated DOI associated with those commits.  
+
+pyOpenSci also has a Zenodo communiy where people can add their presentations, blog posts, or any content related to pyOpenSci to. This allows the community member (or pyOpenSci staff) to gain a citable DOI for the element deposited in the community, while the original submitter still owns the addition.
+
+The pyOpenSci Zenodo community is moderated by pyOpenSci staff admins, so while anyone can suggest an addition, pyOpenSci staff admins moderate what is ultimately added.