created:2021-05-14
author:Foobär
top:README:Blog Entries:Tags
sort:009
title:Tag Types

<p>
The following tag types can be used in header of pagge source files as well as entry source files.
</p><p>
<code>note:</code>
This tag has no function. It is a valid tag but it is ignored by SBWG. It can be used to include a note in an entry or page source file header.
Example: <code>note:This is just a note.</code>
</p><p>
<code>title:</code>
The title of the entry or page
Example: <code>title:An Interesting Title</code>
</p><p>
<code>menu:</code>
This tag type does not exist, yet. It will be used in future versions of SBWG to place an entry (or page) at a certain point in a menu.
Example: <code>menu:Main:About:History</code> (not yet implemented)
</p><p>
The following tag types can only be used in entry source file headers.
</p><p>
<code>created:</code>
The date at which the entry was first created. Any string is accepted. Any numerical date format in descending order works for sorting of entries as long as every
entry uses the same format. It is recommented to use the ISO style date formt YYYY-MM-DD.
Example: <code>created:2020-12-29</code>
</p><p>
<code>edited:</code>
The date at which the entry has been edited last. This is not updated automatically unless you use an editor that edits the line automatically. Any string is
accepted. Any numerical date format in descending order works for sorting of entries as long as every entry uses the same format. The value overwrites the created
date in sorting entries. It is recommented to use the ISO style date formt YYYY-MM-DD.
Example: <code>edited:2021-05-05</code>
</p><p>
<code>sort:</code>
A value that overwrites both the edited and the created date in sorting entries. The value is not displayed. Values from edited: and created: will be ignored when a
sort: tag is present. It is recommented to use the ISO style date formt YYYY-MM-DD when the sort tag is used to place an entry in between other entries that use
the same format for created/edited dates. If numerical values are used for created and edited dates, then a sort value that starts with a letter will sort an entry
on top of the blog view. If the value of a sort: tag starts with "about" or "stick" then the entry's title-wrapper is not included in the output file. This can be
used to create stickied entrys (paragraphs that are displayed above all entries on certain tagpages). See the "Sorting" section below for more details.
Example: <code>sort:stickied</code> will place the entry content (without meta information) above all other, non-stickied, content on the tagpages of every cat: tag that is
included in the header.
</p><p>
<code>cat:</code>
A category the entry will be filed under. An entry can have any number of category tags.
Example: <code>cat:Dogs</code> marks an entry that contains something relating to dogs. A tagpage that lists all entries with this tag will be generated.
</p><p>
<code>top:</code>
A topic that is adressed by this entry. An entry can have multiple topics and/or sub-topics. A sub-topic is assigned by adding another colon after a topic name, 
followed by the sub-topic name. Topic tagpages are indexes of entries with a specific topic tag or a sub-topic tag of that topic tag.
Example: <code>top:Science:Mathematics</code> will include the entry's title in the topic tagpages/indexes "Science" and "Science:Mathematics".
</p><p>
<code>lang:</code>
The language the entry is written in. Any string is accepted. You can use <code>lang:en</code> or <code>lang:English</code> or <code>lang:ENG</code> or whatever you like, as long as entries of the
same language use the same tag. Only one language tag per entry is allowed.
Example: <code>lang:gr</code> tags an entry as being written in Greek.
</p><p>
<code>author:</code>
The name of the author of the entry. If only one person is adding entries to the web site then it is best to ignore this tag type and not include it in any entry
header. Every author name that is used in at least one entry will be listed in the navigation bar to offer to display only entries written by this author.
Example: <code>author:Nickname7000</code>
</p><p>
<code>re:</code>
The name of an entry this entry is connected to. Includes a note at the top of the entry, linking to the entry named in the re: tag.
Example: <code>re:some_entry</code> links the entry that has this tag to the entry with the filename "some_entry".
</p><p>
<code>ref:</code>
The name of an entry this entry is referring to. Includes a note at the top of the entry, linking to the entry named in the ref: tag.
Example: <code>ref:entry0815</code> links the entry that has this tag to the entry with the filename "entry0815".
</p><p>
<code>reply:</code>
The name of an entry this entry is a reply to. Includes a note at the top of the entry, linking to the entry named in the reply: tag.
Example: <code>reply:Some Questions</code> links the entry that has this tag to the entry with the filename "Some Questions".
</p><p>
<code>redirect:</code>
The name of an entry this entry will redirect to. The content below the entry header will not be displayed on the web site (but will still be included in the RSS
feed). Visitng this entry's page will redirect the browser to the entry with the file name in the redirect: tag. On tagpages the entry will be substituted with the
entry it is redirecting to. This can for example be used to link multiple galleries to the same entry by creating dummy entries with the names of the galleries.
Example: <code>redirect:some_entry</code>
</p>
