New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pagination #77

govuk-design-system opened this Issue Jan 15, 2018 · 7 comments


8 participants

govuk-design-system commented Jan 15, 2018


Help users navigate through multiple pages. Typically used for pages of search results.


Anything else

@govuk-design-system govuk-design-system created this issue from a note in GOV.UK Design System Community Backlog (Agreed) Jan 15, 2018


This comment has been minimized.


joelanman commented Feb 22, 2018


This comment has been minimized.

36degrees commented Aug 22, 2018


This comment has been minimized.

gazaston commented Sep 25, 2018

Pagination from

screen shot 2018-09-25 at 10 27 19


This comment has been minimized.

leekowalkowski-hmrc commented Oct 17, 2018

We need to make sure pagination links are big enough for touch screens, I think all the examples shared are not.


This comment has been minimized.

glenjamin commented Oct 19, 2018

Are there scenarios where "jump to page N" is actually desirable to a user?

In practice I can see why next/previous is useful in a long list, but jumping to a numbered page is probably always going to be worse than providing the user a way to filter down the results to something manageable.


This comment has been minimized.

36degrees commented Oct 19, 2018

One scenario I can think of is a user 'binary searching' a relatively small number of sorted results. For example, with an imagined alphabetical result set spanning 10 pages, if a user is looking for something beginning with 'N' they might jump to page 5 (guessing, based on the position of n in the alphabet) and then navigate from there to find the result they're looking for, which would arguably be a better experience than having to page through one page at a time.

I'd agree that providing a search or filtering interface would be preferred, but might not always be possible?

EDIT: Filtering and searching might be the sort of thing that would get dropped from an 'MVP', in which case providing the ability to quickly move through a result set as described above might be an easy short-term solution.

@helena-moj helena-moj referenced this issue Nov 28, 2018


Pagination #13


This comment has been minimized.

mgilgar commented Nov 29, 2018

I think 90% of the times it should be enough to provide only the first X results without pagination and give the option to filter or seach. Less complicated for the user and for the developer.

Anyway, I can see the needs of the other options for some scenarios. I think it would be great if govuk can develop patterns for all of them.

Also, please specify what the url should look like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment