Scarlett/update contributing (#276)

* Update CONTRIBUTING.md

* Update CONTRIBUTING.md

remove visualization

* Update CONTRIBUTING.md

* Update CONTRIBUTING.md

* Add in note about architecture

Author: sattensil

CONTRIBUTING.md

@@ -1,9 +1,42 @@
 # Contributing to Graphiti
 
-We're excited you're interested in contributing to Graphiti! This document outlines the process for contributing to our project. We welcome contributions from everyone, whether you're fixing a typo, improving documentation, or adding a new feature.
+We're thrilled you're interested in contributing to Graphiti! As firm believers in the power of open source collaboration, we're committed to building not just a tool, but a vibrant community where developers of all experience levels can make meaningful contributions.
 
-## Getting Started
+When I first joined this project, I was overwhelmed trying to figure out where to start. Someone eventually pointed me to a random "good first issue," but I later discovered there were multiple ways I could have contributed that would have better matched my skills and interests.
 
+We've restructured our contribution paths to solve this problem:
+
+# Four Ways to Get Involved
+
+### Pick Up Existing Issues
+Our developers regularly tag issues with "help wanted" and "good first issue." These are pre-vetted tasks with clear scope and someone ready to help you if you get stuck.
+
+### Create Your Own Tickets
+See something that needs fixing? Have an idea for an improvement? You don't need permission to identify problems. The people closest to the pain are often best positioned to describe the solution.
+
+For **feature requests**, tell us the story of what you're trying to accomplish. What are you working on? What's getting in your way? What would make your life easier? Submit these through our [GitHub issue tracker](https://github.com/getzep/graphiti/issues) with a "Feature Request" label.
+
+For **bug reports**, we need enough context to reproduce the problem. Use the [GitHub issue tracker](https://github.com/getzep/graphiti/issues) and include:
+- A clear title that summarizes the specific problem
+- What you were trying to do when you encountered the bug
+- What you expected to happen
+- What actually happened
+- A code sample or test case that demonstrates the issue
+
+### Share Your Use Cases
+Sometimes the most valuable contribution isn't code. If you're using our project in an interesting way, add it to the [examples](https://github.com/getzep/graphiti/tree/main/examples) folder. This helps others discover new possibilities and counts as a meaningful contribution. We regularly feature compelling examples in our blog posts and videos - your work might be showcased to the broader community!
+
+### Help Others in Discord
+Join our [Discord server](https://discord.gg/2JbGZQZT)  community and pitch in at the helpdesk. Answering questions and helping troubleshoot issues is an incredibly valuable contribution that benefits everyone. The knowledge you share today saves someone hours of frustration tomorrow.
+
+## What happens next?
+Once you've found an issue tagged with "good first issue" or "help wanted," or prepared an example to share, here's how to turn that into a contribution:
+
+1. Share your approach in the issue discussion or [Discord](https://discord.gg/2JbGZQZT) before diving deep into code. This helps ensure your solution adheres to the architecture of Graphiti from the start and saves you from potential rework. 
+
+2. Fork the repo, make your changes in a branch, and submit a PR. We've included more detailed technical instructions below; be open to feedback during review.
+
+## Setup
 1. Fork the repository on GitHub.
 2. Clone your fork locally:
    ```
@@ -83,20 +116,7 @@ make check
 
 This command will format your code, run linting checks, and execute tests.
 
-## Reporting Bugs
-
-Use the GitHub issue tracker at https://github.com/getzep/graphiti/issues to report bugs. When filing an issue, please include:
-
-- A clear title and description
-- As much relevant information as possible
-- A code sample or an executable test case demonstrating the expected behavior that is not occurring
-
-## Feature Requests
-
-Feature requests are welcome. Please provide a clear description of the feature and why it would be beneficial to the project. You can submit feature requests through the GitHub issue tracker.
-
-## Questions?
-
-If you have any questions, feel free to open an issue or reach out to the maintainers through the GitHub repository.
+# Questions?
+Stuck on a contribution or have a half-formed idea? Come say hello in our [Discord server](https://discord.gg/2JbGZQZT). Whether you're ready to contribute or just want to learn more, we're happy to have you! It's faster than GitHub issues and you'll find both maintainers and fellow contributors ready to help.
 
 Thank you for contributing to Graphiti!