Other articles

  1. Migrating Plugins to New Organization

    So you want to help migrate a plugin? Great! Depending on the situation, tap on one of the following links.

    The target plugin is located in:

    • [legacy monolithic repository](#migration-from-monolithic-repository) (i.e., at github.com/getpelican/pelican-plugins)
    • [personal repository on GitHub](#migration-from-personal-repository)

    Migration from Monolithic Repository

    Create an issue at …

    read more
  2. Pelican 4.5 released

    Pelican 4.5 is now available. Its marquee feature is support for “namespace” plugins, which means any plugin listed under the new Pelican Plugins organization can be installed via Pip, after which Pelican should automatically detect and enable the new plugin.

    This also means that Pelican projects can specify and …

    read more
  3. Pelican Sprint — Fall 2019

    In the spirit of Hacktoberfest, we will be conducting an informal sprint on Sunday, 20 October. One of the goals for this sprint is to migrate plugins from the current monolithic repository to individual, community-shared repositories. The following issues will provide some historical background for those who want to learn …

    read more
  4. Pelican 4.1 released

    Pelican 4.1 has been released and includes the following enhancements, fixes, and tweaks:

    • Live browser reload upon changed files (provided via Invoke task)
    • Add pyproject.toml, managed by Poetry
    • Support for invoking python -m pelican
    • Add relative source path attribute to content
    • Allow directories in EXTRA_PATH_METADATA
    • Add all_articles variable …
    read more

Page 1 / 4 »