Currently ARES UI is a mishmash of various UI components and styles. Some styles are acquired from the Radzen component library, some styles are used from the Darkly css library, some from just plain old css, and there's also bootstrap. The styling also varies from page to page and does not have a cohesive language. This is also prevalent when adding new pages with the help of AI with no style guidance and steering.
I'd like to see a set of ARES visual components along with a common style guide that provides color guidance and maybe variables. Right now for variables we do use --rz ones coming from Radzen, but that is also rather inconsistent. We could continue using Radzen for graph support, but I'd like to see more ARES specific ones, especially if we can leverage the power of the "optimizers" to help speed the process.
Currently ARES UI is a mishmash of various UI components and styles. Some styles are acquired from the Radzen component library, some styles are used from the Darkly css library, some from just plain old css, and there's also bootstrap. The styling also varies from page to page and does not have a cohesive language. This is also prevalent when adding new pages with the help of AI with no style guidance and steering.
I'd like to see a set of ARES visual components along with a common style guide that provides color guidance and maybe variables. Right now for variables we do use --rz ones coming from Radzen, but that is also rather inconsistent. We could continue using Radzen for graph support, but I'd like to see more ARES specific ones, especially if we can leverage the power of the "optimizers" to help speed the process.