Update documentation on when to use tabs versus filters.
Problem
There seems to be a conflict between when to use tabs, versus when to filter the data to be viewed. Both operate in the same way by reducing content to a set of parameters. The key problem is that tabs can grow beyond screen widths, and do not have an affordance for responsive or accessible usage, apart from simply stacking on top of one and other.
As well, there are instances where there are multiple levels of tabs, which are not visually distinct. There should be more defined guidance on when to use one versus another.
Pajamas documentation
Examples
Tabs extend beyond page width |
---|
Checklist
Make sure the following are completed before closing the issue:
-
Assign the correct component label to this issue. -
Create an MR with the additions or updates needed. -
When applicable, create a new Pajamas issue using the "Figma update" issue template to update the component in Figma. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one. -
When applicable, create an MR in GitLab UI to update the component. If you do not have capacity or are unable to update the component directly, create a new GitLab UI issue using the "Component" issue template. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one. -
When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting. -
🎉 Congrats, you made it! You can now close this issue.
Edited by Daniel Mora