Skip to content

RSS Feed Generation #7290

@dragonstyle

Description

@dragonstyle

Discussed in #7280

Originally posted by prncevince October 18, 2023

Description

Quarto Website Document Listing Feeds Reference:

It appears that the following option includes a large portion of the HTML webpage (everything in <main> after <header>) in the <item><description> tag/node of an RSS feed document XML format document:

listing:
  feed:
    type: full

Additionally, it appears that the following option includes the contents of the first <p> encountered after <main><header> HTML tag within <item><description> of the XML:

listing:
  feed:
    type: partial

This can significantly reduce the amount of HTML content pushed to the RSS feed XML document.

Additionally, options like YAML header metadata descriptions for listing item pages do not get pushed to the RSS feed file in either of these options.

I'm new to the RSS feed game, but I believe that storing rich content (e.g. iframes from widgets) may be overkill. This can produce very large RSS feeds that popular RSS readers (e.g. Feedly), do not actually parse. Additionally, if the goal is to generate additional custom content automatically from the RSS feed (e.g. a newsletter), this type of content may not be desired.

I guess that one could run a post processing text parsing script on their Quarto project to remove such content from the <description><![CDATA[[ ...]]></description> XML tag using project:post-render.

Or maybe more options could be built-in to base Quarto as extra listing:feed:type options?

Or possible, a listing:feed:remove field can be added to selectively remove rich content based on scraping search matches?

e.g. [no-iframes, no-social-embeds, etc.]

Thoughts? Thanks!

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions