The Indieweb called "sidefiles" an antipattern, mostly because a strong allergy to DRY. I find it a little bit overblown and sometimes suspect it is a result of

The Indieweb called "sidefiles" an antipattern, mostly because a strong allergy to DRY. I find it a little bit overblown and sometimes suspect it is a result of Tantek Çelik’s CMS. https://indieweb.org/sidefile-antipattern https://indieweb.org/sidefile-antipattern But of course there were ideas to embed the feed data structure directly in HTML as attributes. In the indieweb/microformats corner there is h-feed which could simply be extended with rel=enclosure links for an embedded podcast feed. https://indieweb.org/h-feed https://indieweb.org/h-feed And more formal side you could use RFDa/Microdata and the schema.org vocabulary to annotate the HTML with the logical properties of a feed and podcast episodes: https://schema.org/PodcastEpisode https://schema.org/PodcastEpisode Of course there aren’t any podcatchers with understand these vocabularies. ... I’m a little bit torn. I love good minimal markup and have a soft spot for the idea of RDFa. An early 2000s idealist. But the real world is different. Netscape’s original RSS came out of a clear need: the markup for table layout of the late 90s was shit and not generally parsable. Which is the same thing today: Today’s markup a wastelands of nested divs which are not generally parsable and often generated by tools nobody really has control over. Just today I had to wade through a Wordpress site builder plugin and its crappy visually generated HTML. That’s the majority of the web, sadly.