Skip to content
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

[ENHANCEMENT] - Podcast 2.0 namespaces #391

Open
rastacalavera opened this issue Oct 13, 2022 · 5 comments
Open

[ENHANCEMENT] - Podcast 2.0 namespaces #391

rastacalavera opened this issue Oct 13, 2022 · 5 comments

Comments

@rastacalavera
Copy link
Contributor

rastacalavera commented Oct 13, 2022

Hey Matt,

I have been learning a LOT by figuring out how to use your theme, Hugo and git and just want to say a very heart felt thank you.

My podcast took a bit of a break during Covid, but now I am trying to bring it back. I have been listening to various podcasts that are involved in the 2.0 movement and would like to find a way to help incorporate some of the name spaces into your project if you're interested.

I don't think it would be that hard to do, i just can't figure out where to start. I think adding the value tag would be a good first step. I found an old 2015 post from you when you were trying to figure out the RSS generation for Castanet. I looked in the layouts/ folder of Castanet but didn't see any rss.xml file.
EDIT
Found the rss generator file here castanet/layout/section/episode.rss.xml

I think what needs to be done is a base value set using the user's config.toml and then as a per episode option, there could be front matter for the host/guest to include their wallet address in the value tag.

Value tags at the <item> level of the RSS over ride the <channnel> so if a guest/co-host doesn't have a value tag associated with them, the defaults would take over.

I normally work on Gitlab, but I'll move some of my work over to Github and make a pod-2.0 branch to play with. Any advice or insight you can provide would be awesome.

Thanks!

@rastacalavera
Copy link
Contributor Author

I've been playing around with transcripts and I have an idea on how to do it but I'm not sure it's the best idea.

I am thinking that there needs to be a an item tag in the episode.rrs.xml file that would look something like this:

          <podcast:transcript url= {{ ".pod2_transcript" }} type="application/srt"/>

I referenced that from the podcasting 2.0 RSS feed and in addition to this, i think there might need to be a new archetype added to the episode.md file that would distinguish this from the other plan text transcript option. That is why I went with pod2_transcript shown in the item tag. I just don't know how to fully marry the two together. . .

  • can you have "" in the double's and have it render out correctly or do they need to be escaped in the front matter or somewhere else?
  • is it enough to create a front matter object in the archetype and then attempt to call it in the episode.rss.xml file? I am trying to learn Hugo and am unsure of this.
  • Should this be a fully qualified URL, if hosted somewhere else or a relative url to the base like with images and such?

@rastacalavera
Copy link
Contributor Author

Well, I have a hacky of doing it at this point:
image

I made new front matter in the archetype for episode and then added this to the episode.rss.xml

        <podcast:transcript> url = "{{ .Params.pod2_transcript }}" type="application/srt"</podcast:transcript>

Then in the individual episode front matter, I added this

pod2_transcript = "https://linuxlemming.com/files/Edit00.srt" #WIP to get transcripts working

@rastacalavera
Copy link
Contributor Author

This was wrong
podcast:transcript url = "{{ .Params.pod2_transcript }}" type="application/srt"</podcast:transcript>
it needs to just be
podcast:transcript url = "{{ .Params.pod2_transcript }}" type="application/srt"/>

@rastacalavera
Copy link
Contributor Author

Also added chapters!
<podcast:chapters url = "{{ .Params.pod2_chapters }}" type="application/json"/>

@mattstratton
Copy link
Owner

My apologies for not seeing this until today! This is very interesting and I'll read up some more on what you've been doing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants