refactor(Splash): migrate component from SCSS to TailwindCSS#8099
refactor(Splash): migrate component from SCSS to TailwindCSS#8099shivam1608 wants to merge 3 commits intowebpack:mainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
rahul-kr-rai
left a comment
There was a problem hiding this comment.
Whole style and structure are looking different from webpack.js.org
You can see carefully from h2 spanning Install Webpack to Backers
4130da2 to
fed757f
Compare
|
@rahul-kr-rai mistakenly pushed the wrong playground files. |
Still, the problem is not solved. See the difference ( https://webpack-js-org-git-fork-shivam1608-refactor-splas-7c53bb-openjs.vercel.app/ and https://webpack.js.org/ ) Note: Please test and verify manually on localhost before committing. |
rahul-kr-rai
left a comment
There was a problem hiding this comment.
Why did you change the original text inside span below the sponsor h2.
Please fix it.
@rahul-kr-rai sorry i don't get you can you please specify the point because i only changed the style not any text |
Visit Here: https://webpack-js-org-git-fork-shivam1608-refactor-splas-7c53bb-openjs.vercel.app/ and https://webpack.js.org/ Note: See the difference carefully from Platinum Sponsors Please fix it. |
Summary
Migrates the
components/Splash.jsxcomponent from SCSSSplash.scssto Tailwind CSS utility classes.Part of #8047
What kind of change does this PR introduce?
refactor
Did you add tests for your changes?
No — this is a pure styling refactor with no logic changes. Visual output remains equivalent to the previous SCSS styles.
Does this PR introduce a breaking change?
No. The change is internal to the
components/Splash.jsxcomponent. No public API or component interface is affected.If relevant, what needs to be documented once your changes are merged or what have you already documented?
No documentation changes required.
Use of AI
Minimal use of gemini for utility classes