Add Project Folder Structure to README for Better Contributor Clarity

[SanikaDahiwal0015]

Description:

The current README does not clearly explain the project folder structure. Because of this, new contributors sometimes add unnecessary or misplaced files, making the repository harder to navigate and maintain.

To improve clarity and consistency, we should add a dedicated Project Structure section in the README that explains the directory layout and purpose of each major folder.

Proposed Change:

Add a section in README.md like:

Clearly list main folders (app/, prisma/, public/, scripts/, etc.)
Briefly describe what each folder is used for
Include important files and their purpose (e.g., vite.config.ts, .env.example)
Add simple rules for contributors on where to place new code

Expected Outcome:
New contributors understand project structure immediately
Reduces creation of unnecessary or random files
Improves consistency in codebase organization
Makes onboarding faster and smoother

Additional Suggestion (Optional):

We can also add a small “Contributor Rules” note under this section to guide where code, components, and utilities should be placed.

[aryansaini101007-rgb]

Hi! I'd like to work on this issue under ECSoC 2026. I'll document the current project structure based on the actual repository, explain the purpose of the major directories and important files, and add concise contributor guidelines for where new code should be placed. Could you please assign it to me?
Thanks.

[github-actions]

Hi @aryansaini101007-rgb! 👋

Thank you for your interest in contributing to this repository! Please wait until a maintainer officially assigns you to this issue before opening a Pull Request.

While you wait, please consider starring ⭐ this repository to show your support! We review requests regularly and will assign it as soon as possible if it's available. Happy coding! 🚀

[kashyapanshu3108-ops]

hi! i am interested to solve this bug under ECSoC 2026. pls assign it to me ?

[SanikaDahiwal0015]

hello @rushikesh-bobade can you please assign this issue to me

[student-nitrr]

hello assigned it to me @SanikaDahiwal0015

[RitikaSen27]

Hi @SanikaDahiwal0015 , I'd like to take this on! I'll add a Project Structure section to the README covering the main folders (app/, prisma/, public/, scripts/, etc.) with a brief description of each, call out key files like vite.config.ts and .env.example, and include a short Contributor Rules note on where new code, components, and utilities should go. Pure docs change, no code touched. Can I get this assigned?

[Chinmay0904]

Hi! I'd like to work on this issue. Could you please assign it to me?

[rushikesh-bobade]

Hi everyone, thank you all so much for volunteering to help improve our documentation! 🙌

@SanikaDahiwal0015 Since you are the original author of this fantastic proposal, you have first dibs on implementing it!

However, following our contributor guidelines (one active issue per person), we cannot officially assign this new issue to you until your open Chatbot PR (#116) is fully merged. I'd love to see you push the requested fixes over there so we can get it shipped! Once that PR is merged, let me know here and I will officially assign this to you.

Please Note: To keep the project moving, we have a 7-day inactivity rule. If you are unable to finish your current PR and claim this issue within 7 days, the issue will be passed on to the next person in line.

@aryansaini101007-rgb You are officially second in line! If this issue becomes available after 7 days, it goes straight to you.

For everyone else (@kashyapanshu3108-ops @RitikaSen27 @Chinmay0904), thank you for stepping up! We have plenty of other exciting good first issue tickets open right now—please check the issues tab and grab one!

[SanikaDahiwal0015]

Thank you!
I've completed the requested updates for PR #116 and pushed the changes.
I'll wait for it to be reviewed and merged, then I'll come back here to claim this documentation issue.
I appreciate the opportunity!
Can you please assign this to me

[karrisanthoshigayatri]

Hi @rushikesh-bobade ,

I'd be happy to work on this issue if it becomes available.

Approach: I'll document the current project structure in the README, describe the purpose of each major directory and key configuration files, and add concise contributor guidelines to help maintain a clean and consistent project structure.

Thank you!