Feat: Migrate UI framework from Semantic-UI to TailwindCSS V3 (Closes #648) #655
+6,794
−7,402
Conversation
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
Signed-off-by: Samrat Biswas <[email protected]>
Signed-off-by: Samrat Biswas <[email protected]>
Author
|
Plz Review the changes |
northdpole
reviewed
Dec 17, 2025
| > | ||
| <Link | ||
| to={getInternalUrl(usedNode)} | ||
| style={{ |
Collaborator
There was a problem hiding this comment.
sorry, I'm not a css pro, so please excuse the ignorance but isn't inline css considered bad practice and instead you should have classes etc?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 Pull Request addresses the need to modernize the OpenCRE frontend by migrating the styling framework from Semantic-UI to Tailwind CSS v3.
This change was initiated to leverage the benefits of a modern, actively maintained CSS framework, which offers better customization, design flexibility, and compatibility with modern React workflows, as discussed in the original issue.