Change Details

==== Background/Goal Create and publish an initial version of the Design System Component Catalog ===== User stories - As a designer, I can easily locate components supported by the design system and their current state. ===== Considerations - Components available in the Design System should be easy to find by any type of user - We have multiple documents related to components that need to be organized and centralized ===== Requirements [X] Develop a component catalog: https://783871--wikimedia-codex.netlify.app/components/button.html [] The Component Catalog MUST include the following datapoints: [] Overview of what Components are [X] A full list of all components that already exist in the Design System [X] Component Descriptions [] Component Design Guidelines link (if available) [] Overall Design System Status**: Not Started, In Design/Scoping, Ready for Development, In Development, Product Sign-Off, Done (aka available in Codex), Blocked [] For existing components within the Design System, the Component Catalog MUST include: [] **Token Integration Stauts**: Not Started, In Token Review, Needs Token Updates, In Development (Tokens being incorporated), Done (Tokens Fully Integrated), Blocked [X] **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 [to come]

==== Background/Goal Create and publish an initial version of the Design System Component Catalog ===== User stories - As a designer, I can easily locate components supported by the design system and their current state. ===== Considerations - Components available in the Design System should be easy to find by any type of user - We have multiple documents related to components that need to be organized and centralized ===== Requirements [X] Develop a component catalog: https://783871--wikimedia-codex.netlify.app/components/button.html [] The Component Catalog MUST include the following datapoints: [] Overview of what Components are [X] A full list of all components that already exist in the Design System [X] Component Descriptions [] Component Design Guidelines link (if available) [] Overall Design System Status**: Not Started, In Design/Scoping, Ready for Development, In Development, Product Sign-Off, Done (aka available in Codex), Blocked [] For existing components within the Design System, the Component Catalog MUST include: [] **Token Integration Status**: Not Started, In Token Review, Needs Token Updates, In Development (Tokens being incorporated), Done (Tokens Fully Integrated), Blocked [X] **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 [to come]

==== Background/Goal Create and publish an initial version of the Design System Component Catalog ===== User stories - As a designer, I can easily locate components supported by the design system and their current state. ===== Considerations - Components available in the Design System should be easy to find by any type of user - We have multiple documents related to components that need to be organized and centralized ===== Requirements [X] Develop a component catalog: https://783871--wikimedia-codex.netlify.app/components/button.html [] The Component Catalog MUST include the following datapoints: [] Overview of what Components are [X] A full list of all components that already exist in the Design System [X] Component Descriptions [] Component Design Guidelines link (if available) [] Overall Design System Status**: Not Started, In Design/Scoping, Ready for Development, In Development, Product Sign-Off, Done (aka available in Codex), Blocked [] For existing components within the Design System, the Component Catalog MUST include: [] **Token Integration Stauttus**: Not Started, In Token Review, Needs Token Updates, In Development (Tokens being incorporated), Done (Tokens Fully Integrated), Blocked [X] **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 [to come]