intail version for prdouction

Author: shadil-rayyan

docs/community.md/ contribution-guidelines.md

@@ -0,0 +1,199 @@
+
+# Contributing to Gecian Hub
+
+Thank you for your interest in contributing to **Gecian Hub** 🎉  
+This guide will help you contribute effectively — whether you're a beginner or experienced developer.
+
+---
+
+## 🧠 Before You Start
+
+Please make sure you:
+- Read the README of the repository
+- Understand the project goal
+- Follow the Community Guidelines
+
+If you are confused — **that’s normal**. Ask questions.
+
+---
+
+## 🧭 Ways to Contribute
+
+You can contribute in many ways:
+
+### 📝 Documentation
+- Fix typos or grammar
+- Improve clarity
+- Add missing sections
+- Write guides or tutorials
+
+### 💻 Code
+- Bug fixes
+- Feature improvements
+- UI/UX enhancements
+- Performance optimizations
+
+### 🐞 Issues
+- Report bugs
+- Suggest improvements
+- Discuss ideas
+
+### 🎨 Design & UX
+- Icons
+- Layout suggestions
+- Accessibility improvements
+
+---
+
+
+---
+
+## 🔁 Contribution Workflow (Step by Step)
+
+### 1️⃣ Fork the Repository
+Click the **Fork** button on GitHub.
+
+---
+
+### 2️⃣ Clone Your Fork
+```bash
+git clone https://github.com/<your-username>/<repo-name>.git
+cd <repo-name>
+````
+
+---
+
+### 3️⃣ Create a New Branch
+
+Never work directly on `main`.
+
+```bash
+git checkout -b feature/short-description
+```
+
+Examples:
+
+* `fix/navbar-bug`
+* `docs/add-install-guide`
+* `feature/project-search`
+
+---
+
+### 4️⃣ Make Your Changes
+
+* Keep changes focused
+* Follow existing code style
+* Add comments if needed
+
+---
+
+### 5️⃣ Commit Like a Pro
+
+Use **clear and meaningful commit messages**:
+
+```bash
+git commit -m "docs: improve contribution guide clarity"
+```
+
+Format:
+
+```
+type: short description
+```
+
+Examples:
+
+* `fix: resolve crash on login`
+* `feat: add project collaboration page`
+* `docs: update README`
+
+---
+
+### 6️⃣ Push Your Branch
+
+```bash
+git push origin feature/short-description
+```
+
+---
+
+### 7️⃣ Open a Pull Request (PR)
+
+When opening a PR:
+
+* Clearly explain **what** you changed
+* Explain **why** you changed it
+* Reference related issues if any
+
+Good PR description:
+
+> This PR improves documentation clarity for new contributors by adding examples and fixing grammar.
+
+---
+
+## ✅ Pull Request Rules
+
+Your PR should:
+
+* Be focused (one feature/fix per PR)
+* Not break existing functionality
+* Follow project structure
+* Pass any required checks
+
+Maintainers may:
+
+* Request changes
+* Suggest improvements
+* Ask questions
+
+This is normal — don’t take it personally.
+
+---
+
+## 🧪 Testing (If Applicable)
+
+Before submitting:
+
+* Test your changes locally
+* Ensure the app builds/runs
+* Check docs formatting
+
+---
+
+## 📌 Issue Guidelines
+
+When creating an issue:
+
+* Use a clear title
+* Describe the problem clearly
+* Add screenshots if possible
+* Mention steps to reproduce (for bugs)
+
+Avoid vague issues like:
+
+> “App not working”
+
+---
+
+## 🙋 Need Help?
+
+If you’re stuck:
+
+* Comment on the issue
+* Ask in discussions
+* Reach out to maintainers
+
+**Asking questions is encouraged.**
+
+---
+
+## 🏁 Final Words
+
+You don’t need to be perfect to contribute.
+You just need to be honest, respectful, and willing to learn.
+
+Every contribution — big or small — matters.
+
+Welcome to Gecian Hub 💙
+
+```

docs/community.md/community.md

@@ -0,0 +1,113 @@
+
+
+# 📜 COMMUNITY GUIDELINES
+
+👉 `COMMUNITY_GUIDELINES.md` or `docs/community/community-guidelines.md`
+
+```md
+# Community Guidelines – Gecian Hub
+
+Welcome to the **Gecian Hub community** 👋  
+This document outlines how we work together and what we expect from everyone participating in our GitHub organization.
+
+Gecian Hub exists to help students learn, collaborate, and grow through open source.  
+To make that possible, we value **respect, learning, and transparency** over perfection.
+
+---
+
+## 🌱 Our Core Values
+
+### 1. Learning Over Ego
+No one here is expected to know everything.
+- Beginners are welcome
+- Questions are encouraged
+- Mistakes are part of learning
+
+There is no place for superiority or gatekeeping.
+
+---
+
+### 2. Respect for Everyone
+We respect all contributors regardless of:
+- Branch or department
+- Experience level
+- Background or opinions
+
+Harassment, discrimination, or personal attacks will **not** be tolerated.
+
+---
+
+### 3. Transparency & Honesty
+- Decisions should be explained clearly
+- Credits should be given fairly
+- If something doesn’t work, we talk about it openly
+
+---
+
+### 4. Community Before Code
+Code matters — but people matter more.
+
+We prioritize:
+- Healthy collaboration
+- Constructive feedback
+- Long-term sustainability
+
+---
+
+## 🤝 Expected Behavior
+
+We expect all community members to:
+
+- Be polite and respectful in discussions
+- Give constructive and kind feedback
+- Accept feedback without hostility
+- Help others when possible
+- Follow repository rules and documentation
+
+---
+
+## 🚫 Unacceptable Behavior
+
+The following will **not** be accepted:
+
+- Harassment or hate speech
+- Personal attacks or insults
+- Spamming issues or pull requests
+- Stealing credit for others’ work
+- Forcing changes without discussion
+
+Repeated violations may result in removal from the organization.
+
+---
+
+## 🛠 Maintainers & Decision Making
+
+Maintainers are responsible for:
+- Reviewing pull requests
+- Managing issues
+- Guiding contributors
+
+Final decisions rest with maintainers, but:
+- Feedback is always welcome
+- Discussions are encouraged
+- Decisions should be explained
+
+---
+
+## 🆘 Reporting Issues
+
+If you experience or witness unacceptable behavior:
+- Reach out to a maintainer privately
+- Or open a confidential issue if applicable
+
+Your concerns will be taken seriously.
+
+---
+
+## ❤️ Final Note
+
+Gecian Hub is built **by students, for students**.  
+Be kind, be patient, and help make this a safe place to learn.
+
+Thank you for being part of the community.
+```