-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Identify UI elements for the Dataverse Design System and create issues for their development #14
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: 3
A percentage of a sprint. 2.1 hours.
Comments
This was referenced Mar 23, 2023
next sprint:
|
Analysis doc to be reviewed: https://docs.google.com/document/d/1OxCQO7B-yJaMWRl8EzuflcSmIaCmVSs19aoD83PjPmA/edit#heading=h.3opjq01zzxnw |
I reviewed the doc and I'm ready to close this but @ekraffmiller should have an opportunity to take a look. |
sprint:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: 3
A percentage of a sprint. 2.1 hours.
Overview of the Feature Request
For the development of the different Dataverse functionalities, we need to identify the common UI primitives shared across the application, such as generic buttons, text fields, etc, that will be part of the Dataverse Design System.
Since the Dataverse UI is already developed in JSF and there is already documentation related to this topic (https://guides.dataverse.org/en/latest/style/patterns.html), the ultimate goal of this issue is to analyze the existing UI and resources to identify and create issues corresponding to the implementation of the different UI elements.
Considerations:
Design system elements don't need to be atoms they can also be molecules as long as they are not business specific


Example atom (a button):
Example molecule (a modal):
A part from that, we'll use this issue to think about UI components documentation Guidelines. Using for example the Storybook docs capabilities
What kind of user is the feature intended for?
Dataverse frontend developers
What inspired the request?
What existing behavior do you want changed?
N/A
Any brand new behavior do you want to add to Dataverse Frontend?
N/A
Any related open or closed issues to this feature request?
N/A
The text was updated successfully, but these errors were encountered: