Repository Structure and Code Formatting Improvement

[muditkashyap]

This issue is raised to address the formatting and code structure concerns within the repository. The current organization of files and code is not following best practices, which can make it challenging for contributors and users to navigate and utilize the content effectively.

To improve the repository, we should consider the following actions:

Define Clear Structure: We need to define a clear and consistent structure for the repository. This includes organizing code files, examples, and assets into logical folders and subfolders.

Standardize File and Folder Names: Standardize the naming conventions for files and folders to make them more descriptive and easier to understand.

Remove Unnecessary Files: Identify and remove irrelevant files like .DS_Store and .giignore. Keep the repository clean and free from clutter.

Improve Code Formatting: Ensure that the code follows best practices and is well-structured. This includes proper indentation, comments, and documentation where necessary.

Add Contribution Guidelines: It's essential to have clear contribution guidelines for all contributors to follow. These guidelines should define how contributions should be formatted, named, and structured.

By addressing these issues, we can enhance the overall quality and usability of the repository. Please feel free to share your thoughts and suggestions on how we can achieve these improvements effectively. Your input is valuable in making this repository more accessible and user-friendly for all.

[muditkashyap]

@aayush105 I was having some important work in my office so was not able to do for 2 days, don't close this issue. I'll work tomorrow on this.

[aayush105]

@aayush105 I was having some important work in my office so was not able to do for 2 days, don't close this issue. I'll work tomorrow on this.

@muditkashyap Okay brother i will not close the issue. You can work in this issue in free time.