added more file to teh docs

Author: shadil-rayyan

docs/faq/contributors.md

@@ -0,0 +1,136 @@
+
+
+# ❓ Contributor FAQ — Gecian Hub
+
+## 1. Who can contribute to Gecian Hub?
+
+In general, **any student interested in learning and contributing is welcome**.
+
+However, some contributions—especially those related to **college-specific data, workflows, or internal coordination**—may be limited to **students of the host college** (e.g., GEC SKP) to ensure accuracy, safety, and accountability.
+
+This distinction will always be **clearly mentioned in the issue description**.
+
+---
+
+## 2. Is Gecian Hub restricted only to students of the host college?
+
+No.
+Gecian Hub follows an **open and learning-friendly approach**.
+
+* **Open issues** → Anyone can contribute
+* **College-specific issues** → Restricted to host college students
+
+This model ensures both **openness** and **responsible development**.
+
+---
+
+## 3. Do I need prior experience to contribute?
+
+No prior experience is required.
+
+Gecian Hub is designed as a **beginner-friendly project**, making it an excellent starting point for:
+
+* First-time contributors
+* Students new to GitHub
+* Those learning open-source workflows
+
+Guidance and reviews are provided where possible.
+
+---
+
+## 4. How difficult are the tasks compared to large open-source projects?
+
+Most tasks in Gecian Hub are **significantly simpler** than those in large or well-established open-source organizations.
+
+The project is intentionally structured to:
+
+* Reduce complexity
+* Encourage learning
+* Provide confidence through small wins
+
+It serves as a **stepping stone** before contributing to larger open-source projects.
+
+---
+
+## 5. Are there advanced or restricted issues?
+
+Yes. Some issues may:
+
+* Require access to internal systems
+* Involve real student data
+* Affect live deployments
+* Need on-campus coordination
+
+Such issues are usually:
+
+* Marked clearly
+* Assigned to **core team members or host college students**
+* Not suitable for first-time contributors
+
+---
+
+## 6. How will I know which issues I can work on?
+
+Each issue will clearly mention:
+
+* Skill level (beginner / intermediate)
+* Whether it is **open to all contributors**
+* Whether it is **restricted to host college students**
+
+If unsure, always **comment on the issue and ask** before starting work.
+
+---
+
+## 7. Can contributors from other colleges join the core team?
+
+Core team membership generally prioritizes:
+
+* Availability
+* Long-term commitment
+* Understanding of the host college environment
+
+Students from other colleges may contribute regularly, but **core leadership roles are usually reserved for host college students** to ensure continuity and accountability.
+
+---
+
+## 8. Will contributors receive mentorship or guidance?
+
+Yes, where possible.
+
+* Maintainers review Pull Requests
+* Feedback is provided constructively
+* Learning is encouraged over perfection
+
+However, contributors are expected to:
+
+* Read documentation
+* Follow contribution guidelines
+* Respect maintainers’ time
+
+---
+
+## 9. What is expected from contributors?
+
+Contributors should:
+
+* Follow GitHub best practices
+* Communicate respectfully
+* Complete tasks they take responsibility for
+* Avoid submitting incomplete or rushed PRs
+
+Quality matters more than quantity.
+
+---
+
+## 10. Can I use my contributions for learning or resumes?
+
+Yes.
+Contributions to Gecian Hub are:
+
+* Public
+* Open-source
+* Valid learning experience
+
+You are encouraged to showcase your work responsibly.
+
+---

docs/faq/general.md

@@ -0,0 +1,172 @@
+
+# ❓ General FAQ — Gecian Hub
+
+## 1. What is Gecian Hub?
+
+Gecian Hub is a student-first platform built to solve real problems faced in daily college life.
+It focuses on accessibility, simplicity, collaboration, and ethical use of technology to support students across departments and years.
+
+---
+
+## 2. Who runs Gecian Hub?
+
+Gecian Hub is run by a **student core team** under a designated **Project Lead (Head)**.
+Leadership may change over time through a documented succession process to ensure continuity.
+
+---
+
+## 3. Is Gecian Hub an official college project?
+
+Gecian Hub is a **student-led initiative**.
+While it may collaborate with departments or faculty when required, it operates independently unless explicitly stated otherwise.
+
+---
+
+## 4. Who can use Gecian Hub?
+
+All students are welcome to use Gecian Hub, regardless of:
+
+* Department
+* Year of study
+* Technical background
+
+Some features may be limited to verified students to ensure safety and trust.
+
+---
+
+## 5. Is Gecian Hub free to use?
+
+Yes.
+Gecian Hub is **free for students** and is not built for profit.
+
+---
+
+## 6. Who can contribute to the project?
+
+Anyone interested in contributing can do so, including:
+
+* Developers
+* Designers
+* Writers
+* Testers
+* Documentation contributors
+
+Technical knowledge is helpful but **not mandatory** for all contributions.
+
+---
+
+## 7. How do I start contributing?
+
+Start by:
+
+1. Reading the **Contribution Guidelines**
+2. Checking open GitHub issues
+3. Commenting on an issue before starting work
+4. Submitting a Pull Request (PR)
+
+All contributions follow open-source best practices.
+
+---
+
+## 8. Do I need to be an expert in Git or programming?
+
+No.
+However, **core team members and leads** are expected to understand:
+
+* Creating GitHub issues
+* Working with branches
+* Submitting and reviewing PRs
+* Basic open-source workflows
+
+Beginners are encouraged to learn and grow.
+
+---
+
+## 9. How are decisions made?
+
+Decisions are made through:
+
+* Discussion within the core team
+* Technical review when required
+* Final responsibility resting with the Project Lead
+
+All decisions should prioritize the project’s long-term health and student benefit.
+
+---
+
+## 10. Is the platform politically or ideologically affiliated?
+
+No.
+Gecian Hub maintains a **politically neutral stance** and avoids promoting ideological, religious, or controversial agendas.
+
+---
+
+## 11. What kind of content is not allowed?
+
+Content that is:
+
+* Harmful, offensive, or discriminatory
+* Politically provocative
+* Culturally insensitive or indecent
+* Violates privacy or ethical standards
+
+The platform aims to maintain a **safe and respectful environment**.
+
+---
+
+## 12. How is user data handled?
+
+User data is handled responsibly and minimally.
+We do not misuse personal data, and access is restricted to authorized maintainers only.
+
+Refer to the **Privacy Policy** for details.
+
+---
+
+## 13. What happens if something breaks or the site goes down?
+
+The project follows a documented **Incident Response & Recovery process** to:
+
+* Identify the issue
+* Minimize impact
+* Restore services safely
+
+Lessons learned are documented to prevent repetition.
+
+---
+
+## 14. What happens if leadership becomes inactive?
+
+If leadership succession fails, the project may be responsibly restarted following the **Succession Failure & Project Continuity Protocol**, ensuring the original mission continues.
+
+---
+
+## 15. How can I contact the team?
+
+* Official communication channels (email, forms, or GitHub)
+* For succession or continuity matters, previous leads may be contacted if necessary
+
+Avoid direct personal messages unless requested.
+
+---
+
+## 16. Where can I report issues or suggest features?
+
+* GitHub Issues (preferred)
+* Official feedback forms if available
+
+Clear, constructive reports help the project improve faster.
+
+---
+
+## 17. Can this project be forked or reused?
+
+Yes, under the project’s open-source license.
+However, forks should respect:
+
+* Ethical guidelines
+* Attribution requirements
+* Community responsibility
+
+---
+