Fix Replace current CSS with tailwind CSS with gitauto model

[gitauto-ai]

Original issue: #35

What is the feature

Replace the current CSS with Tailwind CSS.

Why we need the feature

Switching to Tailwind CSS will streamline our styling process, reduce the amount of custom CSS we need to maintain, and provide a more consistent design system. Tailwind's utility-first approach allows for rapid UI development and easier maintenance.

How to implement and why

1. Install Tailwind CSS: Add Tailwind CSS to the project by installing it via npm or yarn.

   • This step is crucial to integrate Tailwind into our build process.

2. Configure Tailwind: Create a tailwind.config.js file to customize the default Tailwind configuration.

   • This allows us to tailor Tailwind to our project's specific needs.

3. Purge Unused CSS: Configure the purge option in tailwind.config.js to remove unused styles in production.

   • This step is important to keep the final CSS bundle size small.

4. Update Global Styles: Replace global styles in pages/landing.module.css with Tailwind utility classes.

   • This ensures that our global styles are consistent and maintainable.

5. Refactor Component Styles: Update the styles in pages/index.js and pages/landing.js to use Tailwind classes.

   • This step will convert our existing custom CSS to Tailwind's utility classes, simplifying the styling process.

6. Test the Changes: Thoroughly test the application to ensure that the new styles are applied correctly and that there are no regressions.

   • Testing is essential to verify that the transition to Tailwind CSS does not introduce any visual or functional issues.

Test these changes locally

git checkout -b gitauto/issue-#35-b83346e9-ded1-4d92-9795-c8da46df0afd
git pull origin gitauto/issue-#35-b83346e9-ded1-4d92-9795-c8da46df0afd