Implement a basic CI/CD pipeline to ensure code quality assurance.

[Jarmos-san]

Having a CI/CD pipeline in place will ensure all PRs & code pushed to the remote repository abides by standard coding practices. At some point in time the pipeline can also be extended to run an automated test suite and/or build-deploy the website after a series of checks. The checks might or mightn't contain:

• Linting checks using ESLint
• Formatting the source code by Prettier
• Running the test suites
• If all of the above passes build & deploy the website to production

The pipeline can made even more complicated if the need arises but to start with a minimal & basic template should be in-place. This issue will track the implementation of that basic CI/CD pipeline template.