Pelican YAML Metadata
This Pelican plugin allows articles written in Markdown to define their metadata using a YAML header. This format is compatible with other popular static site generators like Jekyll or Hugo.
It is fully backwards-compatible with the default metadata parsing.
Installation
This plugin can be installed via:
python -m pip install pelican-yaml-metadata
As long as you have not explicitly added a PLUGINS setting to your Pelican settings file, then the newly-installed plugin should be automatically detected and enabled. Otherwise, you must add yaml_metadata to your existing PLUGINS list. For more information, please see the How to Use Plugins documentation.
Usage
This plugin aims to keep things simple. After installing and enabling it, any Markdown files will have the option of defining metadata using a YAML header instead of the standard key/value pairs.
In order to specify metadata using YAML, enclose it within --- lines.
Example:
---
title: Some title
author: Some person
tags:
- tag 1
- tag 2
date: 2014-12-25 00:00
summary: The article summary will be __parsed__ as markdown
---
This is some article text.
If the YAML block is not found, the metadata will be parsed using the normal Markdown metadata syntax.
Contributing
Contributions are welcome and much appreciated. Every little bit helps. You can contribute by improving the documentation, adding missing features, and fixing bugs. You can also help out by reviewing and commenting on existing issues.
To start contributing to this plugin, review the Contributing to Pelican documentation, beginning with the Contributing Code section.
License
This project is licensed under the MIT license.
Metadata
Release files for pelican-yaml-metadata 2.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pelican_yaml_metadata-2.2.0.tar.gz | 5.5 kB | With provenance | Details for pelican_yaml_metadata-2.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pelican_yaml_metadata-2.2.0-py3-none-any.whl | Python 3 | none | any | Details for pelican_yaml_metadata-2.2.0-py3-none-any.whl |
Total release size: 11.0 kB
Release files / pelican_yaml_metadata-2.2.0.tar.gz
| Download URL | pelican_yaml_metadata-2.2.0.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5fcaa19ee3521501a5129aaabcfe0bdceb00a525ccc9a102d2fb093e72e2b04b
|
|
BLAKE2b-256 checksum How to use checksums |
de3d8f5cf45b7593e9b01cbf20ce51aa08c5103fae3008c77dd240366ca49872
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logRelease files / pelican_yaml_metadata-2.2.0-py3-none-any.whl
| Download URL | pelican_yaml_metadata-2.2.0-py3-none-any.whl |
|---|---|
| Size | 5.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ad8db728a962251f0a554bcccb661a8a9d174fbad689a7af7603c02ae7f9d7e3
|
|
BLAKE2b-256 checksum How to use checksums |
a2940e83a09ba95d7dd8c9ce0a7beda7a3e692080d274556fc99fdec9937e336
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logSecurity for pelican-yaml-metadata 2.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pelican_yaml_metadata-2.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.