You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the paginator in cobalt has support for next/prev and first/last, it doesn't know what the URLs are for other pages in the current index. This means bootstrap's default paginator, which leans heavily on clickable links for specific page numbers, requires manually figuring out the URLs that a specific page number should link to. This is fine while the paginator is restricted to not being used in layouts, but as soon as there's potential for the frontmatter to be separated from the paginator, or for the paginator to be used in layouts, this is going to be a bigger problem.
The minimum solution would be a field on the paginator that listed all the URLs for each page generated by the current index ("index-page"). A more sophisticated solution would make it possible to access the full frontmatter for each index-page
My proposition is to implement this new trail field.
indexes is intended for "meta paginator" in the case of indexing on tags/categories/dates:
each paginator in indexes is the access to the paginator of each tags
While the paginator in cobalt has support for next/prev and first/last, it doesn't know what the URLs are for other pages in the current index. This means bootstrap's default paginator, which leans heavily on clickable links for specific page numbers, requires manually figuring out the URLs that a specific page number should link to. This is fine while the paginator is restricted to not being used in layouts, but as soon as there's potential for the frontmatter to be separated from the paginator, or for the paginator to be used in layouts, this is going to be a bigger problem.
The minimum solution would be a field on the paginator that listed all the URLs for each page generated by the current index ("index-page"). A more sophisticated solution would make it possible to access the full frontmatter for each index-page
Here's an example of my workaround:
The text was updated successfully, but these errors were encountered: