RSS feed for listing page with multiple listings and YAML listing content

[blenback]

Description

Hello, I am trying to add an RSS feed to a listing page on a quarto website. The website already has two other listing pages with functioning feeds (for presentations and a blog) however this last listing page is slightly different as it contains multiple listings and the listing contents are created as inputs in the YAML. A repro would be like this:

---
title: "Publications"
page-layout: full
title-block-banner: false
format: 
  html: 
    css: css/publications.css
listing:
  - id: Journal-articles
    template: publication.ejs
    contents:
    - name: Archetypes
      title: test
      Authors: Wicki, S., <b>Black, B</b>., Kurmann, M., Grêt-Regamey, A.
      Title: Archetypes of social-ecological-technological systems for managing ecological infrastructure.
      Journal: Environ. Res. Lett.
      href: https://doi.org/10.1088/1748-9326/ad1080
      Bibtex: media/Archetypes.bib
  - id: Theses
    template: publication.ejs
    contents:
    - name: MSc
      Authors: <b>Black, B</b>.
      Title: "Assessing the ecological effectiveness of protected areas in Cambodia: a quasi-experimental counterfactual estimation of avoided deforestation."
      Journal: Masters thesis. Central European University.
      href: https://doi.org/10.13140/RG.2.2.28621.10727
      Bibtex: media/MSc_thesis.bib
    feed: true
---

An rss file is created (docs/publications.xml) when the page is rendered but it does not contain the listing contents:

<?xml version="1.0" encoding="UTF-8"?>
<rss  xmlns:atom="http://www.w3.org/2005/Atom" 
      xmlns:media="http://search.yahoo.com/mrss/" 
      xmlns:content="http://purl.org/rss/1.0/modules/content/" 
      xmlns:dc="http://purl.org/dc/elements/1.1/" 
      version="2.0">
<channel>
<title>Ben&lt;br&gt;Black</title>
<link>https://blenback.github.io/publications.html</link>
<atom:link href="https://blenback.github.io/publications.xml" rel="self" type="application/rss+xml"/>
<description>Personal website for Ben Black</description>
<generator>quarto-1.3.450</generator>
<lastBuildDate>Fri, 29 Dec 2023 09:22:08 GMT</lastBuildDate>
</channel>
</rss>

I also tried to put feed:true as an indented option under one of the listing - id:'s

Quarto version: 1.3.450
OS: Version: Windows 10.0.19045 Build 19045
Rstudio: 2023.09.1 Build 494

[mcanouil]

Could you actually share a Git repository?

[mcanouil]

Your repository is invalid and cannot be rendered.

[blenback]

Fixed with a push now. Thanks for your help.

[mcanouil]

Could you fix your link?
Your website has some serious accesibility concerns.

I am not familiar with RSS and less in the context of listings.
Maybe @dragonstyle can chime in.

[dragonstyle]

Feeds don't really know how to deal with completely arbitrary items - RSS requires a specific set of fields and it would be difficult to map arbitrary items into an RSS feed without knowing a lot about them.

As a result, we will only include items in feeds if they minimally contain a name and an href (without those, the feed item wouldn't be useful in any real to readers). We'll use an item description, authors, and image if available.

You'll need to specify those fields above specifically in your YAML for the various listings items if you'd like them to be included in feeds.

HTH!

[blenback]

@mcanouil sorry, I'm not sure I understand, could you expand on what you mean by accessibility concerns? Thanks, for the help.

[mcanouil]

We cannot see the titles in your navbar, take a look at the screenshot.
it's the result of a build using 1.4 release candidate on your repository.

And your link (in your post) is bad (it does not link to what is written):

Also when sharing a repository, share it's root without tree/BRANCH unless the branch matters (not the default).

[blenback]

Ah thanks, I can't see this behaviour when viewing the actual website but I will look into it. Thanks for advice, I'm still new to Github and want to learn.

[mcanouil]

You are welcome.
Your website might be rendered using 1.3, so you have a bit of time to avoid breaking your website unintentionally when upgrading to the future 1.4 release (soonish).