pelican mit Homebrew, apt, pacman, dnf installieren

Projektlinks

• Homepage
• Paketmanager-Seite

Befehle und Aliase

• pelican
• pelican-import
• pelican-plugins
• pelican-quickstart
• pelican-themes

Projektgeschichte

Alexis Métaireau created Pelican in 2010 after wanting to leave WordPress while continuing to write with an editor in Markdown or reStructuredText. The name is an anagram of the French word `calepin`, meaning notebook.

The first usable implementation was about 200 lines. As settings, feeds, multiple themes, and markup formats accumulated, the original single-file program was split into readers, generators, writers, and content objects.

The documented release history begins with the first working version on 2010-08-19. Later development added Python 3 support, a separate plugin ecosystem, richer importing, multilingual publishing, caching, and deployment automation.

Adoptionsgeschichte

Pelican became part of the Python static-publishing ecosystem and is distributed through PyPI and several operating-system package managers. The supplied package facts identify Homebrew, Debian, Ubuntu, Fedora, and Arch packages.

A notable public deployment occurred in March 2013, when kernel.org announced that it had switched to Pelican for static rendering in order to simplify mirroring and distribution.

Wie es verwendet wird

Start a site with `pelican-quickstart`, write content in the generated content tree, run `pelican` to build the output directory, and use `pelican --listen` for local preview.

Keep general settings in `pelicanconf.py` and publication-specific settings in `publishconf.py`; use `pelican-import`, themes, and plugins for migration and customization.

Warum Paket-Nerds sich dafür interessieren

Pelican is the Pythonic branch of static-site-generator culture: text content, Jinja2 themes, Python plugins, reproducible static output, and no database or server-side application required at deployment time.

Its bundled commands cover project creation, generation, migration, theme management, and plugin inspection, making the package a complete publishing workflow rather than a single format converter.

Zeitleiste

• 2010-08-19: Pelican's first working release was published.
• 2010-12: Original author Alexis Métaireau documented Pelican's motivation and early architecture.
• 2013-03-01: kernel.org announced its switch to Pelican for statically rendered site content.
• 2013-04: Pelican added Python 3 support and moved plugins toward a separate repository.

Related projects

• Jinja2 supplies Pelican's theme-template model.
• Pelican Plugins is the official extension ecosystem, while Pelican Themes provides reusable presentation layers.
• Hugo and Zola are single-binary static-site generators commonly considered for the same publishing task.

Quellen

• https://docs.getpelican.com/en/latest/
• https://docs.getpelican.com/en/latest/changelog.html
• https://docs.getpelican.com/en/latest/report.html
• https://github.com/getpelican/pelican
• https://www.kernel.org/pelican.html