[askhan]

This entire post has galvanized me to write up an idea I've been noodling over as I work on a reader myself: a standard that would eliminate precisely the waste you mention by specifying within the HTML all that's needed for a feed.

See https://sfeed.org. In the spirit of the multi-meaninged RSS acronym itself, the S might stand for scrape, selector, speed, or of course Scotty.

Vinni, might you be interested in enabling the standard in Feed Me Up?

[Vinnl]

There already is such a standard! https://microformats.org/wiki/hatom

Happy to take a merge request that adds the option to set `extends = "sfeed"` or `extends = "hatom"` and then automatically sets the correct selectors though.

(That said, if a publisher goes through the trouble of adhering to those selectors, they might as well publish a feed while they're at it :)

[detaro]

https://microformats.org/wiki/h-feed is the up-to-date version

[askhan]

I like this name better — the h prefix is cool in that it shows things are coming all the way from basic HTML.

Microformats, I see this is the proper way.

[Vinnl]

Ah thanks - been out of that world for a long time now.

[askhan]

Ah thanks, didn't know about hAtom, will investigate that.

I do think it's (much) easier to add some HTML classes than output an entire separate file.

I've been using Nuxt + Strapi as my new CMS stack, and while it's a big step forward in so many other ways, outputting an RSS feed is far from automatic.