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

L4: Move all styling to Tailwind CSS #3

Open
bewildergeist opened this issue Feb 22, 2022 · 0 comments · May be fixed by #6
Open

L4: Move all styling to Tailwind CSS #3

bewildergeist opened this issue Feb 22, 2022 · 0 comments · May be fixed by #6

Comments

@bewildergeist
Copy link
Owner

bewildergeist commented Feb 22, 2022

Refactoring time! We're moving to Tailwind CSS for all our styling needs. So do the following:

  • Install and set up Tailwind as described in the Remix docs.
  • Install the official Tailwind extension for VS Code and be sure to configure the editor.quickSuggestions setting as described in the extension's README.
  • Methodically go through all components and replace the route-related stylesheets with Tailwind classes added directly inside your JSX files. If you find yourself repeating the same styling several places, consider extracting a new component.
  • Aim to replicate the existing styling from L4: Use Remix route styles for styling #2 as closely as possible.
  • When you are done, you should only be importing a tailwind.css file and have no other CSS files in your solution.
  • Answer this little questionnaire when you are done (or before you run out of time)

If you finish early:

@bewildergeist bewildergeist changed the title Move all styling to Tailwind CSS L4: Move all styling to Tailwind CSS Feb 22, 2022
@bewildergeist bewildergeist linked a pull request Feb 22, 2022 that will close this issue
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 a pull request may close this issue.

1 participant