Release/v1.0.0

.github/CODEOWNERS

@@ -1,6 +1,5 @@
-# These owners will be the default owners for everything in
-# the repo. Unless a later match takes precedence,
-# @smcnab1 will be requested for
-# review when someone opens a pull request.
-# if you want to add more owners just write it after the demo user @OctoCat
+# These owners will be the default owners for everything in the repo. Unless a later match takes precedence,
+
+# @smcnab1 will be requested for review when someone opens a pull request.
+
 *       @smcnab1

.github/CODE_OF_CONDUCT.md

@@ -17,23 +17,23 @@ diverse, inclusive, and healthy community.
 Examples of behavior that contributes to a positive environment for our
 community include:
 
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
   and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
+- Focusing on what is best not just for us as individuals, but for the
   overall community
 
 Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery, and sexual attention or
+- The use of sexualized language or imagery, and sexual attention or
   advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
   address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
+- Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Enforcement Responsibilities
@@ -59,8 +59,7 @@ representative at an online or offline event.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-the following e-mail address sam@sammcnab.co.uk.
+reported to the community leaders responsible for enforcement via [this page](https://sammcnab.co.uk/contact).
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the
@@ -106,7 +105,7 @@ Violating these terms may lead to a permanent ban.
 ### 4. Permanent Ban
 
 **Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
+standards, including sustained inappropriate behavior, harassment of an
 individual, or aggression toward or disparagement of classes of individuals.
 
 **Consequence**: A permanent ban from any sort of public interaction within

.github/CONTRIBUTING.md

@@ -1,19 +1,73 @@
 # Contributing
 
-There are a lot of different ways to contribute to this project. See below for
-everything you can do and the processes to follow for each contribution method.
-Note that no matter how you contribute, your participation is governed by our
-[Code of Conduct](CODE_OF_CONDUCT.md).
+Contributions to SimuGen are welcome, including code changes, documentation improvements, bug reports, feature suggestions and clinical-content feedback.
 
-## Make changes to the code or docs
+Participation in this project is governed by the [Code of Conduct](CODE_OF_CONDUCT.md).
 
-Fork the project, make a change, and send a pull request! 
+## Code and documentation changes
 
-Make sure you read and follow the instructions in the [pull request template](PULL_REQUEST_TEMPLATE.md). And note
-that all participation in this project (including code submissions) is
-governed by our [Code of Conduct](CODE_OF_CONDUCT.md).
+To contribute code or documentation:
 
-## Submit bug reports or feature requests
+1. Fork the repository.
+2. Create a feature branch.
+3. Make and test your changes.
+4. Commit your changes with a clear commit message.
+5. Push the branch to your fork.
+6. Open a pull request.
 
-Just use the GitHub issue tracker to submit your bug reports and feature
-requests. 
+Please follow the guidance in the [pull request template](PULL_REQUEST_TEMPLATE.md) when submitting changes.
+
+Where your change affects the plugin, check that:
+
+- `plugin/plugin.json` remains valid.
+- Relevant skills continue to behave as intended.
+- Clinical simulation content remains educational rather than patient-specific.
+- No identifiable patient information or other sensitive personal data is introduced.
+- Documentation is updated where behaviour or structure has changed.
+
+## Bug reports
+
+Use the [GitHub issue tracker](https://github.com/smcnab1/SimuGen/issues) to report bugs.
+
+Please include enough information to reproduce the issue where possible.
+
+Do not include:
+
+- Identifiable patient information
+- Protected health information
+- Confidential organisational information
+- Credentials, secrets or API keys
+- Other sensitive personal data
+
+## Feature requests
+
+Feature suggestions are also welcome through the [GitHub issue tracker](https://github.com/smcnab1/SimuGen/issues).
+
+Where possible, describe:
+
+- The problem or educational need
+- The intended user or learner group
+- The expected behaviour
+- Why the change would improve SimuGen
+
+## Clinical-content feedback
+
+If you identify a potential clinical inaccuracy, outdated recommendation or unrealistic scenario behaviour, please open an issue and provide an authoritative source where possible.
+
+Suitable sources include current guidance from organisations such as NICE, NHS, Resuscitation Council UK, relevant Royal Colleges and other recognised professional bodies.
+
+## Pull requests
+
+Keep pull requests focused on a single change where practical.
+
+Before submitting:
+
+- Run the website build if the change affects the web app.
+- Review any affected plugin skills.
+- Update documentation where necessary.
+- Avoid unrelated formatting or dependency changes.
+- Confirm that no sensitive or identifiable information is included.
+
+## Licence
+
+By contributing to SimuGen, you agree that your contributions will be licensed under the project's [MIT Licence](../LICENSE.md).