🚀 Refactor: Code Modularisation

[Sarthak2601]

🔖 Feature description

This issue suggests a refactoring effort aimed at improving the codebase by breaking it down into smaller components.

Note: I'm using the issue template for feature requests since there's no template for refactoring and also because this is neither a bug nor a documentation fix.

🎤 Pitch

By breaking down the code into smaller and more manageable components, we can enhance the readability and maintainability of the codebase. This refactor will not only make the code more approachable for new contributors but also improve the overall understanding and navigation of the project. It will also lead to optimisation since we can reuse these small components at multiple places.

For example: we can break down most of the component files into smaller components. I've created a follow up PR(#7) for the footer component. If it gets approved, we can probably create a common issue that covers file-by-file refactoring of multiple files using a check list.

PS: I'd like to work on this and follow up issue(s).

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[Sarthak2601]

Hi @christyjacob4 @loks0n @Meldiron, could you please take a look at this and the follow up PR -- thanks!

[loks0n]

Hey @Sarthak2601 👋
Thanks for raising this 🎉

I've responded to your PR. For the broader issue of code modularisation - this is definitely something that can be improved throughout the codebase, but I don't think the Footer is a good candidate for that.

[Sarthak2601]

Thanks for your response @loks0n! Is there any specific part of the codebase that you'd recommend I begin looking into?