Print full post content in RSS description #41
Conversation
As gmnhg right now doesn't generate post summary, using post content as RSS post description source seems like our best bet. Right now gmnhg will generate RSS with empty descriptions.
cmd/gmnhg/templates.go
Outdated
| @@ -79,7 +79,7 @@ var defaultRssTemplate = mustParseTmpl("rss", `{{- $Site := .Site -}} | |||
| <link>{{ $AbsURL }}</link> | |||
| <pubDate>{{ $p.Metadata.Date.Format "Mon, 02 Jan 2006 15:04:05 -0700" }}</pubDate> | |||
| <guid>{{ $AbsURL }}</guid> | |||
| <description>{{ html $p.Metadata.Summary }}</description> | |||
| <description>{{ printf "%s" $p.Post }}</description> | |||
There was a problem hiding this comment.
By default Hugo uses the post's "summary" front matter if it exists (that's what is loaded into Metadata.Summary), then it falls back to an auto-generated summary. It should be fine to put in the full post data since people can override the defaults, but I wanted to mention that here.
There was a problem hiding this comment.
Yes, but the difference between us and Hugo is that Hugo autogenerates a summary unlike us.
There was a problem hiding this comment.
Exactly. I write my own summaries and put it into the front matter (I don't particularly like Hugo's autogenerated summaries), but as long as Metadata.Summary remains available, I can make a custom template that uses the summary data. Or who knows, maybe I should use the default and put the whole post content into RSS.
There was a problem hiding this comment.
The thing I never thought of: since RSS is XML, raw post content which might contain XML has to be escaped.
There was a problem hiding this comment.
Good catch, yep, gemtext may contain XML content. Passing it through the escaper should be enough.
As gmnhg right now doesn't generate post summary, using post content as RSS post description source seems like our best bet. Right now gmnhg will generate RSS with empty descriptions.