docs: add cont and support

Author: Ma11hewThomas

CONTRIBUTING.md

@@ -0,0 +1,50 @@
+# Contributing
+
+First off, thank you for considering contributing to this project.
+
+## Reporting Issues
+
+Before submitting an issue, please check the issue tracker to ensure that the issue hasn't already been reported. If you find your issue already reported, you can subscribe to that issue to receive updates. If you have any additional information to add, please comment on the issue. If the issue is unnasigned and you'd like to contribute, assign the issue to yourself.
+
+## How to Contribute
+
+If you'd like to contribute, start by searching through the issues and pull requests to see whether someone else has raised a similar idea or question.
+
+If you don't see your idea listed, and you think it fits into the goals of this project, do one of the following:
+
+- If your contribution is minor, such as a typo fix, open a pull request.
+- If your contribution is major, or you have not yet decided how to implement your idea, open an issue to discuss it. This allows other contributors to point out any potential flaws or to help you flesh out your idea.
+
+### Pull Requests
+
+1. Fork the repository and create your branch from `main`.
+2. Write some code
+3. Make sure your code lints.
+4. Issue that pull request!
+
+### Commit Messages
+
+Write meaningful commit messages that provide insight into the changes made.
+
+## Finding Bugs
+
+If you find a bug, please report it in the issue tracker with a detailed description.
+
+## Feature Requests
+
+Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and aims of the project. Please provide as much detail and context as possible.
+
+## License
+
+By contributing to this project, you agree that your contributions will be licensed under MIT.
+
+## Acknowledgments
+
+Your contributions are sincerely appreciated. We want to make contributing to this project as easy and transparent as possible, whether it's:
+
+- Reporting a bug
+- Discussing the current state of the code
+- Submitting a fix
+- Proposing new features
+
+Thank you for your interest in contributing

README.md

@@ -90,8 +90,22 @@ go-ctrf-json-reporter can be used in conjunction with gotestsum
 gotestsum --jsonfile gotestsum.json && go-ctrf-json-reporter < gotestsum.json
 ```
 
+## Test Object Properties
+
+The test object in the report includes the following [CTRF properties](https://ctrf.io/docs/schema/test):
+
+| Name       | Type   | Required | Details                                                                             |
+| ---------- | ------ | -------- | ----------------------------------------------------------------------------------- |
+| `name`     | String | Required | The name of the test.                                                               |
+| `status`   | String | Required | The outcome of the test. One of: `passed`, `failed`, `skipped`, `pending`, `other`. |
+| `duration` | Number | Required | The time taken for the test execution, in milliseconds.                             |
+
 ## Troubleshoot
 
 ### Command Not Found
 
 When running go-ctrf-json-reporter results in a "command not found" error this usually means that the Go bin directory is not in your system's PATH.
+
+## Support Us
+
+If you find this project useful, consider giving it a GitHub star ⭐ It means a lot to us.