https://github.com/djo/reverse_kaminari

An example of the reverse pagination
https://github.com/djo/reverse_kaminari

Last synced: 9 months ago
JSON representation

An example of the reverse pagination

• Host: GitHub
• URL: https://github.com/djo/reverse_kaminari
• Owner: djo
• License: mit
• Created: 2012-01-17T16:58:48.000Z (over 14 years ago)
• Default Branch: master
• Last Pushed: 2014-06-19T10:18:44.000Z (about 12 years ago)
• Last Synced: 2025-08-11T17:43:51.928Z (11 months ago)
• Language: Ruby
• Homepage: http://reverse-kaminari.heroku.com/
• Size: 168 KB
• Stars: 7
• Watchers: 0
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# Example of the reverse pagination

[![Build Status](https://secure.travis-ci.org/Djo/reverse_kaminari.png "Build Status")](http://travis-ci.org/Djo/reverse_kaminari)

With the standard pagination strategy on adding a new content you will have situation when the older content moves from page #1 to page #2 and so on. It leads to issues with SEO, indexing and UX. This example shows you how to implement reverse pagination with [kaminari](https://github.com/amatsuda/kaminari) and floating limit for the first (index) page to avoid such issues.

## How it looks

For example you need to display 3 posts per page. In this case you will have from 3 to 5 posts on the start page:

9 posts will produce 3 pages with 3 posts on the index:

    9..7 posts on the /posts

    6..4 posts on the /posts/page-2

    3..1 posts on the /posts/page-1

10 posts will produce 3 pages with 4 posts on the index:

    10..7 posts on the /posts

    6..4  posts on the /posts/page-2

    3..1  posts on the /posts/page-1

11 posts will produce 3 pages with 5 posts on the index:

    11..7 posts on the /posts

    6..4  posts on the /posts/page-2

    3..1  posts on the /posts/page-1

And posts will produce 4 pages with 3 posts on the index:

    12..10 posts on the /posts

    9..7   posts on the /posts/page-3

    6..4   posts on the /posts/page-2

    3..1   posts on the /posts/page-1

## How it works

To get this behaviour you need to implement the floating limit for the first page.

In this example you will find the regular pagination bar in ascending order and offsets in URLs. Example of the pagination bar in descending order with page numbers in routes you can find in the [reverse pagination with will_paginate](https://github.com/Djo/reverse_will_paginate).

Also look at [https://github.com/Djo/reverse_will_paginate](https://github.com/Djo/reverse_will_paginate).