You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is some mismatch and inconsistency with how the website treats the Variation and Modifier sections. We should align on a way to clearly differentiate between the two. CDS suggested that the best way may be to audit all component pages to align the differences:
Hey Rich, we had a big audit/discussion on this several months ago on the team. The short story is that the team had to go through Storybook component-by-component and discuss what would be considered a variant. Anything that was considered to have a unique use case, require specialized documentation, or was significantly different in how it is built in code was leveled up to a variant. There were many other stories in our storybook that we decided were just a configuration of properties. The CDS website has not been cleaned up in regards to this audit, but we hope to do that soon. This is the audit of roughly where we are headed.
Currently there is some mismatch and inconsistency with how the website treats the
Variation
andModifier
sections. We should align on a way to clearly differentiate between the two. CDS suggested that the best way may be to audit all component pages to align the differences:https://ibm-studios.slack.com/archives/C03CY846LH3/p1695400598589859
The text was updated successfully, but these errors were encountered: