Skip to content
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

Closed
GPortas opened this issue Mar 7, 2023 · 4 comments
Assignees
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

@GPortas
Copy link
Contributor

GPortas commented Mar 7, 2023

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:

  • There may be elements that, in addition to being used directly, also compound other larger elements that are also used in different places.
  • We must focus only on the components within the scope of the MVP functionalities
  • App-specific components that contain business logic should not be included

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):
image
Example molecule (a modal):
image

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?

  • MVP Strategy document: link
  • Frontend team meeting about initial contributions

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

@GPortas GPortas moved this to Re-arch: SPA MVP (Guillermo) in IQSS Dataverse Project Mar 7, 2023
@GPortas GPortas added MVP Milestone 2 MVP Milestone 2: Add a Dataset D: Design System Deliverable: Design System labels Mar 7, 2023
@GPortas GPortas changed the title Identify the atomic UI elements of Dataverse and create issues for their development Identify UI elements for the Dataverse Design System and create issues for their development Mar 13, 2023
@GPortas GPortas added the Size: 30 A percentage of a sprint. 21 hours. (formerly size:33) label Mar 14, 2023
@MellyGray MellyGray self-assigned this Mar 16, 2023
@mreekie mreekie added the pm.GREI-d-1.7.1 NIH, yr1, aim7, task1: Research & architecture for separating backend and frontend label Mar 20, 2023
@GPortas GPortas moved this from Re-arch: SPA MVP (Guillermo) to Clear of the Backlog in IQSS Dataverse Project Mar 27, 2023
@MellyGray MellyGray added Size: 3 A percentage of a sprint. 2.1 hours. Size: 10 A percentage of a sprint. 7 hours. and removed Size: 30 A percentage of a sprint. 21 hours. (formerly size:33) Size: 3 A percentage of a sprint. 2.1 hours. labels Mar 29, 2023
@mreekie
Copy link

mreekie commented Mar 29, 2023

next sprint:

  • dropped to 10 from 33 for thsi sprint

@MellyGray
Copy link
Contributor

@mreekie mreekie added 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 and removed pm.GREI-d-1.7.1 NIH, yr1, aim7, task1: Research & architecture for separating backend and frontend NIH OTA: 1.7.1 (reArchitecture) labels Apr 10, 2023
@pdurbin pdurbin assigned pdurbin and unassigned MellyGray Apr 11, 2023
@pdurbin
Copy link
Member

pdurbin commented Apr 11, 2023

I reviewed the doc and I'm ready to close this but @ekraffmiller should have an opportunity to take a look.

@pdurbin pdurbin assigned ekraffmiller and unassigned pdurbin Apr 12, 2023
@mreekie
Copy link

mreekie commented Apr 12, 2023

sprint:

  • based on what's left. just a few quesitions.size 3

@mreekie mreekie added Size: 3 A percentage of a sprint. 2.1 hours. and removed Size: 10 A percentage of a sprint. 7 hours. labels Apr 12, 2023
@kcondon kcondon self-assigned this Apr 13, 2023
@kcondon kcondon closed this as completed Apr 13, 2023
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.
Projects
Status: No status
Development

No branches or pull requests

6 participants