|
@@ -13,11 +13,13 @@ For example, if you have the following pieces of metadata in an article:
|
|
|
|
|
|
# my_article.markdown
|
|
|
Date: 2000-01-01
|
|
|
- Created_Date: 1999-08-04
|
|
|
Idea_Date: 1993-03-04
|
|
|
+ Important_Dates: 2013-10-12
|
|
|
+ 2013-11-08
|
|
|
+ 2013-12-02
|
|
|
|
|
|
-Normally, the Created_Date and Idea_Date variables will be strings, so you will
|
|
|
-not be able to use the strftime() Jinja filter on them.
|
|
|
+Normally, the Idea_Date and Important_Dates variables will be strings, so
|
|
|
+you will not be able to use the strftime() Jinja filter on them.
|
|
|
|
|
|
With this plugin, you define in your settings file a list of the names of
|
|
|
the additional metadata fields you want to treat as dates:
|
|
@@ -25,12 +27,15 @@ the additional metadata fields you want to treat as dates:
|
|
|
.. code-block:: python
|
|
|
|
|
|
# pelicanconf.py
|
|
|
- DATEISH_PROPERTIES = ['created_date', 'idea_date']
|
|
|
+ DATEISH_PROPERTIES = ['idea_date', 'important_dates']
|
|
|
|
|
|
Then you can use them in templates just like date:
|
|
|
|
|
|
.. code-block:: html+jinja
|
|
|
|
|
|
# mytemplate.html
|
|
|
- <p>Created date: {{ article.created_date | strftime('%d %B %Y') }}</p>
|
|
|
+ <p>Idea date: {{ article.idea_date | strftime('%d %B %Y') }}</p>
|
|
|
+ {% for d in article.important_dates %}
|
|
|
+ <p>Important date: {{ d | strftime('%d %B %Y') }}</p>
|
|
|
+ {% endfor %}
|
|
|
|