feat: remove css from various pages/Template.* pages
#21267
Draft
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.
This attempts to remove all of the MUI/
@emotionbasedcssprops. Moving onto thepages/Templatesfolders. This should serve to align ourselves better with Tailwind/shadcn and our goal to remove mui from the database.I've made attempts to ensure the
line-heightis consistent, however this isn't always in best-practice with Tailwind in some cases. Minor pixel shifts may happen. There are around 9 or so components living incomponents/I haven't updated yet as the logic was scarier to migrate away from MUI.Note
This pull-request is a fork-out of #21154 as I found it was getting too big to merge and hard to understand. Alongside this various components were being misrepresented in Chromatic (despite rendering fine in Storybook). I felt it better to make this a set of PRs.
Chromatic Link / Chromatic Tests
cssfrom variouscomponents/elementscssfrom variouspages/Template.*pages