pelican-alias
Pelican plugin for creating alias pages (useful for moving from a different URL scheme such as /<year>/<month>/<title>/ as used by Wordpress).
Inspired by jekyll_alias_generator.
License: MIT
Installation
Simply run:
pip install pelican-alias
Usage
Add pelican_alias to PLUGINS in the pelican configuration file
In each post or page that needs an alias, add an :alias: line to the metadata section. Example:
My Aliased Post ############################################## :date: 2013-05-31 22:09 :category: Pelican :slug: my-aliased-post :alias: /2013/05/my-aliased-post/, /2013/even-older-post-address My content goes here.
Markdown example:
Title: Another Aliased Post Date: 2013-06-01 21:10 Category: Pelican Alias: /2013/06/another-aliased-post/ /2013/even-older-aliased-post-address My content goes here.
This will create an additional HTML document at the path specified by :alias: that performs a canonical meta refresh to the new URL. If the path ends in a slash (as in the above example) then the file actually created will be index.html so that this system will work with Github pages.
Multiple aliases can be created for a single post. The delimiter for ReST format may be changed by setting ALIAS_DELIMITER in the pelican configuration file.
Metadata
Release files for pelican-alias 1.1
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-alias-1.1.tar.gz | 3.2 kB | Without provenance | Details for pelican-alias-1.1.tar.gz |
Release files / pelican-alias-1.1.tar.gz
| Download URL | pelican-alias-1.1.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e548c8245127bd540d53d9b1a95c8fb6958184f819d13f996f208f45f7237c4f
|
|
BLAKE2b-256 checksum How to use checksums |
af0a82422526f2d69917015ed7d47ba6dcd2789875359595fc5cb04a58115ec9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pelican-alias 1.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.