[DOCS] Add Project Documentation Under `docs/`

[HarshYadav152]

The project needs structured documentation to improve contributor onboarding, project understanding, and development workflow.

This issue focuses on creating and organizing documentation files inside the docs/ directory.

---

Tasks

• Create a docs/ directory
• Add setup and installation documentation
• Add project architecture overview
• Add API/authentication documentation (if applicable)
• Add contribution guidelines
• Add folder structure explanation
• Add deployment instructions
• Improve formatting and readability

---

Suggested Documentation Structure

docs/
├── installation.md
├── architecture.md
├── contribution-guide.md
├── deployment.md
├── api.md
└── folder-structure.md

---

Requirements

• Documentation should be beginner-friendly
• Use proper Markdown formatting
• Include code snippets/examples where necessary
• Maintain consistent headings and structure
• Ensure all information is accurate and updated

---

Acceptance Criteria

• All documentation files are added under docs/
• Markdown files are properly formatted
• Instructions are clear and easy to follow
• Documentation matches the current project structure
• No broken links or outdated information

---

[samalbishnupriya06-stack]

Subject: Expression of Interest: Documentation Restructuring and Setup

Hello @HarshYadav152 sir,
I am writing to express my strong interest in taking on the issue regarding the creation and organization of the project’s documentation.

I understand how critical clear, structured documentation is for a smooth contributor onboarding experience and overall project maintainability. I am confident that I can deliver a comprehensive and beginner-friendly documentation suite that aligns with the project’s goals.

I plan to execute the task by:

• Implementing the proposed structure: Creating the docs/ directory and populating it with the requested files (installation.md, architecture.md, contribution-guide.md, etc.).
• Ensuring clarity: Providing easy-to-follow, step-by-step instructions with accurate code snippets and examples to facilitate a low barrier to entry for new contributors.
• Prioritizing readability: Utilizing clean Markdown formatting, consistent header hierarchies, and well-organized folder explanations to ensure the technical information is accessible and easy to navigate.

I have reviewed the acceptance criteria and am fully prepared to ensure that all documentation is accurate, up-to-date, and free of broken links.

Could you please assign this issue to me? I am ready to begin immediately and would be happy to discuss any specific preferences or stylistic guidelines you would like me to follow.

[HarshYadav152]

@samalbishnupriya06-stack Go ahead.
I will assign this issue to you under ELUSoC 2026.