Customize OpenMCT UI with crazy styles #8059
Open
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.
Closes
Describe your changes:
This PR introduces creative UI changes and improvements, focusing on vibrant and dynamic visual effects for a more engaging user experience in Open MCT.
Key Changes:
Bold animations: Various UI elements now have smooth, engaging animation transitions, including rotating, flipping, and sliding effects that make the interface more visually dynamic.
Enhanced styles: The design has been updated with bright colors, vivid gradients, and hover effects to create a fun and energetic look, without altering the original class names.
Backgrounds, icons, and buttons have been tweaked to add a modern and interactive feel.
Improved message and alert components: New vibrant styles for message popups and alerts for better user interaction.
These changes are intended to revitalize the interface with a unique and bold aesthetic while maintaining its functionality.
All Submissions:
Have you followed the guidelines in our Contributing document?
Have you checked to ensure there aren't other open Pull Requests for the same update/change?
Is this a notable change that will require a special callout in the release notes? For example, will this break compatibility with existing APIs or projects that consume these plugins?
Author Checklist
Changes address original issue?
Tests included and/or updated with changes?
Has this been smoke tested?
Have you associated this PR with a type: label? Note: this is not necessarily the same as the original issue.
Have you associated a milestone with this PR? Note: leave blank if unsure.
Testing instructions included in associated issue OR is this a dependency/testcase change?
Reviewer Checklist
Changes appear to address issue?
Reviewer has tested changes by following the provided instructions?
Changes appear not to be breaking changes?
Appropriate automated tests included?
Code style and in-line documentation are appropriate?