How to implement automatic pagination for BlogPosts like on Lombiq.com/blog?

[Alokohoy]

Hi everyone,
I’m currently working on a Blog/News section in an Orchard Core 2.2.1 project, and I’m trying to understand the best way to implement pagination for a list of blog posts, similar to the pagination used on the Lombiq website:

https://lombiq.com/blog

(example: numbered page buttons, previous/next controls, and URLs like /blog/pages/2)
What I want to achieve
When a new blog post is created using the Blog recipe, the system should automatically:
Display posts in a paginated list
Generate numbered pagination controls (1, 2, 3...)
Support next/previous navigation
Use clean URLs such as /news/pages/2

Basically, I want to reproduce the same pagination behavior as on the Lombiq blog.
What I’ve tried
I experimented with:
SQL Queries (skip/take)
ListPart
Liquid Templates
Custom routes
Query Widgets
I also assume that it’s possible to implement pagination manually in a custom Liquid template (handling skip/take and rendering a custom pager UI), but I’d like to avoid reinventing something if Orchard already provides built-in patterns or best practices for this.

My question

What is the recommended Orchard Core approach for implementing this kind of pagination?

Should I use a Query with a Pager shape, ListPart, Autoroute patterns, a custom Content Item, or another method?

Any guidance, examples, or recommendations would be greatly appreciated, especially from the Lombiq team.
Thanks in advance!

[hishamco]

Simple, you could use the Pager shape

https://github.com/OrchardCoreContrib/OrchardCoreContrib.Modules/blob/3a5d2928c05685559abb87726deed46647715c49/src/OrchardCoreContrib.UserGroups/Controllers/AdminController.cs#L33-L69

https://github.com/OrchardCoreContrib/OrchardCoreContrib.Modules/blob/3a5d2928c05685559abb87726deed46647715c49/src/OrchardCoreContrib.UserGroups/Views/Admin/Index.cshtml#L85

[Piedone]

So, keep in mind, that for this, you'll need to write your own C# and Razor (or Liquid). I think you can achieve something similar to a querying controller action with SQL or other Queries, but apparently, @Alokohoy you've tried that. Can you elaborate?