Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitAuto: Replace current CSS with tailwind CSS #49

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

gitauto-for-dev[bot]
Copy link
Contributor

Resolves #35

What is the feature

The feature involves replacing the current CSS styling with Tailwind CSS in the project.

Why we need the feature

Tailwind CSS is a utility-first CSS framework that provides low-level utility classes to build custom designs without leaving the HTML. It can significantly reduce the amount of custom CSS we need to write, improve consistency across the application, and make it easier to maintain and scale the design system.

How to implement and why

  1. Install Tailwind CSS:

    • Add Tailwind CSS to the project using npm or yarn. This will allow us to use Tailwind's utility classes in our HTML files.
  2. Configure Tailwind:

    • Create a tailwind.config.js file to customize the default configuration. This step is crucial to extend or override the default Tailwind settings to fit our design requirements.
  3. Remove Existing CSS:

    • Identify and remove existing CSS files that are no longer needed. This will help in reducing redundancy and potential conflicts between Tailwind and existing styles.
  4. Refactor HTML Files:

    • Update the HTML files in the pages directory to use Tailwind's utility classes. This involves replacing existing class names with Tailwind's utility classes to achieve the same or improved styling.
  5. Test the Application:

    • Thoroughly test the application to ensure that the new styles are applied correctly and that there are no visual regressions.
  6. Optimize for Production:

    • Use Tailwind's built-in PurgeCSS to remove unused CSS in production builds, which will help in keeping the CSS bundle size small.

About backward compatibility

Backward compatibility is not a concern in this case as the change is purely related to styling. However, we need to ensure that the visual appearance remains consistent with the previous design to avoid any disruption to the user experience.

Test these changes locally

git checkout -b gitauto-wes/issue-#35-4967f562-b607-4b91-be38-481d95eebe8e
git pull origin gitauto-wes/issue-#35-4967f562-b607-4b91-be38-481d95eebe8e

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Replace current CSS with tailwind CSS
0 participants