fix: update onboarding

organization/employee-onboarding.md

@@ -21,33 +21,45 @@ Before pyOpenSci onboarding begins, the new hire is guided through the onboardin
 
 Once Community Initiatives onboarding is complete, all core pyOpenSci staff receive the following:
 
-**Google Workspace account**
-- A pyOpenSci email (`[email protected]`) will be created.
+### 1. Create a Google Workspace account
 
-**Google Drive access**
-- Added to `pyos-shared` and other relevant shared drives.
+A pyOpenSci email (`[email protected]`) will be created for staff / salaried employees.
+
+### 2. Provide Google Drive access
+
+Add the employee to the `pyos-shared` Google Drive and any other relevant shared drives that support their work for pyOpenSci.
+
+### 3. Provide pyOpenSci GitHub organization access
+
+The employee will be added to the pyOpenSci GitHub organization.
 
-**pyOpenSci GitHub organization access**
-- Added to the pyOpenSci GitHub organization.
 As part of the onboarding process, New staff are given the freedom to choose their preferred GitHub account. Depending on their role and personal preference, they may opt to use their existing personal account or create a new one specifically for their work with pyOpenSci.
 
 [Learn more about how we use GitHub.](github)
 
-**Access to Asana**
+### 4. Add employee to the pyOpenSci Operations Asana Team
+
+[We use Asana to track and manage tasks.](asana) All pyOpenSci employees will be added to the pyOpenSci Operations Asana team.
 
-- [We use Asana to track and manage tasks.](asana). All pyOpenSci employees will be added to the pyOpenSci Operations Asana team.
+### 5. Add employee to the pyOpenSci Slack
 
