Create tooltips of the design system #37
Labels
D: Design System
Deliverable: Design System
MVP Milestone 2
MVP Milestone 2: Add a Dataset
pm.GREI-d-2.7.1
NIH, yr2, aim7, task1: R&D UI modules for creating datasets and supporting publishing workflows
pm.GREI-d-2.7.2
NIH, yr2, aim7, task2: Implement UI modules for creating datasets and publishing workflows
Size: 30
A percentage of a sprint. 21 hours. (formerly size:33)
Overview of the Feature Request
We would like to add the tooltips elements of our design system as React components and document them in Storybook. This will make it easier for developers to use and maintain consistent tooltips elements across our applications.
The tooltips elements would be the ones documented in the Design System Analysis document.
These tooltips elements would be using the Design tokens as SASS variables if applicable. These variables are described in the document
What kind of user is the feature intended for?
This feature is intended for developers who use React to build and test components for our web applications.
What inspired the request?
Our design system includes a set of tooltips elements that are used consistently across our applications. By creating reusable React components for these elements and documenting them in Storybook, we can provide a centralized and easy-to-use reference for developers.
Some references for the Storybook:
What existing behavior do you want changed?
We want to add a new section to Storybook that displays our tooltips elements as React components. This section should include documentation on how to use each component, as well as examples of how the components can be customized.
Any brand new behavior do you want to add to Dataverse?
No, this feature request does not introduce any brand new behavior to Dataverse.
Any open or closed issues related to this feature request?
Identify UI elements for the Dataverse Design System and create issues for their development #14
Create the design tokens of the design system using SASS variables #30
The text was updated successfully, but these errors were encountered: