Repository navigation
Replies: 51 comments 35 replies
|
External |
Avatar
|
|
Status indicators can be done with Randomized color is consumer inplemented. |
|
The randomized color is not easily applied in it's current form.
Maybe we suggest they only change background color using that variable and to make sure color contrast is met without changing the foreground colors. Otherwise #1887 does seem more important. |
|
We can deem the "randomized color" as unsupported for now. This effort is tied to #1846, where the proposal is to generate a unique pattern (image) based on the user's name. This image can be paired with new color tokens that designers are currently exploring. |
AvatarGroup
|
Badge
|
Blockquote
Use native |
Breadcrumbs
|
Button
|
|
Missing split button which it looks like we have an example of using a |
|
We should consider adding a "split button" example to |
ButtonGroup
|
|
Can we just use Isn't overflow just a MUI button group supports orientation="vertical" |
Carousel
Carousel is discouraged, but can be consumer implemented using StrataKit components. |
Checkbox
|
|
I would break out default and visibility into two different items so they can be tracked independently. Default should be consumer implemented. The existing example is just using state and logic to control the values of |
|
separated into 2 rows. default variant is out of the box support, but the visibility variant is still not supported atm. Loading I'm guessing is consumer implemented. |
CodeUse |
Color picker
|
|
Linking to #868 where |
|
Composite |
Combobox
|
|
Would recommend |
Date picker
|
|
Localization should already be supported both for date formats as well as UI text. |
Side navigation
|
|
We want to do away with the "submenu" pattern, which is intentionally not supported by |
Would the recommended action be to move all the menu content into its own page, or something else? For all of the other unsupported options it was a visual change, and the functionality was still there. This is impacting functionality. Just removing the submenu without an alternative seems like a significant risk that some of the apps functionality would be inaccessible. |
|
Yes, the secondary ("sub") links should be moved out of the side navigation and displayed through other means. The StrataKit |
Skip to content link
|
|
This is worth an example since it is more than just |
|
Composite skip link example+guidance added in #1917. Uses a visually-hidden-until-focused |
Slider
|
Stepper
|
TableUse a 3rd party package such as Tanstack Table. |
|
MUI Grid will also have upcoming support. |
Tabs
|
|
MUI already supports orientation="vertical" Sublabel can use |
|
isMuted on the text component is something I find myself often having to restyle in stratakit text |
|
@arome |
Tile
|
|
Selected - Card supports Avatar - Can have Avatar with large size as child of CardMedia with custom styling to center it. Folder - Can just use regular card format with Folder media image. |
|
For "selected Cards", we should add an example similar to radio tiles. We can place a Might need "corner elements" support, which was also requested in #1535. |
Toast
|
Tooltip
|
Transfer list
|
Tree |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We need to review and validate all iTwinUI components and their features against the StrataKit design system. This will ensure easy migration from iTwinUI to StrataKit for consumers. The results of this discussion will show up in #1908.
💬 Discussion Guidelines
To keep this audit organized, please follow these rules:
iTwinUI components
All reactions