📝 update contribution guide (#122)

Signed-off-by: Sindre Kjelsrud <[email protected]>

Author: SindreKjelsrud

CONTRIBUTING.md

@@ -1,4 +1,8 @@
-# Contributing to Chimera!
+# Contributing to 🦁Chimera🐍!
+
+First and foremost, a huge thank you for considering contributing to Chimera! Whether you're fixing a bug, proposing a new feature, or pondering becoming a maintainer, your support is what keeps this project alive and kicking. 🫶
+
+## About 📄
 
 We want to make contributing to this project as easy and transparent as possible, whether it's:
 
@@ -8,41 +12,50 @@ We want to make contributing to this project as easy and transparent as possible
 - Proposing new features
 - Becoming a maintainer
 
-## We Develop with Github
+Therefore we've created this document to provide a set of best practices for your contributions!
 
-We use github to host code, to track issues and feature requests, as well as accept pull requests.
+## How to Contribute
 
-## SOON: We will Use [Github Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
+### Reporting a bug 🐛
 
-Pull requests are the best way to propose changes to the codebase (we use [Github Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
+**Spot a bug?** We use Github [issues](https://github.com/ChimeraCSS/ChimeraCSS/issues) for tracking. Reporting is simple:
 
-1. Fork the repo and create your branch from `master`.
-2. If you've added code that should be tested, add tests.
-3. Ensure the test suite passes.
-4. Make sure your code lints.
-5. Issue that pull request!
+1. **Check if the bug exists:** Browse existing issues to avoid duplicates
+2. **Report:** [Open a new issue](https://github.com/ChimeraCSS/ChimeraCSS/issues/new/choose), providing a clear title and description. Screenshots and code snippets are highly encouraged!
 
-## Any contributions you make will be under the Apache license 2.0
+### Discuss the State of the Code 💬
 
-In short, when you submit code changes, your submissions are understood to be under the same Apache license 2.0 license that covers the project. Feel free to contact the maintainers if that's a concern.
+Engaging in discussions about the current state of the code, potential improvements, and innovative ideas are highly encouraged! 
+
+**Want to start a discussion?** [Create a new discussion](https://github.com/ChimeraCSS/ChimeraCSS/discussions/new/choose), choosing the category you want to discuss! 
 
-## Report bugs using Github's [issues](https://github.com/J0hans1/Chimera/issues)
+Here's some of our **Best Practices for Discussion:**
 
-We use GitHub issues to track public bugs. Report a bug by [opening a new issue](); it's that easy!
+- **Be Respectful:** Respect others' opinions and be open to feedback. We strive for a welcoming and inclusive environment.
+- **Stay On Topic:** Keep discussions focused on the technical aspects and how changes can improve the project.
+- **Provide Context:** When suggesting changes or highlighting issues, provide as much context as possible. Links to documentation, previous discussions, or examples can be incredibly helpful.
+- **Ask Questions:** Don’t hesitate to ask for clarification if something isn’t clear. Our community is here to help each other.
 
-## Use a Consistent Coding Style
+### Code Contribution 🤝
 
-- we use prettier formatting
+Before you dive in, here are some key points to ensure your contributions make a smooth landing:
 
-## License
+- **Coding Style:** We use Prettier for formatting. Ensure your code align with our style guide for consistency.
+- **SCSS over CSS:** Make your styling changes in `.scss` files, not `.css`. Remember to compile & build your SCSS changes with `sass sass/main.scss css/chimera.css`.
+- **Pull Requests:** Ready to submit your code? Open a pull request with a clear list of what you've done. The more detailed, the better!
 
-By contributing, you agree that your contributions will be licensed under its Apache License.
+### Proposing Features 💡
 
-## References
+Got an idea for a new feature? We're all ears!! Here's how to propose it:
 
-This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)
+1. **Check Existing Discussions:** Browse through our [Discussion board](https://github.com/ChimeraCSS/ChimeraCSS/discussions) and [Issues](https://github.com/ChimeraCSS/ChimeraCSS/issues) to see if your idea has been previously suggested or discussed.
+2. **Start with an Issue:** [Open a new issue](https://github.com/ChimeraCSS/ChimeraCSS/issues/new/choose) to discuss your idea. This allows for feedback and collaboration from the community.
+3. **Outline the Feature:** Provide a detailed explanation of the feature and its benefits.
 
-## NB! Remember!
+### Becoming a Maintainer 🧑‍🔧
 
-- Dont write the styling changes in the .css files, write them in .scss files
-- Remember to run `sass sass/main.scss css/chimera.css` to build the changes in sass/
+Interested in taking a more active role in Chimera? Maintainers are crucial to our project's health and growth. Reach out to us with your contributions and interest!
+
+## Any contributions you make will be under the Apache license 2.0
+
+In short, when you submit code changes, your submissions are understood to be under the same Apache license 2.0 license that covers the project. Feel free to contact the maintainers if that's a concern.