blob: 412148a33151168b4b76bea3819296e324244f8b (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
<!--
This is based on Yandex's https://yandex.com/support/zen/website/rss-modify.html
The scope of this segment is the LOCAL scope (page variables). For instance 'rss_title'.
Notes:
* the local var rss_description (or rss) *must* be given otherwise the item
is not generated.
* rss_title if not given is inferred from page title
* rss_pubdate if not given is inferred from the date of last modification
* the full content is not added by default but can be if the variable rss_full_content
is set to true (either globally or locally).
* RFC822 or RFC1123 is a date format required by RSS.
* there is debate about supporting one or several enclosures
(see https://www.rssboard.org/rss-profile#element-channel-item-enclosure).
We use the conservative 'only one' approach by default but you could tweak this by
defining your own `rss_enclosures` variable with a list of string and use that.
-->
<item>
<title><![CDATA[{{fd2rss rss_title}}]]></title>
<link>{{fd_full_url}}</link>
<guid>{{fd_full_url}}</guid>
<description><![CDATA[{{fd2rss rss_description}}]]></description>
<!-- note that fd_page_html is already HTML, so we don't use fd2rss here -->
{{if rss_full_content}}
<content:encoded>
<![CDATA[{{fix_relative_links fd_page_html}}]]>
</content:encoded>
{{end}}
<!-- RFC1123 enforces a RSS-compliant date formatting -->
<pubDate>{{RFC822 rss_pubdate}}</pubDate>
{{isnotempty rss_author}}<author>{{rss_author}}</author>{{end}}
{{isnotempty author}}
<atom:author>
<atom:name>{{author}}</atom:name>
</atom:author>
{{end}}
{{isnotempty rss_category}}<category>{{rss_category}}</category>{{end}}
{{isnotempty rss_comments}}<comments>{{rss_comments}}</comments>{{end}}
{{isnotempty rss_enclosure}}<enclosure>{{rss_enclosure}}</enclosure>{{end}}
</item>
|
