-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RSS feed generation, workflow, pipeline #108
Comments
Here's my understanding of the future publishing process. I'm not entirely sure whether that's the plan or not, so please correct my if I'm wrong:
Now, taking all that in mind here's the answer for your question: Hugo can generate basically any custom output format. What would we need to build is the template for the rss xml file using the variables from the JSON front-matter of each episode. It's very similar now the HTML pages are created using the templates from the JB theme folder, but inside it would be XML. The current json (in which all the data created by the scraper) might be missing some things that we would need for the RSS. Will need to take a closer look at the current RSS of the shows, the new standards from podcasting index, and add anything that might be missing. I'll go over it tomorrow. |
We do generate RSS / Podcatcher compatible feeds already: All Shows: https://jupiterbroadcasting.net/show/index.xml The template file for this is here: https://github.com/JupiterBroadcasting/jupiterbroadcasting.com/blob/main/themes/jb/layouts/section/list.rss.xml |
I didn't even know we had that already implemented. That's great! I think we do need to modify the template a little to include a bunch of those new tags from Podcastingindex 2.0 namespace This might need to be a separate issue, but somewhat related here: |
Here's what we discussed and decided for now internally at JB regarding RSS feeds for JB.com 1.0:
So! The above are all great ideas, and will certainly be revisited in time. |
What Brent said. But I figured I'd share a bit more background with you all. I'm going to try and talk about this in Office Hours 8 a bit for those of you who want more info/context than I can put in text, but I wanted to post our current plans for RSS generation. RSS feed generation for the podcasts is a bit more complicated than it might look at first pass. Each show has quite a few feeds, each with various end-use cases in mind. Take LUP for example:
👆 That's just one show off the top of my head. And not even the most complicated. And the features those feeds support IE Podcasting 2.0 namespaces are still in flux right now. We are going to be adding more and more P2.0 feature support this year and next. Additionally, things get even more complex once we start using the Podcasting 2.0 live tag. Which requires an update to the show's RSS feed (and the all shows feeds) when:
👆 Each one of those will require whichever Podcast is going live to have its feed updated 3 times, without any episode, or web page ever being updated. We also want the flexibility in the future of being able to offer meta-feeds, ie, a "Linux only feed" or "interviews feed", etc. So while we could generate one (or maybe more) of the feeds using the website, it would just add fragmentation to how we build the RSS feeds and not functionally ideal for JB. I could TOTALLY see it working in some setups. IE, if we had a simpler lineup, fewer shows/feeds, etc. |
Ya...wow...while really informative (thank you for the background (I love hearing this type of info, because it helps drive the technical solution) 😁) , that's a lot 😅 There's a couple ( or at least one) that I can think of off hand, but I'll post it after I finish work today (to let the info percolate and validate I'm understanding things properly). About this part (note for myself):
My first thoughts is that it should be a python script in a separate repo like how the scraper is. |
So, @gerbrent meta question for this issue...should this issue still be a 1.0 task? Should we create another issue for 1.0 saying point to fireside for the RSS feeds, or keep it all here? |
good point, it was in the milestone for decision making, lets make a new issue for the implementation. |
The BIG question: how will the RSS feed generation pipeline function, in a best-case scenario?
from devotoare:
The text was updated successfully, but these errors were encountered: