Closed slyeargin closed 1 year ago
I think the idea is good and well scoped. There are some issues with the RFC itself that I'd like to see cleaned up, but assuming that can be done I would be in favor of this.
Forgive me if this is a naive question, but is <content:encoded>
a valid element in RSS 2.0? I don't see it in the list of item subelements, but it is mentioned here for 1.0.
I would not want to publish the compiled content that's rendered by Astro for the following reasons:
Ideally, I'd want a separate markdown pipeline to generate the HTML optimised for syndication.
This feature was added to @astrojs/rss
in 1.6.14
with a different API than this RFC suggests. As a result, this can probably be closed.
@naiyerasif: Full content is opt-in, so you don't need to include it if you don't want.
Summary
Updating @astrojs/rss to generate feeds that include full
compiledContext()
strings ascontent:encoded
in the XML, given a parameter ofcontentLength
with a value offull
. (This value would default tosummary
, which is the current default behavior.)Links