it regenerates static html files for articles that are just before and
after newly added and deleted articles (this to maintain the
"previous" and "next" links alive),
-
it regenerates the archives.html, tags.html, and feed.xml files,
+
it regenerates the archives.html, tags.html, atom.xml, and rss.xml
+ files,
and finally it copies the static html file of the last article to
"index.html".
- The foreach loop construct is specific to the archives.html, tags.html, and
- feed.xml templates and will therefore be described at the same time. Where
- available, the loops are processed right after the includes.
+ The foreach loop construct is specific to the archives.html, tags.html,
+ atom.xml, and rss.xml templates and will therefore be described at the same
+ time. Where available, the loops are processed right after the includes.
The syntax of the conditional construct is as follows:
@@ -195,8 +196,8 @@ fugitive: README
page_title
Its value is "archives" in the archives.html template,
- "feed" in the feed.xml template, or the article title in the
- article.html template.
+ "feed" in the atom.xml and rss.xml template, or the article title
+ in the article.html template.
blog_url
@@ -373,7 +374,7 @@ fugitive: README
Its value is the title of the next article ordered by publication date.
-
foreach loops in archives.html and feed.xml:
+
foreach loops in archives.html, atom.xml, and rss.xml:
Two foreach loops are available: foreach:article
and foreach:commit. The syntax is as follows:
@@ -389,8 +390,9 @@ fugitive: README
set in accordance with the commit each time.
<?fugitive endforeach:commit ?>
- The only difference between the archives.html and feed.xml templates is that
- in feed.xml these constructs only loop on the five last articles and commits.
+ The only difference between the archives.html, atom.xml, and rss.xml
+ templates is that in atom.xml and rss.xml these constructs only loop on the
+ five last articles and commits.