Merge pull request #73 from nhs-r-community/62-contact-page

62 contact page

code-of-conduct.qmd

@@ -4,7 +4,7 @@ We value the participation of every member of our community and want to ensure t
 
 Accordingly, everyone who participates in the NHS-R Community and the NHS-R Community Way project is expected to show respect and courtesy to other community members at all times.
 
-Zoë Turner, as lead instigator in this community, and all project members, are dedicated to a ***harassment-free experience for everyone***, regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, age, religion or class. **We do not tolerate harassment by and/or of members of our community in any form**.
+Zoë Turner, as lead investigator in this community, and all project members, are dedicated to a ***harassment-free experience for everyone***, regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, age, religion or class. **We do not tolerate harassment by and/or of members of our community in any form**.
 
 We are particularly motivated to support new and/or anxious collaborators, people who are looking to learn and develop their skills, and anyone who has experienced discrimination in the past.
 
@@ -29,7 +29,7 @@ The NHS-R Community has a core development team which consists of:
 * [Zoë Turner](mailto:[email protected]) - who is also the lead investigator of the NHS-R Community Way and is responsible for enforcing the Code of Conduct
 * [Chris Beeley](mailto:[email protected]) - who leads the NHS-R Community
 
-The central email [[email protected]](mailto:[email protected]) is accessed by Chris Beeley, Zoë Turner and administrative/support staff in the Strategy Unit.
+The [central email](#contact-us) is accessed by Chris Beeley, Zoë Turner and administrative/support staff in the Strategy Unit.
 
 Both Chris Beeley and Zoë Turner are employees of NHS Midlands and Lancashire Commissioning Strategy Unit and are not excluded from this Code of Conduct but, if required, contact can be made with the Senior Management team within the Strategy Unit in the same organisation through [[email protected]](mailto:[email protected]) which neither have access to.
 
@@ -130,9 +130,9 @@ This can include contacting law enforcement (or other local personnel) and speak
 If the act is ongoing, any community member may act immediately, before reaching consensus, to diffuse the situation.
 In ongoing situations, any member may at their discretion employ any of the tools available in this enforcement manual, including bans and blocks online, or removal from a physical space.
 
-In situations where an individual community member acts unilaterally, they must inform [[email protected]](mailto:[email protected]) as a central point of contact as soon as possible, and report their actions for review within 24 hours.
+In situations where an individual community member acts unilaterally, they must inform [the core development team](#contact-us) as a central point of contact as soon as possible, and report their actions for review within 24 hours.
 
-It is likely that a situation at this level will require incidents being raised in the NHS Midlands and Lancashire Commissioning Strategy Unit as well as any other corresponding organisations. Please ensure that you comply with local incident reporting systems and share incident reference numbers with [[email protected]](mailto:[email protected]).
+It is likely that a situation at this level will require incidents being raised in the NHS Midlands and Lancashire Commissioning Strategy Unit as well as any other corresponding organisations. Please ensure that you comply with local incident reporting systems and share incident reference numbers with [the core development team](#contact-us).
 
 ## Less-Urgent Situations
 
@@ -147,7 +147,7 @@ Upon receiving a report of an incident, the Code of Conduct committee will revie
 
 This information will be collected either in person or in writing.
 The Code of Conduct committee will provide a written summary of the information surrounding the incident.
-All participants will be anonymised in the summary report, referred to as "Community Member 1", "Community Member 2", or "Research Team Member 1".
+All participants will be anonymised in the summary report, referred to as "Community Member 1", "Community Member 2", or "Core Development Team Member 1".
 The "de-anonymising key" will be kept in a separate file and only accessed to link repeated reports against the same person over time.
 
 The Code of Conduct committee will aim to have a resolution agreed upon within 5 working days.
@@ -167,14 +167,14 @@ Possible responses may include:
 * Nothing, if the issue reported is not a violation or outside of the scope of this Code of Conduct.
 * A private in-person conversation between a member of the team and the individual(s) involved.
   In this case, the person who has the conversation will provide a written summary for record keeping.
-* A private written reprimand from a member of the research team to the individual(s) involved.
-  In this case, the research team member will deliver that reprimand to the individual(s) over email, cc'ing [email protected] for record keeping.
+* A private written reprimand from a member of the core development team to the individual(s) involved.
+  In this case, the core development team member will deliver that reprimand to the individual(s) over email, cc'ing [the core development team](#contact-us) for record keeping.
 * A public announcement of an incident, ideally in the same venue that the violation occurred (i.e. on the listserv for a listserv violation; GitHub for a GitHub violation, etc.).
   The committee may choose to publish this message elsewhere for posterity.
 * An imposed "time out" from online spaces.
   Zoë Turner and Chris Beeley will communicate this "time out" to the individual(s) involved.
 * A permanent or temporary ban from some or all NHS-R Community project spaces (GitHub, in-person events etc).
-  The research team will maintain records of all such bans so that they may be reviewed in the future, extended to a Code of Conduct safety team as it is built, or otherwise maintained.
+  The core development team will maintain records of all such bans so that they may be reviewed in the future, extended to a Code of Conduct safety team as it is built, or otherwise maintained.
   If a member of the community is removed from an event they will not be reimbursed for any part of the event that they miss.
 
 Once a resolution is agreed upon, but before it is enacted, a member of the Code of Conduct committee will contact the original reporter and any other affected parties and explain the proposed resolution.

community-handbook.qmd

@@ -7,11 +7,11 @@ Sessions are recorded and posted onto the NHS-R Community [YouTube channel](http
 
 There is no restriction on who can attend the webinar and people can join/sign up through the [NHS-R Community website](#website).
 
-Suggestions for webinars can be emailed to [[email protected]](mailto:[email protected]).
+Suggestions for webinars can be emailed to [the core development team](#contact-us).
 
 # Workshops from volunteers
 
-To volunteer any workshops please contact [[email protected]](mailto:[email protected]).
+To volunteer any workshops please contact [the core development team](#contact-us).
 
 ## Introduction to R and R Studio
 
@@ -44,7 +44,7 @@ See section [Video Recording](#recordings) for more information.
 
 # Social Media
 
-## NHS-R Slack
+## NHS-R Slack {#slack}
 
 [https://nhsrcommunity.slack.com/](https://nhsrcommunity.slack.com/)
 
@@ -63,7 +63,7 @@ Because this is a free account we don't have a history of posts but they would b
 
 ### Accessing the Slack
 
-Some organisations' emails have been added to the white list but because there are so many public sector organisations it may be that you require an individual link to join. Please contact the central email [[email protected]]([email protected]) for the link. 
+Some organisations' emails have been added to the white list but because there are so many public sector organisations it may be that you require an individual link to join. Please contact the central email [the core development team](#contact-us) for the link. 
 Links that are shared are only available for several days.
 
 It's best to use an organisational email for the group, but not necessary, and you are also able to change the email once you've joined.
@@ -111,7 +111,7 @@ Access to register events is based on the membership level and the default is fr
 Core memberships is available to all NHS, public sector and civil servants and allows registration to all workshops and webinars.
 We restrict the numbers to workshops and so restrict places to just Core members.
 Webinars though, don't have the same restrictions and so are open to both Core and Fringe members to attend the live event. 
-The site automatically detects emails according to a white list that is maintained through the website and so we can add to that when notified at [[email protected]](mailto:[email protected]).
+The site automatically detects emails according to a white list that is maintained through the website and so we can add to that when notified at [the core development team](#contact-us).
 
 ### Changes of emails on website
 
@@ -120,7 +120,7 @@ This is because tickets are restricted in number and we have to be mindful of pe
 
 ### Confirming Core membership
 
-If you are in a situation where you would like a Core membership but can only apply as a Fringe member (for example you cannot use your work email and wish to use gmail, google and so on) or your account has been reset in prepartion for events like the conference please contact [[email protected]](mailto:[email protected]) with details of your situation.
+If you are in a situation where you would like a Core membership but can only apply as a Fringe member (for example you cannot use your work email and wish to use gmail, google and so on) or your account has been reset in prepartion for events like the conference please contact [the core development team](#contact-us) with details of your situation.
 
 ### Deletion of website membership
 
@@ -140,7 +140,7 @@ Future deletions are expected for:
 
 ### Password resets
 
-It is possible to request a password reset, however, if this is going to an address that has changed due to organisational change or you have moved job, please contact [[email protected]](mailto:[email protected]) for this to be updated manually.
+It is possible to request a password reset, however, if this is going to an address that has changed due to organisational change or you have moved job, please contact [the core development team](#contact-us) for this to be updated manually.
 
 ## Mailing list
 
@@ -169,7 +169,7 @@ We host blogs on the NHS-R Community website and we welcome contributions from a
 We review blogs before posting and will give feedback if there are any reasons that we can't publish.
 Blogs are rarely removed so some will be out of date due to the changes in the programs like R and best practice.
 
-Submissions for blogs can be in any format but need to be easily copied and pasted to [[email protected]](mailto:[email protected]). 
+Submissions for blogs can be in any format but need to be easily copied and pasted to [the core development team](#contact-us). 
 For this reason pdf formats are not necessarily the easiest to share content.
 
 Pictures and charts can be included in the blogs and these are expected to have Alternative Text or Captions for greater accessibility.

index.qmd

@@ -7,6 +7,10 @@ Like The Turing Way, this is an open source, open collaboration, and community-d
 We are called NHS-R Community but our contributors come from Local Authorities, Civil Service, Public Sector, Academia, Voluntary Sector, Charities and as individuals with no organisational connection. 
 Our goal is to promote R - extended to data science tools - and to do this in an open way by supporting and promoting open code sharing which includes other media content like videos of our workshops and conferences. 
 
+## Contact us {#contact-us}
+
+The NHS-R Community can be found on [Slack](#slack) and the core support team through the email [the core development team](#contact-us).
+
 ::: {.callout-tip title="Where to start?"}
 This book is not meant to be read from start to finish and we recommend that you read the Code of Conduct first. 
 :::
@@ -16,7 +20,7 @@ This is a book about the NHS-R Community, how it works and its values.
 
 We have a book to help with technical resources and experiences getting started with open source programs called [Statement on Tools](https://tools.nhsrcommunity.com/) and a book for [Open Analytic Resource](https://resources.nhsrcommunity.com/) links started by AphA in 2020.
 
-The [training book](https://training.nhsrcommunity.com/) contains NHS-R Community training materials and [R4DS Unofficial Solutions](https://r4ds-solutions.nhsrcommunity.com/) is being written by the NHS-R Book club.
+The [training book](https://training.nhsrcommunity.com/) contains NHS-R Community training materials.
 :::
 
 # Our Community {.unnumbered}
@@ -34,7 +38,7 @@ The NHS-R Community Way reflects our:
 * above all the community
 
 Everything here is available for free under a CC-BY licence. Please use and re-use whatever you need, for any purpose and all the book is collaboratively written and open from the start. To make this book and the community truly accessible to everyone, we invite you to contribute your skills and bring your perspectives into this project. 
-Write and issue, do a pull request or even [NHS-R Community](mailto:[email protected]). 
+Write and issue, do a pull request or even [the core development team](#contact-us). 
 
 The NHS-R Community initially received funding for its activities but is now completely reliant upon volunteers. 
 There is no restriction to who you work for, what your background is or what skills you have as we are the sum of all our parts and the more diverse and varied we are, the better our work together will be. 

training.qmd

@@ -1,6 +1,6 @@
-# Training {.unnumbered, #training}
+# Training {.unnumbered}
 
-## Posit Cloud
+## Posit Cloud {#training}
 
 NHS-R Community pay for an account to use workspaces and projects for training/workshops.
 These mean that people can have projects that are set up with all the packages they require, have access to the latest version of R and RStudio and projects can be preloaded with any scripts or data.
@@ -13,9 +13,9 @@ The Posit Cloud account is monitored and maintained by admins who have access to
 Admins are:
 
 * [Zoë Turner](mailto:[email protected])
-* [Tom Jemmett]([email protected])
-* [Chris Beeley]([email protected])
-* [NHSR Administration]([email protected]) - access to this email is detailed in the [NHS-R Way](https://nhsrway.nhsrcommunity.com) book in the [Code of Conduct - Introduction](https://nhsrway.nhsrcommunity.com/code-of-conduct.html)
+* [Tom Jemmett](mailto:[email protected])
+* [Chris Beeley](mailto:[email protected])
+* [NHSR Administration](mailto:[email protected]) - access to this email is detailed in the [NHS-R Way](https://nhsrway.nhsrcommunity.com) book in the [Code of Conduct - Introduction](https://nhsrway.nhsrcommunity.com/code-of-conduct.html)
 
 ### Posit Cloud terminology
 
@@ -107,7 +107,7 @@ and follow the slides published through [GitHub](https://intro-git-github.nhsrco
 ### Course materials
 
 Materials produced by and for NHSR Community will be available through [GitHub](https://github.com/nhs-r-community).
-However, some workshops are provided with course material available through Posit Cloud only so contact [[email protected]](mailto:[email protected]) to request materials.
+However, some workshops are provided with course material available through Posit Cloud only so contact [the core development team](#contact-us) to request materials.
 
 ## Introduction to R and RStudio course materials
 
@@ -168,7 +168,7 @@ The NHS-R Community confirmation email will include:
 * the Posit Cloud specific workspace url and 
 * a calendar invitation
 
-If you are not sure that you can access Zoom from your work laptop, please request a test Zoom meeting coordinated by [[email protected]](mailto:[email protected]).
+If you are not sure that you can access Zoom from your work laptop, please request a test Zoom meeting coordinated by [the core development team](#contact-us).
 
 ## Modern desktop users (NHS England)