Yep, however I’m questioning about the pagination pages, the second warn should be correct.
Page
Permalink
https://example.org/
https://example.org/
https://example.org/page/2
https://example.org/
https://example.org/page/3
https://example.org/
I’m not sure if the pagination page’s Permalink should be similar the follows, or it’s theme author’s duty to use .Paginator.URL instead of Permalink in this case.
Pagination is the process of splitting a list page into two or more pagers, where each pager contains a subset of the page collection and navigation links to other pagers.
So at this stage
there is no Page but only ONE Pager object which offers Pager methods | Hugo to deal with it’s pageSets.
the current context “.” of the rendered Page (index.md) is unchanged.
You already noticed that by using .Paginator.PageNumber and not just .PageNumber in your warnf Statement.
This is a Design/Implementation decision
There are plenty of reasons I can think of why that has been done… but I wont guess here