Skip to content

Epic: Review file tree and update MUI Components #1617

@JackHaeg

Description

@JackHaeg

Overview

Currently, components throughout the VRMS app do not match - some use MUI styling while others do not, thus creating a fractured user experience. All components throughout the VRMS file tree below must be updated to Material-UI components.

What if we're unable to access the component listed?

Do your best to change the HTML elements out anyway and note in the PR that you're unable to get the component to render within VRMS for screenshots.

Should I try to match the CSS of the app beforehand?

No, there will be some changes to the look and feel of the app switching to MUI components, we plan on going back in a second set of issues to match the CSS to our current figma design or a new figma design as it comes available. That said if functionality suffers based on MUI changes, please try to match the styling to maintain functionality (e.g., if a button previously was outlined on VRMS, then please implement an outlined MUI button).

Action Items

Check off these items when we have fully moved from standard HTML components to MUI components (note that same may already be updated to MUI). Each can be broken into its own issue.

Resources/Instructions

https://mui.com/base-ui/all-components/

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Epic Issues

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions