You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 24, 2024. It is now read-only.
Document any known aliases of the component, decide if another name makes more sense.
Has known aliases
Requires name change
Design Standard Doc
Any documentation needed to be added to terra-ui describing the make up and usage of the component
Any doc examples that need to be updated?
Missing design standard documentation linkage.
Guides
Any guides needed to be added to terra-ui describing the usage of this component when used with other components.
Missing Guides
Missing UX recommended Usage.
Deprecation guide
Accessibility Guides
Missing Accessibility Guides
Behaviours
Missing behaviours
Contains bad practice behaviours that should be removed
Accessibility
Meets wcag 2.0/section 508 standards
Meets wcag 2.1/en 301 549 standards
Deprecation
Component is a bad pattern and should be deprecated.
Related Issues
Other Considerations
This component has relatively high usage but does not really have a mapped UX concept. It seems to be good at what it does (i.e. not a whole lot of issues with it or enhancement requests for it). Proposal is to leave this relatively alone as it does not seem to have a super high priority for any changes.
The text was updated successfully, but these errors were encountered:
terra-grid
Known Aliases
Document any known aliases of the component, decide if another name makes more sense.
Design Standard Doc
Any documentation needed to be added to terra-ui describing the make up and usage of the component
Any doc examples that need to be updated?
Guides
Any guides needed to be added to terra-ui describing the usage of this component when used with other components.
Accessibility Guides
Behaviours
Accessibility
Deprecation
Related Issues
Other Considerations
This component has relatively high usage but does not really have a mapped UX concept. It seems to be good at what it does (i.e. not a whole lot of issues with it or enhancement requests for it). Proposal is to leave this relatively alone as it does not seem to have a super high priority for any changes.
The text was updated successfully, but these errors were encountered: