Is your feature request related to a problem? Please describe.
Tailwind 1.0 was released during the implementation of the new Lansing Codes website and has since seen a Tailwind 2.0 release.
As new utility classes and features are added to Tailwind, the Lansing Codes site will not be able to use these features until a migration from Tailwind 0.7.4 to Tailwind 2.x is performed.
Before and after screenshots of the whole website on mobile and desktop may be useful for verifying the upgrade was implemented completely.
It's okay to submit the upgrades to Tailwind 1 and Tailwind 2 as two separate pull requests. Do not close this issue until the upgrade to Tailwind 2 is complete though.
Is your feature request related to a problem? Please describe.
Tailwind 1.0 was released during the implementation of the new Lansing Codes website and has since seen a Tailwind 2.0 release.
As new utility classes and features are added to Tailwind, the Lansing Codes site will not be able to use these features until a migration from Tailwind 0.7.4 to Tailwind 2.x is performed.
Describe the solution you'd like
First, upgrade to Tailwind 1.x using the Tailwind 1.0 Migration Guide. Once that is complete and verified, upgrade to Tailwind 2.x using the Tailwind 2.0 Migration Guide.
Before and after screenshots of the whole website on mobile and desktop may be useful for verifying the upgrade was implemented completely.
It's okay to submit the upgrades to Tailwind 1 and Tailwind 2 as two separate pull requests. Do not close this issue until the upgrade to Tailwind 2 is complete though.