Problem/Motivation
Currently, pagination in Drupal follows the standard ascending order (1, 2, 3, …). When new nodes are added and the page limit is reached (e.g., 10 per page), older nodes shift to different pages, causing two issues:
User Experience: Users memorize page numbers, and when they return, content is no longer in the expected location.
SEO Concerns: Search engine bots (e.g., Googlebot) index pages based on their URLs. When content shifts, bots detect different content on the same URLs, leading to unnecessary reindexing, possible ranking penalties, and incorrect search results.
Steps to reproduce
- Create a view with a paginated list of nodes, ordered by descending creation time.
- Set the page limit to a fixed number (e.g., 10 per page).
- Observe the pagination pattern (1, 2, 3, …).
- Add new nodes and notice how older nodes shift to different pages, disrupting memorized URLs and positions.
Proposed resolution
- Implement an option in Drupal’s Views pagination to reverse the numbering.
- Instead of 1, 2, 3, ... use a descending pattern like 45, 44, 43, ... for a total of 45 pages.
- Ensure that when new nodes are added, older ones remain on the same page number.
Remaining tasks
- Identify the best method to implement reversed pagination.
- Modify Drupal Views or pagination logic to allow descending page numbers.
- Provide configuration options to enable/disable this feature.
- Test for compatibility with existing themes and modules.
- Ensure SEO benefits are achieved and document the improvements.
User interface changes
A new option in Views configuration to enable reversed pagination.
Introduced terminology
Reversed pagination: A pagination method where page numbers count down instead of up.
API changes
Potential modifications to pagination handling in Views.
Data model changes
No database schema changes are required.
Release notes snippet
Added an option in Views to enable reversed pagination, allowing page numbers to count down instead of up. This helps maintain content consistency for returning users and improves SEO by reducing unnecessary reindexing.
Problem/Motivation
Currently, Views pagination only allows users to navigate using previous/next arrow links. This can be inefficient when dealing with large datasets, as users must click through multiple pages to reach a specific one. Adding a direct page number input field will improve usability and efficiency.
Steps to reproduce
- Create a View with pagination enabled.
- Display the View and attempt to navigate to a specific page.
- Observe that there is no option to enter a page number directly.
Proposed resolution
- Introduce a text input field alongside the existing pagination controls.
- Allow users to enter a page number and navigate directly when they submit the input.
- Ensure proper validation to prevent invalid page numbers (e.g., negative numbers, non-numeric input, exceeding total pages).
- Integrate seamlessly with Drupal’s Views system without breaking existing pagination functionality.
Remaining tasks
- Develop and test the pagination input field functionality.
- Implement form validation for the page number input.
- Ensure compatibility with different themes and responsive layouts.
- Write automated tests to validate the functionality.
- Update documentation and user guides for the new feature.
User interface changes
- A new input field will be added to the pagination controls in Views.
- Users will be able to enter a page number and press "Go" or "Enter" to navigate.
- Improved user experience for large datasets in Views.
Introduced terminology
- Pagination Input Field: A new input box allowing users to enter a page number directly.
API changes
- No API changes
Data model changes
- No changes to the data model.
Release notes snippet
The Views pagination system now includes an input field allowing users to enter a page number directly, improving navigation for large content lists. This enhancement provides a more efficient way to jump to a specific page without excessive clicking.