-**Slack**
-- Invited to Slack workspace for day-to-day communication.
+Invite to the pyOpenSci Slack workspace for day-to-day communication.
 - [Learn more about how we use Slack.](https://www.pyopensci.org/handbook/community/slack.html)
 
-**Discord**
-- Invited to our Discord workspace, which we use for events.
+### 6. Invite employee to the pyOpenSci Discord
+
+* Invited to our [Discord workspace](https://discord.gg/FDKVrSB4), which we use for events.
+
+### 7. Provide access to social media and content platforms (as needed)
+
+Access to LinkedIn, [Mastodon](https://fosstodon.org/@pyOpenSci), BlueSky, YouTube, Buffer as needed, depending on the position. **media at pyopensci.org** email is used for these accounts.
 
-**Access to social media and content platforms (as needed)**
-- Access to LinkedIn, Mastodon, BlueSky, YouTube, Buffer as needed, depending on the position.
 - [Learn more about how we use Buffer for social posting.](buffer)
 
+### 7. Provide access to BitWarden for media and admin account credentials
+
+We use [BitWarden](bitwarden) for administration accounts and social. Provide the employee
+with access to BitWarden to access these accounts.
 
 ## Onboarding for flexible project-based positions
 
@@ -57,33 +69,44 @@ Typically, project-based roles involve a weekly time commitment of 5-20 hours, w
 
 Unless they are hired as an outside contractor, project-based employees complete onboarding with Community Initiatives and report time using Community Initiatives' Paylocity platform.
 
-**Google Workspace account**
-- We will create a Google Workspace account if there is a clear business need for the role (for example, external communications or another specific role).
+### 1. Create Google Workspace account (as needed)
+
+We will create a Google Workspace account if there is a clear business need for the role (for example, external communications or another specific role).
 - [Learn more about how we use GitHub.](google-workspace)
 
-**Google Drive access**
+### 2. Provide access to Google Drive
+
 - Granted access to relevant shared folders as needed.
 
-**GitHub**
-- Added to the pyOpenSci organization or granted repo-specific access based on project needs.
+### 3. Add to the pyOpenSci GitHub Organization
+
+Added to the pyOpenSci organization or granted repo-specific access based on project needs.
 - [Learn more about how we use GitHub.](github)
 
-**Slack**
-- All pyOpenSci contributors and staff are invited to join the Slack community.
+### 4. Slack
+
+All pyOpenSci contributors and staff are invited to join the Slack community.
 - [Learn more about how we use Slack.](slack)
 
-**Discord**
-- Invited to our Discord workspace, which we use for events.
+### 5. Discord
 
-**Access to social media and content platforms (as needed)**
-- Access to LinkedIn, Mastodon, BlueSky, YouTube, Buffer as needed, depending on the position.
+Invited to our Discord workspace, which we use for events.
+
+### 6. Access to social media and content platforms (as needed)
+
+Access to LinkedIn, Mastodon, BlueSky, YouTube, Buffer as required, depending on the position. **media at pyopensci.org** Email is used for these accounts.
 - [Learn more about how we use Buffer for social posting.](buffer)
 
+### 7. Provide access to BitWarden for media and admin account credentials as needed
+
+We use [BitWarden](bitwarden) for administration accounts and social. Provide the employee
+with access to BitWarden to access these accounts.
+
 ## Email groups
 
 pyOpenSci staff may be added to one or more email groups to support their role as needed:
 
-- [[email protected]](mailto:[email protected]): used for administration tasks such as hiring calls.
+- [[email protected]](mailto:[email protected]): used for administration tasks such as meetighns calls.
 - [[email protected]](mailto:[email protected]): used for general social media work.
 
 ## Engaging with the community
@@ -95,7 +118,7 @@ Once a new staff member is onboarded, they are introduced to the pyOpenSci commu
 - **Introductory blog post**: New hires write a brief blog post introducing themselves to the community. Topics may include work background, hobbies, why they joined pyOpenSci, and their role.
 - **Social media**: Post the hire announcement on pyOpenSci social channels.
 
-## New Hire evaluation and support
+## New hire evaluation and support
 
 At pyOpenSci, we aim to ensure a supportive transition for new team members. To foster this, we conduct formal evaluations at both three and six months during the initial employment period. These check-ins provide an opportunity to discuss progress, address challenges, and identify any additional support that may be needed. They also serve as a chance to assess whether the role and expectations remain a good fit for both the team member and pyOpenSci.
 

organization/how-we-work.md

@@ -9,13 +9,15 @@ Wherever possible, we use open, collaborative tools such as GitHub and Google Dr
 For information on how we onboard new staff, see the [New Hire Onboarding](onboarding) page.
 :::
 
-
-For daily operations, primarily use:
+For daily operations, we use:
 
 * [GitHub](github)
 * [Google Workspace](google-workspace)
 * [Slack](slack)
 * [Asana](asana)
+* [BitWarden](bitwarden)
+
+We use Canva for shared graphic development.
 
 (github)=
 ## GitHub
@@ -71,7 +73,6 @@ Storing documents in the shared drive also supports continuity, as documents are
 
 Employees can save personal documents such as 1-on-1 agendas, personal notes, and other information that does not need to be shared at the organizational level in their personal pyOpenSci Drive and share them with other team members as needed.
 
-
 (slack)=
 ### Slack
 
@@ -90,7 +91,7 @@ If a conversation in Slack highlights the need for updated or new documentation,
 (asana)=
 ### Asana
 
-[Asana](https://asana.com/) is an internal tool we use as pyOpenSci staff for general task management. Within Asana, we assign tasks to one another that need to be accomplished, along with their respective deadlines. In staff check-ins, we review tasks, update deadlines as needed, and discuss future efforts. Asana can also be used to build road maps for projects.
+[Asana](https://asana.com/) is an internal tool we use as pyOpenSci staff for general task management. Within Asana, we assign tasks to one another that need to be accomplished, along with their respective deadlines. During staff check-ins, we review tasks, update deadlines as necessary, and discuss upcoming efforts. Asana can also be used to build road maps for projects.
 
 Asana is also connected to GitHub, which allows us to track open issues and pull requests as needed.
 
@@ -113,4 +114,4 @@ Asana is connected to GitHub, allowing us to track relevant issues and pull requ
 
 * **For individuals:** Team members are encouraged to use Bitwarden to securely store passwords related to their pyOpenSci work, including access to Google Workspace services, Slack, and Canva.
 
-* **For the organization:** Bitwarden manages shared login access to accounts where only one organizational account is needed, such as Eventbrite and Buffer. Authorized team members can access these shared credentials as necessary.
+* **For the organization:** Bitwarden is used to manage pyOpenSci accounts where only one organizational account is needed, such as Eventbrite, Buffer, and social media accounts. pyOpenSci has an organization account in BitWarden that staff can be added to for access to these shared accounts.

organization/index.md

@@ -8,7 +8,7 @@ This section outlines the essential processes and structures that guide the oper
 
 External Communication <external-communication>
 Branding <branding>
-Social Media <social-media-blog>
+Communications <social-media-blog>
 Canva <canva>
 :::
 

organization/social-media-blog.md

@@ -1,21 +1,21 @@
 (social-platforms)=
-# External Communication & Social Media
+# Communication & Social Media
 
 pyOpenSci uses several popular social channels and platforms to connect with the
 community including:
 
-* social media accounts on BlueSky and Mastodon
-* LinkedIn
+* Social media accounts on [BlueSky](https://bsky.app/profile/pyopensci.org) and [Mastodon](https://fosstodon.org/@pyOpenSci)
+* LinkedIn: https://www.linkedin.com/company/pyOpenSci
 * A blog on our [organization's website](https://www.pyopensci.org/blog)
-* YouTube
+* [YouTube](https://www.youtube.com/@pyopensci)
 
 (buffer)=
 ## Buffer for scheduled social media posts
 
 [Buffer](https://buffer.com/) is a [social media](https://www.pyopensci.org/handbook/community/social.html) platform that makes it easy to schedule, track, and collaborate on social media posts. While Buffer supports a host of platforms, pyOpenSci currently uses Buffer for
 * [Fosstodon](https://fosstodon.org/@pyOpenSci),
 * [Bluesky](https://bsky.app/profile/pyopensci.bsky.social), and
-* [LinkedIn](https://www.linkedin.com/company/pyOpenSci).
+* LinkedIn: https://www.linkedin.com/company/pyOpenSci
 
 Buffer is great for tracking some analtics and scheduling posts. However, generally, Buffer also has some challenges
 
@@ -26,10 +26,9 @@ Buffer is generally a great time-saving tool for pyOpenSci, especially when we d
 
 [Learn more about our social platforms here.](community-social)
 
-
 ## Linktree
 
-Linktree is a social media landing page that allows users to share multiple links from a single page, which is useful for landing pages on social media sites that provide limited space for external links.
+Linktree is a social media landing page that enables users to share multiple links from a single page, making it particularly useful for landing pages on social media sites that offer limited space for external links.
 
 Our active sites, platforms, and social media accounts are documented in a Linktr.ee account. The [Linktr.ee link](https://linktr.ee/pyopensci) is shared in the **Description** of our social media sites.