Draft: Update pagination guidelines for gl-card implementations
What does this MR do?
Provide guidance of how to use pagination/load more in a list that is contained in gl-card layout.
Main goal of guidance
- Which kind of pagination is recommended (numbered, prev/next, load more)
- Placement of pagination (inside card, outside card, in footer)
Current mixed usage
At the moment we have different ways of doing pagination in lists in GitLab
| Protected packages | Labels |
|---|---|
 |
 |
Some other ways that have been proposed
| Approval rules - Load more gitlab-org/gitlab!148824 (merged) | Concept - footer |
|---|---|
 |
 |
Does this MR meet the acceptance criteria?
-
The MR title and commit messages meet the Pajamas commit conventions. -
The “What does this MR do?” section in the MR description is filled out, explaining the reasons for and scope of the proposed changes, per “Say why not just what”. - For example, if the MR is focused on usage guidelines, addressing accessibility challenges could be added in a separate MR.
-
Relevant label(s) are applied to the MR. -
The MR is added to a milestone. -
If creating a new component page from scratch, it follows the page template structure. -
Content follows the Pajamas voice and tone guidelines, falling back on the GitLab Documentation Style Guide when needed. -
Related pages are cross-linked, where helpful. Component pages have related components and patterns defined in their Markdown front matter. -
If embedding a Figma file, it follows the Figma embed guide. -
Review requested from any GitLab designer or directly from a maintainer or trainee maintainer.