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

Added Tailwind #456

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Added Tailwind #456

wants to merge 3 commits into from

Conversation

jeromehardaway
Copy link
Contributor

@jeromehardaway jeromehardaway commented Mar 27, 2023

Change

🤖 Generated by Copilot at 76989fd

Summary

🎨🛠️🚚

This pull request introduces tailwindcss as a new CSS framework for the project, replacing Bootstrap and inline styles. It adds the necessary dependencies, configuration files, and tailwindcss classes to the package.json, postcss.config.js, globals.css, index.css, Header.js, Layout.js, and _app.js files.

Sing, O Muse, of the skillful coder who changed the style
Of his project's web pages with postcss and tailwindcss
He created a config file and a global file, importing them with care
And replaced the old classes with new ones, like a sculptor shaping clay

Walkthrough

  • Add autoprefixer, postcss, and tailwindcss packages as dependencies for cross-browser support and UI design (link, link)
  • Create and configure postcss.config.js file to use tailwindcss and autoprefixer plugins (link)
  • Create globals.css file to import base, components, and utilities styles from tailwindcss (link)
  • Import globals.css file in index.css, Layout.js, and _app.js files to ensure tailwindcss styles are available for the project (link, link, link)
  • Modify Header component to use tailwindcss classes instead of inline styles and Bootstrap classes (link)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@vercel
Copy link

vercel bot commented Mar 27, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated
vets-who-code-app ✅ Ready (Inspect) Visit Preview 💬 Add your feedback Mar 27, 2023 at 2:42AM (UTC)

@jeromehardaway
Copy link
Contributor Author

DO NOT MERGE.

Messes Up Some Styles As we convert things over.

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

Successfully merging this pull request may close these issues.

None yet

1 participant