pelican-plugins / jinja-filters Goto Github PK

Further to #4 (Moving to pelican-plugins organization), look into hosting documentation within the core Pelican documentation. Or is the README here enough?

See getpelican/pelican#1999

As the package name changed, release one more 1.x release pointing to the new location.

This filter would allow you to do a reverse lookup based on the slug of the page you are looking for:

# custom Jinja2 filter
def get_by_slug(objs, slug):
    for obj in objs:
        if obj.slug == slug:
            return obj

JINJA_FILTERS = {
    "get_by_slug": get_by_slug,
}

https://siongui.github.io/2017/01/08/pelican-get-single-page-or-article-by-slug-metadata-in-theme/

Further to #4 (moving to the pelican-plugins organization), move this project's tasks.py file to mostly be contained in a separate repo, much like minchin.releaser.

@MinchinWeb said:

Would it be possible to "transfer ownership" instead?

The advantage of this is that is moves everything (issues, PR history, forks), and not just the Git history.

To do it, you'd need to give me permission to create repositories under pelican-plugins.

Done! Once you accept the invitation and this repo has been transferred, I'll rename the repo such that it lives at pelican-plugins/jinja-filters in order to maintain consistency with plugin naming conventions throughout the new organization. Looking forward to collaborating with you over at the new communal org! ✨