Added contribution guidance (#35)

<!-- markdownlint-disable-next-line first-line-heading -->
## Description

<!-- Describe your changes in detail. -->
This adds contribution guidance for this project.

## Context

<!-- Why is this change required? What problem does it solve? -->
This allows for any potential future requests or development to meet
expected standards.

## Type of changes

<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply. -->

- [ ] Refactoring (non-breaking change)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would change existing
functionality)
- [ ] Bug fix (non-breaking change which fixes an issue)

## Checklist

<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->

- [x] I am familiar with the [contributing
guidelines](./CONTRIBUTING.md)
- [x] I have followed the code style of the project
- [ ] I have added tests to cover my changes
- [x] I have updated the documentation accordingly
- [ ] This PR is a result of pair or mob programming

---

## Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others
privacy, we kindly ask you to NOT including [PII (Personal Identifiable
Information) / PID (Personal Identifiable
Data)](https://digital.nhs.uk/data-and-information/keeping-data-safe-and-benefitting-the-public)
or any other sensitive data in this PR (Pull Request) and the codebase
changes. We will remove any PR that do contain any sensitive
information. We really appreciate your cooperation in this matter.

- [x] I confirm that neither PII/PID nor sensitive data are included in
this PR and the codebase changes.

Author: davethepunkyone

.github/PULL_REQUEST_TEMPLATE.md

@@ -20,9 +20,9 @@
 
 <!-- Go over all the following points, and put an `x` in all the boxes that apply. -->
 
-- [ ] I am familiar with the [contributing guidelines](../docs/CONTRIBUTING.md)
+- [ ] I am familiar with the [contributing guidelines](https://github.com/nhs-england-tools/playwright-python-blueprint/blob/main/CONTRIBUTING.md)
 - [ ] I have followed the code style of the project
-- [ ] I have added tests to cover my changes
+- [ ] I have added tests to cover my changes (where appropriate)
 - [ ] I have updated the documentation accordingly
 - [ ] This PR is a result of pair or mob programming
 

.vscode/settings.json

@@ -7,6 +7,8 @@
   "cSpell.words": [
     "addopts",
     "codegen",
+    "Licence",
+    "organisation",
     "pytest",
     "utilise",
     "utilised",

CONTRIBUTING.md

@@ -1,3 +1,40 @@
-# Contributing to this project
+# Contributing To This Project
 
-This page will be populated in the near future to outline the contribution process.
+With this project, we actively encourage anyone who may have any ideas or code that could make this repository better to contribute
+in any way they can.
+
+## How To Contribute
+
+If you have an idea about something new that could be added, then please raise a
+[Feature Request via the Issues tab](https://github.com/nhs-england-tools/playwright-python-blueprint/issues/new/choose) for this
+repository. Even if you don't feel you have the technical ability to implement the request, please raise an issue regardless as
+the maintainers of this project will frequently review any requests and attempt to implement if deemed suitable for this blueprint.
+
+If you have some code you think could be implemented, please raise a Feature Request and
+[create a fork of this repository](https://github.com/nhs-england-tools/playwright-python-blueprint/fork) to experiment and ensure
+that the change you want to push back works as intended.
+
+## Contribution Requirements
+
+For any contributions to this project, the following requirements need to be met:
+
+- You must be a member of the [NHS England Tools](https://github.com/nhs-england-tools) organisation on GitHub.
+- [Any commits must be signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits), so they show as verified once they reach GitHub. This checking serves as part of our CI/CD process, so unsigned commits will prevent a pull request from being merged.
+- For any utility methods that are added to this framework in the `utils` directory, the following applies:
+  - Unit tests for the utility should be added to the `tests_utils` directory and need to be tagged with the `utils` mark.
+  - Documentation for these classes and how to use any methods should also be added to the `docs/utilities-guide` directory.
+  - Each method that is intended to be used as part of a class should have a correctly formatted docstring, to allow for developers using Intellisense within their IDE to understand what the code is intended to do.
+- All CI/CD checks will need to pass before any code is merged to the `main` branch - this includes ensuring appropriate formatting of code and documentation, security checks and that all unit and example tests pass.
+
+## Things We Want
+
+What we are particularly interested in is:
+
+- Any utility classes that can uniformly applied to any project. This may be something that's been created for your own project and by doing some minor abstraction any other teams working in a similar way could adopt this functionality.
+- Any development code that supports executing this project in a CI/CD fashion. This primarily covers any changes that support development principles outlined in the [Software Engineering Quality Framework](https://github.com/NHSDigital/software-engineering-quality-framework), and could include logic around how the test code is containerized.
+- Any changes that allow for test reporting in a consistent, reliable, maintainable and interesting format for varying stakeholders. This includes logic that expands on from the reporting we generate, such as example scripts for how to generate dashboards using the data we generate.
+
+Examples:
+
+- Say you've created a utility for generating test patients within your application. Any elements of this code that could be universally applied and other teams are likely to use (e.g. NHS number, patient name) we would want in this blueprint. If there's something business specific to your project that exists as part of this code (e.g. a unique reference number that only applies to your service), then we would advise removing that logic from any code before raising a pull request here.
+  - If you do end up adding a utility class in this format in a more generic way to this project, you can subsequently [inherit the utility class](https://docs.python.org/3/tutorial/classes.html#inheritance) to include your additional business-specific requirements within your own version of the class.

README.md

@@ -17,6 +17,7 @@ NOTE: This project is currently under initial development so isn't finalised, bu
     - [Configuration](#configuration)
   - [Getting Started](#getting-started)
   - [Utilities](#utilities)
+  - [Contributing](#contributing)
   - [Contacts](#contacts)
   - [Licence](#licence)
 
@@ -76,16 +77,21 @@ This blueprint also provides the following utility classes, that can be used to
 |Utility|Description|
 |-------|-----------|
 |[Axe](./docs/utility-guides/Axe.md)|Accessibility scanning using axe-core.|
+|[Date Time Utility](./docs/utility-guides/DateTimeUtility.md)|Basic functionality for managing date/times.|
 |NHSNumberTools|Basic tools for working with NHS numbers.|
 
+## Contributing
+
+Further guidance on contributing to this project can be found in our [contribution](./CONTRIBUTING.md) page.
+
 ## Contacts
 
-If you have any queries regarding this blueprint, please contact [[email protected]](mailto:dave.harding1@nhs.net).
+If you have any ideas or require support for this project, please [raise an issue via this repository](https://github.com/nhs-england-tools/playwright-python-blueprint/issues/new/choose) using the appropriate template.
 
-## Licence
+If you have any general queries regarding this blueprint, please contact [[email protected]](mailto:[email protected]).
 
-> The [LICENCE.md](./LICENCE.md) file will need to be updated with the correct year and owner
+## Licence
 
-Unless stated otherwise, the codebase is released under the MIT License. This covers both the codebase and any sample code in the documentation.
+Unless stated otherwise, the codebase is released under the [MIT License](LICENCE.md). This covers both the codebase and any sample code in the documentation.
 
 Any HTML or Markdown documentation is [© Crown Copyright](https://www.nationalarchives.gov.uk/information-management/re-using-public-sector-information/uk-government-licensing-framework/crown-copyright/) and available under the terms of the [Open Government Licence v3.0](https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/).

docs/utility-guides/DateTimeUtility.md

@@ -19,4 +19,4 @@ The docstrings also specify when arguments are optional, and what the default va
     from tests_utils.date_time_utils import DateTimeUtils
 
         def test_date_format(page: Page) -> None:
-        expect(page.locator("#date")).to_contain_text(DateTimeUtils.current_datetime()))
+        expect(page.locator("#date")).to_contain_text(DateTimeUtils.current_datetime())