github/pelican
1
0
Fork 1
mirror of https://github.com/getpelican/pelican.git synced 2025-10-15 20:28:56 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Follow-up changes to metadata field docs

Browse source
This commit is contained in:
Justin Mayer 2019-10-16 15:52:50 -07:00
commit f0617a53dc
1 changed files with 23 additions and 25 deletions
Download patch file Download diff file Expand all files Collapse all files

46
docs/content.rst
View file

@ -71,31 +71,29 @@ Metadata syntax for Markdown posts should follow this pattern::
This is the content of my super blog post. This is the content of my super blog post.
You can also have your own metadata keys (so long as they don't conflict with You can also have your own metadata keys (so long as they don't conflict with
reserved metadata keywords) for use in your templates. Following is reserved metadata keywords) for use in your templates. The following table
the list of reserved metadata keywords: contains a list of reserved metadata keywords:
================= ================ ============================================ =============== ===============================================================
reStructuredText Markdown Description Metadata Description
================= ================ ============================================ =============== ===============================================================
``:title:`` ``Title:`` Title of the article or page ``title`` Title of the article or page
``:date:`` ``Date:`` Publication date (``YYYY-MM-DD HH:SS``) ``date`` Publication date (e.g., ``YYYY-MM-DD HH:SS``)
``:modified:`` ``Modified:`` Modification date (``YYYY-MM-DD HH:SS``) ``modified`` Modification date (e.g., ``YYYY-MM-DD HH:SS``)
``:tags:`` ``Tags:`` Content tags, separated by commas ``tags`` Content tags, separated by commas
``:keywords:`` ``Keywords:`` Content keywords, separated by commas ``keywords`` Content keywords, separated by commas (HTML content only)
``:category:`` ``Category:`` Content category (one only — not multiple) ``category`` Content category (one only — not multiple)
``:slug:`` ``Slug:`` Identifier used in URLs and translations ``slug`` Identifier used in URLs and translations
``:author:`` ``Author:`` Content author, when there is only one ``author`` Content author, when there is only one
``:authors:`` ``Authors:`` Content authors, when there are multiple ``authors`` Content authors, when there are multiple
``:summary:`` ``Summary:`` Brief description of content for index pages ``summary`` Brief description of content for index pages
``:lang:`` ``Lang:`` Content language ID (``en``, ``fr``, etc.) ``lang`` Content language ID (``en``, ``fr``, etc.)
``:translation:`` ``Translation:`` Is article is a translation of another ``translation`` Is content is a translation of another (``true`` or ``false``)
(``true`` or ``false``) ``status`` Content status: ``draft``, ``hidden``, or ``published``
``:status:`` ``Status:`` Content status: ``template`` Name of template to use to generate content (without extension)
``draft``, ``hidden``, or ``published`` ``save_as`` Save content to this relative file path
``:template:`` ``Template:`` Name of template to use to generate content ``url`` URL to use for this article/page
``:save_us:`` ``Save_us:`` Save content to this relative file path =============== ===============================================================
``:url:`` ``Url:`` URL to use for this article/page
================= ================ ============================================
Readers for additional formats (such as AsciiDoc_) are available via plugins. Readers for additional formats (such as AsciiDoc_) are available via plugins.
Refer to `pelican-plugins`_ repository for those. Refer to `pelican-plugins`_ repository for those.