Create Reference Documentation for Component Reasoning - Githubissues

NCIOCPL / ncids

NCI Design System

7 stars 5 forks source link

Create Reference Documentation for Component Reasoning #1742

Open laurelthrash opened 3 weeks ago

laurelthrash commented 3 weeks ago

Description: During conversations for R3/MLPs, it was determined that it would be helpful to have documentation for the reasoning behind each proposed component. This will be used during conversations around scope to help determine which component to keep/cut/modify.

Sub-tasks:

[x] Create documentation for each proposed component (Adriana)
[x] Review internally (week of 06/17)
[x] Make edits (R3.2 - 06/26)
[x] Share internally w/POs (Adriana)
[x] Make edits - R3.3 (07/03)
[x] Make edits - R3.4
[ ] Make edits - R3.5
Review with federal team and use as part of scope conversations

laurelthrash commented 2 weeks ago

Mural board for the component glossary as way to present above information: https://app.mural.co/t/publicissapient7269/m/publicissapient7269/1718208797008/b6f1316c8de402b7d40ebd222170526d7652f31b?sender=uc8881d65820946a13d002641

laurelthrash commented 2 weeks ago

Notes from 06/18 conversation:

Goal of Mural: have reasoning behind each component, complement analytics findings, consider for education/documentation
Could consider using the Mural/information in the Mural for for education/documentation

Actions

[x] Call out on Mural board how components meet stakeholder or content needs/specific use cases (e.g., add call out or use bold)

Timeline

R3.2 portion revised by 06/25