Support for Pagination (issue #496) #589
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Oh gosh finally...
Support for pagination, works like:
Assuming this is on page
foo.md
it will lead to/foo/
and/foo/1/
with content<li>Stefan</li><li>Jeff</li>
/foo/2/
with content<li>Alan</li><li>Viral</li>
Note: this can be used with any sort of list or item, so it doesn't necessarily need to be a
<li>...
in fact it could be div blocks. More specific functionality can be wrapped in a newcommand e.g.:(will be a demo in FranklinFAQ)
closes #496
Note: if pagination over 5 pages then changing something and paginating over 2 pages, the dirs 3,4,5 will be removed. This should generally be innocuous with the exception of people who want to paginate their front page in which case it may be more likely to have numeric dirs in
__site
(but not very so probably still fine).