Pagination path customisation?

[cossssmin]

Been working on a Jigsaw-powered blog template recently, and I want to make it easier for people to switch from WordPress to a static blog.

One of the things that would help with the transition is to be able to customise the pagination path in Jigsaw, so that the static blog will keep the same URLs for paginated content.

Currently, both BasicOutputPathResolver and PrettyOutputPathResolver can only generate root-relative number-based folders, such as /, /2,/3. The WordPress default is /page/[number], and there are also plugins that allow customising this.

If possible, would you please consider allowing for a user-provided prefix for the pagination (output) path?

For example, the pagination front matter could allow for an optional prefix (or slug?) variable:

---
pagination:
  collection: posts
  perPage: 5
  prefix: page
---

That would result in pagination folder structures like this:

[ baseUrl ]
[ baseUrl ]/page/2

What do you think? 🙂

[damiani]

Yes, prefix is a great idea!