Previously, Markdown files without explicit 'Title:' metadata would fail
to get titles extracted from their first heading, unlike RST files which
support both metadata and heading-based title extraction.
New Configuration Options:
- HEADING_METADATA: Enable/disable heading metadata extraction
- HEADING_METADATA_MAP: Map heading levels to metadata fields
- HEADING_METADATA_PATTERNS: Custom regex patterns for extraction
Resolves issue where markdown files like:
Date: 2023-12-01
Category: tech
# My Article Title
Can now have titles extracted without manual Title: metadata.
Fixes also the issue where Markdown articles showed duplicate titles
when HEADING_METADATA=True was set in configuration.
References: https://github.com/getpelican/pelican/discussions/3290
Signed-off-by: Matěj Cepl <mcepl@cepl.eu>
In the documentation, both `SOCIAL` and `LINKS` are described as a list
of tuples, but all examples show them as tuples of tuples. It makes the
most sense for them to be lists, so the examples should match the docs
going forward.
Similarly, `LOCALE` is described as a list, but the examples show it as
a tuple. Likewise, the examples should be lists, in line with the
description.
* Fix anchor links for settings by moving default value text down.
* Fix typos in default values.
---------
Co-authored-by: Justin Mayer <entroP@gmail.com>
The default `IGNORE_FILES` value of `'.*'` was being compiled to a regular expression and then passed into `watchfiles.DefaultFilter` to filter out files when auto-reload is enabled.
This commit compares the patterns from `IGNORE_FILES` directly with the filename to match the usage of `fnmatch` elsewhere in the codebase. The new filtering class will continue working as expected for custom `IGNORE_FILES` settings.
This is to avoid subtle behaviour that contributed to root cause of
https://github.com/pelican-plugins/sitemap/issues/36
Specifically: if installing Pelican into a local virtualenv with the pdm or uv
default name ".venv", then subdirectories of .venv will contain all of the test
.rst and .md files.
If you then run Pelican in that same root directory using the default PATH
value (".") then it will add those content files to the site.
Currently, the documentation refers to creating new themes a lot.
It is much less apparent how one can customize an existing theme by
overriding individual templates or adding new ones. This commit adds
an FAQ for this, and also mentions the mechanism in the FAQ on custom
templates.
