updated contributing.md

Author: gonzolively

CODEOWNERS.md

@@ -0,0 +1,46 @@
+# Contributing to Ocre's Documentation
+
+We welcome contributions to our documentation! This guide (still very mucah a WIP) will help you get started with the process.
+
+## Getting Started
+
+1. Fork the repository.
+2. Clone your fork: `git@github.com:<your_username>/project-ocre.github.io.git`
+3. Create a new branch: `git checkout -b your-branch-name`
+
+## Making Changes
+
+1. Navigate to the `docs` folder and make your changes using your preferred text editor.
+2. Test your changes locally by running `bundle exec jekyll serve` in the project root.
+
+## Submitting Changes
+
+1. Commit your changes: `git commit -am 'Add a brief description of your changes'`
+2. Push to your fork: `git push origin your-branch-name`
+3. Submit a pull request (PR) to the main repository.
+
+## Pull Request Guidelines
+
+- Provide a clear title and description for your PR.
+- Link any related issues in the PR description.
+- Ensure your changes don't break existing documentation.
+- Be open to feedback and be ready to make adjustments if needed.
+
+## Reporting Issues
+
+If you find a problem with the documentation:
+
+1. Check if the issue already exists in our [issue tracker](https://github.com/project-ocre/project-ocre.github.io/issues).
+2. If not, create a new issue, providing as much detail as possible.
+
+## Community Guidelines
+
+- Be respectful and inclusive in your language and conduct.
+- Help others if you can.
+- If you disagree, do so constructively and politely.
+
+## Questions?
+
+If you have any questions, feel free to [reach out](https://lfedge.slack.com/archives/C07F190CC3X) on Slack or open an issue for discussion.
+
+Thank you for contributing to Ocre's documentation!