Website Restructure.

CONTRIBUTING.md

@@ -1,57 +1,6 @@
 # Contributing
-[//]: # (TODO: Maybe move this to the website!)
 
 Thank you for being interested in contributing to this project! 
 Your help is very valuable: to get a handle on the ethical implications of Data Science, we *need* to consider diverse viewpoints! 
 
-## *Types* of contribution
-Here are some ways to get involved. We would absolutely love your input on the following:
-1. Feedback on our [Data Hazard Labels](https://very-good-science.github.io/data-hazards/contents/materials/workshop/data-hazards.html), we accept suggestions through Issues and Pull Requests✨ here on GitHub, or via [email][dec-email]. For example you might suggest:
-    - Ways of rewording Data Hazard Label descriptions or titles.
-    - New examples of Data Hazards.
-    - New/updated "Safety Precautions" (ways of combatting Data Hazards).
-    - Ideas for new Data Hazards.
-2. Join one of [upcoming workshops](https://very-good-science.github.io/data-hazards/contents/upcoming-events.html) or (in development) asynchonous mailing lists to provide Data Hazards reviews on different projects.
-3. Contribute to any of our [workshop materials](https://very-good-science.github.io/data-hazards/contents/exercises.html) - or ideas for new materials (open an issue or  [email us][dec-email]).
-4. Use the Data Hazards materials to reflect on your own work and contribute this as an example to help other people use the 
-5. Find [GitHub issue][issues] that you know how to solve, and help us with that!
-
-## *How* to contribute
-
-[//]: # (TODO: Have a guide here to the way that the website is organised)
-
-We will develop these contribution guidelines as we go, including where to look in this repo for different files and so on.
-For now, they are a little thin, so if you'd like to help please get in touch with us, please [send us an email][dec-email] and we will help you to find what you're looking for!
-
-### Contributing on GitHub
-If you find an [issue][issues] that you'd like to help with, then please:
-1. Comment on it before you start working, so we don't repeat work.
-2. [Fork](https://help.github.com/articles/fork-a-repo) this repository to your own GitHub account
-3. Check that you are happy with the changes by [building the site locally](#build-the-site-locally).
-4. Then, once you've made your changes, submit a [pull request](https://help.github.com/articles/creating-a-pull-request): we'll review it as quick as we can 😄.
-
-### Adding slides
-We try to keep all our slides for Data Hazards on our website.
-
-The current process is:
-1. (Optional) create slides in powerpoint, upload to Google drive (which will convert it to Google slides) + check formatting (alternatively, create in Google slides)
-2. Create a new markdown web page.
-2. Publish google slides `File -> Publish to the web -> Embed -> Small`
-3. Copy and paste to new markdown web page.
-3. Make viewable with link `Share -> Anyone on the internet with this link can view` 
-4. Add link to markdown web page.
-
-Recommendations for a process to create html slides that works with myst markdown extremely welcome!
-
-### Build the site locally
-In order to build the site locally, you'll need to run the following from your root directory:
-`sphinx-build site/ site/_build/` 
-
-These require some Python packages to run. 
-You may want to set up a [virtual environment](https://docs.python.org/3/library/venv.html) first, so that you don't install these packages system-wide.
-Then you can install the packages using `pip install -r requirements.txt`
-
-
----
-[issues]: https://github.com/very-good-science/data-hazards/issues
-[dec-email]: [email protected]
+Please see out full contributing guidelines on the website: 

site/contents/about.md

@@ -0,0 +1,36 @@
+# About
+
+## How the project started 
+
+The Data Hazards project started 2021.
+We (Natalie and Nina) wanted a way to communicate what might go wrong in data science projects, because we were frustrated by the repetitive themes we were seeing in harmful technologies that we talked about in [Data Ethics Club](https://dataethicsclub.com).
+We were also concerned that many projects that have significant societal impact do not have those impacts scrutinised by an Ethics Committee, because they do not technically have research participants. 
+After that conversation we came up with the idea of Hazard labels for communicating these potential harms, and called them Data Hazards. 
+We decided they should be visual, like COSHH chemical hazards are, and that they should be a way for people at all stages of research to communicate about the same potential outcomes (no matter how far away those outcomes might seem).
+
+The image below describes the 'anatomy' of a Data Hazards label. 
+
+```{image} ../images/hazardanatomy.png
+:alt: An image of a orange square with a red hexagon in it and the words 'Title', 'Description', 'Examples', 'Safety precautions'. 
+```
+
+You can see [the current Data Hazard labels here](data-hazards).
+You can [read our original proposal here](materials/misc/proposal).
+
+Once we had thought of the original list of Hazards we wanted a way for researchers to think about them in a format that encouraged them to reflect, invite different opinions and make them think more broadly about the potential ethical concerns from their project. 
+This led to the development of our workshop format and [all the materials we have since made](materials) for self-reflection and teaching. 
+All our resources are designed for re-use by others. 
+
+
+## Ethos
+
+The Data Hazards are built on the foundations of [standpoint theory](https://en.wikipedia.org/wiki/Standpoint_theory). 
+This is an epistemiological theory that knowledge (including in the sciences) is not objective, and that our perspectives are shaped by our lived socio-political experiences. 
+This means that ethical problems are not going to have a single correct answer, and that to get a well-rounded understanding of the ethical issues of any new technology we need people from lots of different standpoints to analyse it from their perspective. 
+This is the best way we can understand the harms it could possibly cause.
+We also need to make sure that we are paying attention to how technology might be more likely to adversely affect people from minoritised backgrounds.
+
+In summary, the Data Hazards exist to prompt discussion, reflection and thought. 
+They are not a checkbox exercise, and there is no requirement for a group to come to a consensus. 
+In an individual context you will likely come to a conclusion, but someone else may have a different view.
+We hope that the Data Hazards discussion and reflective activities will help researchers be aware of a broader variety of potential ethical risks in tech projects, and that ethics is complex, situational and worth discussing.

site/contents/materials/code-of-conduct.md → site/contents/code-of-conduct.md

@@ -1,10 +1,10 @@
 # Code of Conduct
 
 We want all Data Hazards spaces (online or in person) to be places where people feel welcome to discuss their thoughts and ideas. 
-This Code of Conduct (CoC) was developed for Data Ethics Club, to ensure that those participating are protected from abuse, harassment or discrimination, 
+This Code of Conduct (CoC) aims to ensure that those participating in the Data Hazards community are protected from abuse, harassment or discrimination, 
 and that the discussions we have are supportive and productive. 
 
-This CoC is based on content from the [Jean Golding Institute’s](http://www.bristol.ac.uk/golding/) CoC for online events, [Arizona Diversity Journal Club CoC](https://www.as.arizona.edu/diversity_coffee/#two), 
+This CoC was originally developed for [Data Ethics Club](https://dataethicsclub.com), and is based on content from the [Jean Golding Institute’s](http://www.bristol.ac.uk/golding/) CoC for online events, [Arizona Diversity Journal Club CoC](https://www.as.arizona.edu/diversity_coffee/#two), 
 and the [Recurse Centre’s Social Rules](https://www.recurse.com/manual#sub-sec-social-rules). 
 If you would like to suggest an addition or amendment then you can [make an issue](https://github.com/very-good-science/ethical-data-science-journal-club/issues/new/choose), 
 submit a PR or [email us](https://github.com/very-good-science/data-ethics-club#organisers).

site/contents/contribute.md

@@ -0,0 +1,61 @@
+# Contributing
+
+```{toctree}
+:maxdepth: 1
+code-of-conduct
+contribute/style-guide
+contribute/how-to-contribute
+contribute/credit-for-contributions
+contribute/contributors
+contribute/changelog
+```
+
+The Data Hazards project is always welcoming new contributors!
+This page gives you an overview of how you can get involved. 
+You can see all of our wonderful existing contributors in our [Record of contributions](contribute/contributors). 
+
+We strongly welcome first-time GitHub users and are very happy to provide support if you would like to learn how to edit the repository.
+Please just [get in touch by email][dec-email] if that is the case.
+You could also come to our [community co-working calls](events/coworking)!
+
+All our content is created and shared under a [CC-BY 4.0 license](https://creativecommons.org/licenses/by/4.0/), and so if you do contribute to the repository your work will also be shared under this license. 
+
+---
+
+## 1. Decide how you would like to contribute
+
+We would absolutely love your input on the following:
+
+1. General feedback on our [Data Hazard Labels](data-hazards), which you can send to us through email or on [GitHub Discussions](https://github.com/very-good-science/data-hazards/discussions/new?category=feedback).
+2. Suggestions for new Data Hazard labels, or changes to them. 
+   For example you might suggest:
+    - Ways of rewording Data Hazard label descriptions or titles.
+    - New examples of Data Hazards.
+    - New/updated "Safety Precautions" (ways of combatting Data Hazards).
+    - Ideas for new Data Hazards.
+3. Join one of [upcoming events](events) or (in development) asynchonous mailing lists to provide Data Hazards reviews on different projects.
+4. Contribute to [any of our materials](materials) or share ideas for new materials to help others use the Hazards.
+    This could include:  
+    - Sharing a link to materials you have made. 
+    - Adding a written example of how you used the Hazards to our growing list. 
+    - Making additions or changes to the existing materials on the site. 
+5. Use the Data Hazards materials to reflect on your own work and contribute this as an example to help other people use the 
+6. Find [GitHub issue][issues] that you know how to solve, and help us with that!
+
+## 2. Read our [Code of Conduct](code-of-conduct) and [Style Guide](contribute/style-guide)
+
+These documents are linked above and in the side bar.
+They are both short, but we ask that you have read them to ensure that we can make sure this community is a welcoming place, and that the content we create is consistent and easy to understand.
+
+## 3. Make your contribution
+
+The [How to contribute](contribute/how-to-contribute) guide gives you an overview of how you should approach different contribution types. 
+
+## 4. Get credit
+
+The Data Hazards team are very keen to recognise all contributions people make to this project. 
+Check out our [Credit for contributions](contribue/../contribute/credit-for-contributions) page to see how to make sure you get acknowledged on the website. 
+
+---
+[issues]: https://github.com/very-good-science/data-hazards/issues
+[dec-email]: mailto:[email protected]

site/contents/contribute/changelog.md

@@ -0,0 +1,20 @@
+# Change log
+
+The change log records when changes that have been made to the project and gives a brief description of what the changes were. 
+The change log started in March 2022. 
+The most recent changes should be at the top of the list. 
+
+<!-- Example change log entry
+
+## DD-MM-YYYY: <10 words to summarise change
+More detailed paragraph (~100 words is more than enough!) that describes the changes in more detail and their impact.  
+[Your name](link to your github profile) -->
+
+## 07.03.2022: Move Data Hazards to individual pages
+[@ninadicara](https://github.com/ninadicara)  
+Moved all of the Hazards to their own individual pages, and linked them from the original sphynx panels. 
+Also capitalised all of the names so that they are consistently named. 
+This should make it easier for people to contribute to a single Hazard and record their contribution against it :) 
+
+
+

contributors.md → site/contents/contribute/contributors.md

@@ -1,4 +1,4 @@
-# Record of Contributions
+# Record of contributions
 
 The Data Hazards project exists because of the support and contributions of the many different people below.
 
@@ -45,6 +45,13 @@ To be added, please [submit an issue](https://github.com/very-good-science/data-
 
 <!--- Add yourself here!--->
 
+### Nina Di Cara  
+* Role: Co-PI
+* ORCID [0000-0002-6179-1067](https://orcid.org/0000-0002-6179-1067)
+* GitHub: [ninadicara](https://github.com/ninadicara)
+> Along with [Natalie](natalie-zelenka) I worked on the original idea for the Data Hazards, created resources around them (like teaching materials, slides, reflective prompts, illustrations), planned and delivered our workshops, and the website content. Jointly Natalie and I provide leadership for the project in terms of its next steps and uses. I care a lot about reducing the harm that technology can do to people who may not have power to fight back against, and hope this projects goes some way to making us all think more carefully about what we can all do as individuals to prevent harm. I am also thrilled to have been able to work with (and continue to work with) all the fantastic people who have got involved with this project! 
+
+
 ### Natalie Zelenka
 * Role: Co-PI 
 * ORCID: [0000-0002-1007-0286](https://orcid.org/0000-0002-1007-0286)

site/contents/contribute/credit-for-contributions.md

@@ -0,0 +1,48 @@
+# Credit for contributions
+
+We strongly believe everyone should be credited for their contribution to this project, no matter how big or small! 
+We also want people to be able to use their contributions to open source projects like this one as evidence in their CVs or applications. 
+
+To achieve this aim we have two ways to be acknowledged on the site: - you can do both or just (1):  
+
+1. Be added to the front page list of contributors, which uses the [all-contributors bot](https://allcontributors.org/).  
+2. Add a more detailed overview of your contribution to the [Record of contributions](contributors).
+
+## 1. Add yourself to our contributors list with all-contributors
+
+We have an [open issue](https://github.com/very-good-science/data-hazards/issues/109) for adding people to the list of contributors.
+The all-contributors bot [uses an emoji key] that recognises lots of different types of contribution. 
+If you do anything on the website (from fixing a broken link or typo all the way to writing a new page) then please do add yourself using the instructions on the issue! 
+We will do our best to add you too, but it is often faster for you to do it :)
+
+To use it, comment in an issue or pull-request something like:
+`@all-contributors please add @NatalieThurlby for eventOrganizing`
+The bot will then set up a pull-request (PR) to add the named person to the contributors list, and the PR will update the list of contributors at the bottom. We have an open issue that we use to call the all-contributors bot.
+
+Some people aren’t on GitHub of course, so to add them to the contributions list you can manually edit the file .all-contributorsrc by adding the following object to the list:
+```
+    {
+      "login": "",
+      "name": "FirstName SecondName",
+      "avatar_url": "https://www.example.com/profile-pic.jpg",
+      "profile": "https://mywebsite.com",
+      "contributions": [
+        "content"
+      ]
+    },
+```
+This person’s contribution will then show up the next time you use the bot to add someone to the repo.
+
+
+## 2. Add yourself to our [Record of contributions](contributors)
+
+It can be useful to have a more detailed description of your involvement in the project. 
+We would love for everyone to be listed here, but understand it can take a bit of time that not everyone has. 
+If you would like to be added to the [Record of contributions](contributors) then either [make an issue using the template](https://github.com/very-good-science/data-hazards/issues/new?assignees=&labels=documentation&template=contributors.md&title=Add+new+contributor) or make a PR on the page itself. 
+Please include the following information: 
+
+* Your Name  
+* Your Role and Affiliation  
+* (Optional) ORCID ID or other persistent identifier  
+* (Optional) Personal contact details or website  
+* Overview of your contribution to the Data Hazards Project - please don't be modest!   

site/contents/contribute/how-to-contribute.md

@@ -0,0 +1,54 @@
+# How to contribute
+
+Depending on what you would like to do there are different ways to get involved. 
+Please check out the options below!
+If you can't find what you are looking for then [send us an email][dec-email] and we will help!
+You can also come to our [open community co-working calls](../events/coworking) if you would like to chat to us about an idea you have had.
+
+
+## Suggesting new or improved Data Hazards
+
+In the first instance please [start a Discussion with your idea](https://github.com/very-good-science/data-hazards/discussions/new?category=ideas) in the 'Ideas' category.
+We can then chat openly on GitHub about the suggestion, and this gives other people the opportunity to weigh-in on any changes we are considering. 
+Once changes have been agreed then you can follow the process below for [Updating our documentation](#updating-our-documentation).
+
+If you would rather you can also [email us][dec-email] to discuss.
+
+## Making changes to the website content
+
+This website is based on a tool called Sphynx, which allows us to create all our content in Markdown and rendered it as a website. 
+To find the documentation you want to change or add then follow the file path that is indicated by the website link from the `site` folder in the repo. 
+To add the changes to the main repository then:
+
+1. [Fork](https://help.github.com/articles/fork-a-repo) this repository to your own GitHub account.  
+2. Check that you are happy with the changes by [building the site locally](#build-the-site-locally).  
+3. Before submitting your changes, please add a note to the [Change Log](changelog) that describes the change you made.
+4. Then, once you've made your changes, submit a [pull request](https://help.github.com/articles/creating-a-pull-request): we'll review it as quick as we can 😄.
+
+If you are fixing an [issue][issues] then please comment on it before you start working so that we don't repeat your work! 
+
+### Build the site locally
+
+In order to build the site locally, you'll need to run the following from your root directory:
+`sphinx-build site/ site/_build/` 
+
+These require some Python packages to run. 
+You may want to set up a [virtual environment](https://docs.python.org/3/library/venv.html) first, so that you don't install these packages system-wide.
+Then you can install the packages using `pip install -r requirements.txt`
+
+## Adding slides
+We try to keep all our slides for Data Hazards on our website.
+
+The current process is:
+1. (Optional) create slides in powerpoint, upload to Google drive (which will convert it to Google slides) + check formatting (alternatively, create in Google slides)
+2. Create a new markdown web page.
+2. Publish google slides `File -> Publish to the web -> Embed -> Small`
+3. Copy and paste to new markdown web page.
+3. Make viewable with link `Share -> Anyone on the internet with this link can view` 
+4. Add link to markdown web page.
+
+Recommendations for a process to create html slides that works with myst markdown extremely welcome!
+
+---
+[issues]: https://github.com/very-good-science/data-hazards/issues
+[dec-email]: mailto:[email protected]