mattstratton/castanet

Add support for transcriptions

Closed this issue · 9 comments

It would be super helpful to have a frontmatter field for an episode that was a link to the transcript for the episode.

Updating to add - this now also will include the ability to programmatically include transcripts in full on the episode pages.

So also thinking about this a little bit more...it might be interesting to add a page type that is "transcription", so that the link would be to a page on your site (the field should support the concept of either linking externally or to site page, etc).

The transcription page would probably be relatively simple - you would paste in the transcription as the "content", but what I'm imagining is something where it's like this:

episode
- myepisode.md
transcripts
- myepisode.md

If you mark in the frontmatter transcript = "true for example, it would generate the transcription link to transcripts/myepisode based on the shortname of the ep (so they would have to match).

The transcription page would probably be a simple page with just the transcription content.

I really do go back and forth on whether the transcripts should be embedded on the main show notes page or not. See https://twitter.com/theDanielJLewis/status/1223042966618624002 for reference.

Twitter
@mattstratton I've said it in different places. Essentially, it's long content but low-quality writing and thus doesn't help much with SEO.

It's better than nothing, and about the same as basic show notes. But I still find article format to be the best for SEO.”

Some references for how transcripts can be shown:

Inline:

Linked:

The Podcast Host
On this episode of Podcraft, I'm talking to Nicolas Steenhout from the A11Y Rules Podcast. Nicolas is an accessiblity evangelist, helping anyone he can to improve their online content's accesibility. I loved his top-line advice around the all-round benefits of being familiar with accessibility: A little time spent learning the basics of accessibility can help…
Last Week in AWS
Jen Simmons—Designer Advocate at Mozilla, creator of Firefox Grid Inspector, host of Layout Land and The Web Ahead, member of the CSS Working Group, coiner of Intrinsic Web Design, and general force of nature—is Jeffrey Zeldman’s guest.

My initial research is showing that podcast hosts are coming in on the side of "having the full transcript as a section in the show notes" but we should probably do the "show more" button approach that screaming in the cloud does...

For reference, it looks like this on Screaming in the Cloud:
image

I think for this to work, you might have to have a section in the show notes that was marked as the transcript somehow.

OR! make a shortcode to "display transcript" and it would either take the name of the transcript file (or read it from the frontmatter) and then generate the html for it. That might be a better move.

For what it's worth, here's how it might look if it was a linked transcript:
https://www.arresteddevops.com/chatops

Matt & Trevor sit down with Jason Hand (VictorOps), Sasha Rosenbaum (10th Magnitude), and Peter Burkholder (Chef) to discuss ChatOps.

Having a shortcode is definitely the way to go. The problem will be that it will lose formatting, I suppose, when it's including that other file (so if you had html/markdown formatted transcripts, they won't work).

I think the other way might be to somehow tag the transcript section of the show notes; you'd have to use HTML for it and make sure they had a certain ID (if you want the "hide/show show notes" button thing to work.

Aha! You can have shortcodes deal with markdown properly - https://gohugo.io/content-management/shortcodes/#shortcodes-with-markdown

Shortcodes are simple snippets inside your content files calling built-in or custom templates.

I think I have a good start with this, which we can start using and see how it goes.

You can see a demo at https://deploy-preview-275--sample-castanet.netlify.app/sept/

The trick is that you need the transcript files somewhere; the static directory is the best place, I think.

The hardest part is taking whatever you get from your transcription service and turning them into Markdown/html. I was using https://euangoddard.github.io/clipboard2markdown/ for that.

Bootstrapping alpha seed money scrum project. Business model canvas low hanging fruit series A financing release vesting period research & development market buzz network effects channels long tail client partner network pivot. Innovator market android buyer gamification. User experience gamification interaction design sales. Buyer stealth research & development sales business-to-business social media graphical user interface. Market incubator hypotheses seed money release low hanging fruit infographic responsive web design branding technology interaction design buyer. Ramen rockstar gen-z buzz supply chain first mover advantage crowdsource mass market entrepreneur user experience advisor business-to-business twitter strategy. Termsheet low hanging fruit lean startup crowdfunding customer. Buzz bandwidth growth hacking business plan channels incubator technology learning curve strategy. Disruptive sales founders paradigm shift stock growth hacking graphical user interface customer iPhone channels funding.