mkdocs-calendar-plugin
This MkDocs plugin exposes calendar information to the 'extra' configuration variable. This plugin is particularly useful when used together with the mkdocs-macros-plugin
Installation
Install the package with pip:
pip install mkdocs-calendar-plugin
Activate the plugin in mkdocs.yml:
plugins:
- search
- calendar
- macros
Configuration
The plugin can be configured in the plugins section of mkdocs.yml as follows:
plugins:
- search
- calendar:
tz: Europe/Zurich
start: 2023-02-20
end: 2023-06-23
- macros
It can be more convenient to use the extra configuration variable, so that the plugin section of mkdocs.yml can be kept clean.
mkdocs-calendar-plugin can also be configured using the extra.calendar_plugin configuration variable as follows:
extra:
calendar_plugin:
start: 2023-02-20
end: 2023-06-23
plugins:
- search
- calendar:
tz: Europe/Zurich
- macros
The plugin supports the following configuration options:
| Option | Description |
|---|---|
tz |
The timezone to use for the calendar. Defaults to UTC. |
start |
The start date of the calendar. |
end |
The end date of the calendar. |
today |
The date to use as today (used mainly for testing). Defaults to now. |
week_names |
The names of the weeks. Defaults to [] (no week names). |
plan |
The plan to use for the calendar. Defaults to {} (no plan). |
extra_key |
The key to use in the extra configuration variable. Defaults to cal. |
Extra configuration variable
The plugin exposes the following information in the extra.<extra_key> configuration variable:
| Key | Description |
|---|---|
now |
The current date and time |
today |
The current date |
weekday |
The current weekday (Monday == 0 ... Sunday == 6) |
iso_weekday |
The current ISO weekday (Monday == 0 ... Sunday == 7) |
week_number |
The current ISO week number |
start |
A copy of extra.<extra_key>.start (only if extra.<extra_key>.start is defined) |
academic_week |
The academic week number staring from extra.<extra_key>.start (only if extra.<extra_key>.start is defined) |
academic_week_name |
The academic week name (from the week_names array) staring from extra.<extra_key>.start (only if extra.<extra_key>.start is defined)-- |
elapsed |
The number of days elapsed since extra.<extra_key>.start (only if extra.<extra_key>.start is defined) |
elapsed_weeks |
The number of weeks elapsed since extra.<extra_key>.start (only if extra.<extra_key>.start is defined) |
aw |
alias for academic_week (only if extra.<extra_key>.start is defined) |
awn |
alias for academic_week_name (only if extra.<extra_key>.start is defined) |
end |
A copy of extra.<extra_key>.end (only if extra.<extra_key>.end is defined) |
remaining |
The remaining days to extra.<extra_key>.end (only if extra.<extra_key>.end is defined) |
remaining_weeks |
The remaining weeks to extra.<extra_key>.end (only if extra.<extra_key>.end is defined) |
The plugin also exposes the information compited from the plan. A typical plan looks like this:
plan:
P1: [s01, ex01, tp01]
P2: [sol1, s02, ex02, tp02]
The keys of the plan (here above P1 and P2) must exists
in the week_names array (see above). The values of the plan
are boolean variables that will be True if the corresponding week
is the present week (or before) and False otherwise.
Metadata
Release files for mkdocs-calendar-plugin 0.4.5
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 | |
|---|---|---|---|---|
| mkdocs_calendar_plugin-0.4.5.tar.gz | 3.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mkdocs_calendar_plugin-0.4.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.4 kB
Release files / mkdocs_calendar_plugin-0.4.5.tar.gz
| Download URL | mkdocs_calendar_plugin-0.4.5.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
65cb21585aa5815889a3842a385c0a0abfbc1c288278c99ecef1279a4dd681c5
|
|
BLAKE2b-256 checksum How to use checksums |
9b97416250f95490c5acddc5fac2dfb2c543f650f96951e64dbe6d56e8f6c65d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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 Feb 7, 2025.
Transparency logRelease files / mkdocs_calendar_plugin-0.4.5-py3-none-any.whl
| Download URL | mkdocs_calendar_plugin-0.4.5-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
307fabbd7e7bbfc404785eb00477929eb5dd5232c843a9b4b1057449777869d7
|
|
BLAKE2b-256 checksum How to use checksums |
0fb84da351e6a1bae6d7195d1d13177ee939b92ea6c8f2b1e6c0b6975ee65893
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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 Feb 7, 2025.
Transparency logSecurity for mkdocs-calendar-plugin 0.4.5
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mkdocs_calendar_plugin-0.4.5.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 Feb 7, 2025.
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.