Merge pull request #144 from Vaibhav-Kulshreshtha7/docs/add-CONTRIBUTING-md

docs: add CONTRIBUTING.md with clear contribution guidelines

Author: lolpanda2004

CONTRIBUTING.md

@@ -0,0 +1,100 @@
+# Contributing to Amour Editorials 💜
+
+Thank you for your interest in contributing to **Amour Editorials**!  
+We welcome contributions from everyone — whether you’re a beginner or an experienced developer, designer, writer, or tester.
+
+
+## 📜 Code of Conduct
+
+This project follows our [Code of Conduct](CODE_OF_CONDUCT.md).  
+By participating, you agree to uphold these standards.  
+If you witness or experience unacceptable behavior, please report it to the maintainers.
+
+
+## 🚀 Ways to Contribute
+
+There are many ways to contribute:
+
+- 📃 Improve documentation
+
+- 🐞 Report or fix bugs
+
+- ✨ Add new features
+
+- 🎨 Improve UI/UX
+
+
+## 🛠 How to Contribute
+
+### 1. Fork the Repository
+Start by forking the repository to your GitHub account.
+
+### 2. Clone Your Fork
+Clone the repository to your local machine using:
+
+```bash
+$ git clone https://github.com/<your-username>/Amour-Editorial-Website.git
+```
+
+### 3. Create a New Branch
+Create a branch for your contribution:
+
+```bash
+$ git checkout -b <branch-name>
+```
+
+### 4. Make Your Changes
+Add new pages, new algorithms, improve documentation, or fix any issues. Be sure to:
+- Write clean, well-commented code
+- Ensure you don’t break existing features and that your solution is correct and efficient
+
+### 5. Commit Your Changes
+Commit your changes with a descriptive commit message:
+
+```bash
+$ git commit -m "Added [the changes]"
+```
+
+### 6. Push Your Fork
+Push your changes to your forked repository:
+
+```bash
+$ git push origin <branch-name>
+```
+
+### 7. Create a Pull Request
+Go to the original repo → New Pull Request.  
+Explain what you changed and why.
+
+
+## 📌 Contribution Guidelines
+
+- 🧹 Maintain code style & lint rules  
+- 🚫 Don’t break existing features  
+- 🧪 Write/modify tests (if applicable)  
+- 💬 Be clear in PR descriptions  
+- 🙌 Respect others and give constructive feedback  
+
+
+## 📚 Documentation
+
+Please update documentation when adding or modifying features:
+
+- Update `README.md` if necessary
+- Add inline comments for complex code
+
+
+## 💬 Communication
+If you have questions, suggestions, or need help:
+
+Start a discussion in the GitHub Discussions (if enabled).
+
+Open a new issue if you're facing a bug or want to propose an enhancement.
+
+For urgent matters, mention maintainers directly in your issue or PR using @maintainer-username.
+
+
+Stay respectful, constructive, and inclusive in all your interactions.
+---
+
+Thank you for your contributions! Together, we can build something amazing. ✨

README.md

@@ -149,61 +149,8 @@ Amour-Editorial-Website/
 
 ## 🤝 Contributing
 
-We welcome contributions from developers, designers, writers, and testers! 💜
-
-### How to Contribute
-
-1. **Fork** the repository  
-2. **Clone** to local  
-3. **Create a new branch** for your feature/bug  
-4. **Commit changes** with meaningful messages  
-5. **Push** and create a Pull Request 
-6. **Raise a issue**
-    We appreciate you taking the time to improve the project! Here’s how to raise an issue effectively:
-
-    **Check for Existing Issues**
-      -Browse through existing issues to avoid duplicates.
-
-    **Use a Clear Title**
-      -Make your title short but descriptive (e.g., "Navbar overlaps logo on mobile").
-
-    **Describe the Issue in Detail**
-      -Explain what the issue is and why it matters.
-      -Mention the expected behavior vs. actual behavior.
-      -Include steps to reproduce the problem (if it's a bug).
-
-    **Attach Relevant Media (if applicable)**
-      -Screenshots, GIFs, or terminal logs help speed up understanding.
-
-    **Use Appropriate Labels**
-      -Add labels like bug, feature, enhancement, good first issue, etc.
-
-    **Be Respectful and Constructive**
-      -Keep communication kind and focused on solutions.
-7. **Create a Pull Request**
-    Go to your forked repo on GitHub.
-    You'll see a prompt to "Compare & pull request".
-
-    Click it.
-
-    Fill in the PR title and description:
-    ✅ Title: docs: add contribution guidelines for issues and PRs
-    ✅ Description: Briefly explain what you did. 
-    Example:
-    This PR adds a new section to the README with clear steps on how contributors can raise issues and submit PRs, as requested in Issue #<issue-number>.
-
-    Submit the PR.
-8. **Comment on the Issue**
-    If the task was assigned via an Issue, comment something like:
-    I have created a PR that addresses this. Please review it here: [#PR-Link]
-
-### Contribution Guidelines
-
-- 🧹 Maintain code style & lint rules  
-- 🚫 Don’t break existing features  
-- 🧪 Write/modify tests (if applicable)  
-- 💬 Be clear in PR descriptions  
-- 🙌 Respect others and give constructive feedback  
+We welcome contributions to make EventStack even better!  
+Please read our [Contributing Guidelines](CONTRIBUTING.md) before submitting a pull request.
 
 ---