More definition is required for this story - suggestion from Bryan during internal conversation.
Build an NCIDS FAQ to address common questions that we receive during NCIDS consultations, kickoffs, and reviews. This would provide DOC/site teams with additional resources to support NCIDS adoption and may reduce the number of questions the team fields overall.
Key questions that need definition:
1) Should this be a page within the design system site? Or a standalone document (shared in teams or another similar space)
2) What content should live on this page? What sort of questions have we heard frequently that we should document formal responses for?
Examples:
1) What is required for NCIDS adoption? (Refer to maturity model page and levels)
2) Who is responsible for updating images or content within the site that is using NCIDS components? (The DOC team)
More definition is required for this story - suggestion from Bryan during internal conversation.
Build an NCIDS FAQ to address common questions that we receive during NCIDS consultations, kickoffs, and reviews. This would provide DOC/site teams with additional resources to support NCIDS adoption and may reduce the number of questions the team fields overall.
Key questions that need definition: 1) Should this be a page within the design system site? Or a standalone document (shared in teams or another similar space) 2) What content should live on this page? What sort of questions have we heard frequently that we should document formal responses for?
Examples: 1) What is required for NCIDS adoption? (Refer to maturity model page and levels) 2) Who is responsible for updating images or content within the site that is using NCIDS components? (The DOC team)