# Is pagination impossible or just hard?

**URL:** <https://meta.discourse.org/t/is-pagination-impossible-or-just-hard/231838>\
**Category:** Development\
**Created:** [July 3, 2022, 11:51pm UTC](https://meta.discourse.org/t/is-pagination-impossible-or-just-hard/231838 "2022-07-03T23:51:48Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![piffy](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/piffy/32/254198_2.png) [@piffy](https://meta.discourse.org/u/piffy)\
**Post date:** [July 3, 2022, 11:51pm UTC](https://meta.discourse.org/t/is-pagination-impossible-or-just-hard/231838/1 "2022-07-03T23:51:48Z")

</div>

I made the switch to Discourse recently and my community is torn on whether they like the infinite scroll or not. Some users like it, some don’t care, some treat it like an existential threat to the community. Based on other discussions I read here it sounds like it’s a common point of contention.

I understand that the developers of this software have no intention of providing pagination as an option. I can respect that. At this point, I’ve written a few plugins and layouts and looked though a bit of the code in the core github so I have a basic familiarity with the software. I’m just wondering _how_ hard it would be to write a plugin for pagination should my community continue to resist? Is it likely that I will have to rewrite a lot of the basic core ruby code? Is it something that can be placed on top of all the existing code that could run seamlessly? Is the database structure really poorly designed for querying in a paginated way?

Just wanted to get a sense of the feasibility of undertaking this task from the people who are most familiar with the code.

---

_[View the full topic](https://meta.discourse.org/t/is-pagination-impossible-or-just-hard/231838)._