Change Details

==== Background/Goal Create and publish Design System Visual Style Design Guidelines. ===== User stories [] As a designer, I can easily locate and understand defined visual styles that should be leveraged when designing. ===== Considerations - Visual styles defined in the Design System should be easy to find by any type of user ===== Requirements [] There is a single source of truth for Visual Style Guidelines on wiki (ex: are we extending this: https://design.wikimedia.org/style-guide/visual-style.html or adding elsewhere?) [] The Visual Style Guide MUST include the following: [] A full list of all visual styles that already exist in the Design System [] Visual Style descriptions [] Link to visual style design guidelines (if available) [] Overall Design System Status: Not Started, In Design/Scoping, Ready for Development, In Development, Product Sign-Off, Done, Blocked [] Demo Link [] PHAB Implementation Epic Link (if available) [] Design Specs in Figma Link [] There is a single source of truth for each user story (aka artifact) [] All source of truth documents/artifacts are available via Design System Portal/Wiki ===== Acceptance criteria [] There is a single source of truth for each user story (aka document) [] All documentation should link back to a central Design System Portal/Wiki [] Documents should be: [] easy to read (limited jargon) [] clear to follow (written as steps, checklists, visual diagrams, etc.) [] Access to documents should NOT be restricted for viewing by target users (aka remove or update permissions as necessary) ===== Test scenarios [to come] ===== Open questions - How do we mitigate the confusion between existing standards set by other systems (such as OOUI) vs our visual style design standards? Should we document what is different between them?

==== Background/Goal Create and publish Design System Visual Style Design Guidelines. ===== User stories - As a designer, I can easily locate and understand defined visual styles that should be leveraged when designing. ===== Considerations - Visual styles defined in the Design System should be easy to find by any type of user ===== Requirements [] There is a single source of truth for Visual Style Guidelines on wiki (ex: are we extending this: https://design.wikimedia.org/style-guide/visual-style.html or adding elsewhere?) [] The Visual Style Guide MUST include the following: [] A full list of all visual styles that already exist in the Design System [] Visual Style descriptions [] Link to visual style design guidelines (if available) [] Overall Design System Status: Not Started, In Design/Scoping, Ready for Development, In Development, Product Sign-Off, Done, Blocked [] Demo Link [] PHAB Implementation Epic Link (if available) [] Design Specs in Figma Link [] There is a single source of truth for each user story (aka artifact) [] All source of truth documents/artifacts are available via Design System Portal/Wiki ===== Acceptance criteria [] There is a single source of truth for each user story (aka document) [] All documentation should link back to a central Design System Portal/Wiki [] Documents should be: [] easy to read (limited jargon) [] clear to follow (written as steps, checklists, visual diagrams, etc.) [] Access to documents should NOT be restricted for viewing by target users (aka remove or update permissions as necessary) ===== Test scenarios [to come] ===== Open questions - How do we mitigate the confusion between existing standards set by other systems (such as OOUI) vs our visual style design standards? Should we document what is different between them?

==== Background/Goal Create and publish Design System Visual Style Design Guidelines. ===== User stories []- As a designer, I can easily locate and understand defined visual styles that should be leveraged when designing. ===== Considerations - Visual styles defined in the Design System should be easy to find by any type of user ===== Requirements [] There is a single source of truth for Visual Style Guidelines on wiki (ex: are we extending this: https://design.wikimedia.org/style-guide/visual-style.html or adding elsewhere?) [] The Visual Style Guide MUST include the following: [] A full list of all visual styles that already exist in the Design System [] Visual Style descriptions [] Link to visual style design guidelines (if available) [] Overall Design System Status: Not Started, In Design/Scoping, Ready for Development, In Development, Product Sign-Off, Done, Blocked [] Demo Link [] PHAB Implementation Epic Link (if available) [] Design Specs in Figma Link [] There is a single source of truth for each user story (aka artifact) [] All source of truth documents/artifacts are available via Design System Portal/Wiki ===== Acceptance criteria [] There is a single source of truth for each user story (aka document) [] All documentation should link back to a central Design System Portal/Wiki [] Documents should be: [] easy to read (limited jargon) [] clear to follow (written as steps, checklists, visual diagrams, etc.) [] Access to documents should NOT be restricted for viewing by target users (aka remove or update permissions as necessary) ===== Test scenarios [to come] ===== Open questions - How do we mitigate the confusion between existing standards set by other systems (such as OOUI) vs our visual style design standards? Should we document what is different between them?