%PREV% and %NEXT% inclusions #460
Description
those inclusion take the same params base as %LIST%.
they return a single page ID which correspond to the prev or next page compared to the current page according to the given filters.
That way editors can put them in a template inside <a> tag.
[previous article](%PREV?bookmark=articles%)
The problem is when current page is the first or last page of the list.
The solution I see is letting editors add a CSS rule to manage this using [href=""] to target the useless button. For example, the button could be grayed or turn invisible.