redesign: replace Bootstrap with TailwindCSS#3126
Draft
Soxasora wants to merge 5 commits into
Draft
Conversation
…d.css; move katex out of globals.scss to avoid tailwind re-tokenization
… alongside data-bs-theme
- bs-tw-map - bootstrap to tailwind utility codemod - bs-utility-check - bootstrap utility leftover checker - bs-tw-map - bootstrap to tailwind token map
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR:
Bootstrap is an amazing library that still serves a good fraction of the web, but its development has slowed in recent years. Its team is working hard on version 6, but compared to how fast the rest of the web is moving, it feels like it's lagging behind.
Tailwind gives us updated utilities and, more importantly, a powerful platform for our redesign.
This migration supports mixing Tailwind with CSS modules: Tailwind utility classes have the most important CSS layer, they always win over unlayered (even with
!important) bootstrap utilities and CSS modules.Up next:
Screenshots
Stacker News homepage rendered with Tailwind utility classes
Additional Context
This PR only removes the usage of Bootstrap(css classes, where possible) and introduces the Tailwind fundamentals to create our own UI components with Base-UI.
Bootstrap still coexists with Tailwind until all the tokens and css modules have been adjusted.
postcss-preset-envis used (maybe temporarily) to restore Next.js postcss defaults and smooth the transition.Checklist
Are your changes backward compatible? Please answer below:
For example, a change is not backward compatible if you removed a GraphQL field or dropped a database column.
On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:
For frontend changes: Tested on mobile, light and dark mode? Please answer below:
Did you introduce any new environment variables? If so, call them out explicitly here:
Did you use AI for this? If so, how much did it assist you?
Yes, for codemods and bootstrap compatibility layer