Lektor plugin to generate blog-like index pages
Author: Jeff Dairiki
View all tags.
This Lektor plugin can be used to generate “index pages” for a blog or similar collection of pages. These index pages list the blog posts segregated by some key, with each index page containing only those posts which match that key.
Examples of what this can be used for include:
Category Indexes: A set of index pages, one for each category, which lists all the posts in that category. (Multi-valued index keys are also supported, so that each post can appear on more than a single index page: e.g. keyword indexes.)
Date Indexes: A set of index pages, one for each year (say), which list all the posts in that year. (Sub-indexes are supported subindexes — e.g., each year index may have as children a sequence of month indexes.)
Behind the scenes, judicious caching of indexing results, and careful control of Lektor’s dependency tracking prevent all this from slowing the build process down too excruciatingly much.
Jeff Dairiki email@example.com
jinja2. Jinja2 version 3 is now required.
Documentation clarifications, updates and fixes. (PR #2 — Thank you Bart Van Loon!)
Add missing requirement
docs enviroment to
tox.ini to test that docs will build cleanly.
No code changes.
Update development status classifier to "stable".
key field on the index virtual source object. It is an
_id, but is syntactically more self-explanatory.
keys configuration key has been renamed to
key expression is being evaluted, the record whose key(s)
is(are) to be be computed is now available in the jinja context as
item rather than
record argument has been dropped from the (jinja) global
index_pages function. (Since indexes can not have multiple
parents, it is not necessary.)
parent configuration key has been renamed to
slug configuration key has been renamed to
attributes config section has been renamed to
Though they are not quite like regular Lektor Record fields, they are more field-like than attribute-like. (I.e. access is via getitem rather than getattr.)