[Feature] Organise code with proper indentation and comments

[Xaid-vfx]

Problem

The current code in the repository is not well defined, organized, or commented

Description

• [x] organize the code structure in accordance with standard rules and indentation
  • #258
• [ ] include comments to aid future contributors in understanding the function of each segment of code

For example: This is the current code: The above code looks messy.

The organized code:

Implementation

• [x] I would be interested in implementing this feature.

[Xaid-vfx]

@possumbilities could you check this out?

[possumbilities]

@Xaid-vfx I think this helps in a lot of ways to make the code clearer. Nice idea! ❤️

[Xaid-vfx]

@possumbilities Started working 🚀

[Xaid-vfx]

@possumbilities Can I organize all the files in the repo? or would that be considered too big for issue?

[BalrajDhakad]

may I start working on it

[BalrajDhakad]

Hey, I am willing to work on this issue, can you guide me to the first issue

[BalrajDhakad]

Can I start working on this issue @Xaid-vfx

[Karan-Palan]

Hello, @possumbilities ! I noticed PR #106 , which contains a substantial amount of work. However, it appears to have been marked as a draft last year. I'm interested in contributing to this issue.

[Peacesandy]

Hi! I'm interested in working on this project

[TimidRobot]

Please see Contribution Guidelines — Creative Commons Open Source for how we manage issues and PRs.

We generally don't assign issues prior to resolution. Instead of asking for issues to be assigned, do the work and submit a pull request (PR). Even if multiple people submit PRs for the same issue, multiple ideas and implementations strengthen the final product.

For work program applicants, each can all list their own PRs on their application. It is the quality of work that is important, not whether it is merged.