nerdhaus / eleventy-podcast Goto Github PK

We want to add some extra CMS widgets, so we need to do some fancy things and build it ourselves. The NetlifyCMS site has instructions but our stripped-down site skeleton doesn't have any JS/SASS tooling yet.

Once we get that in place, we'll probably just need to change the /admin.index.html file to point to our custom built version of the file.

Some of the data types we'll be using for managing Podcast data are trashy to edit using the builtin widgets. Options for improving the creation/editing experience include:

• UUID Widget for episode GUIDs
• Nested Select could be handy for iTunes categories
• Conditional Widget would let us hide complicated frontmatter or data file options when they're unneeded.

Right now the project is structured with the assumption that hosting will happen on Netlify. Things that would probably need to change include:

• netlify.toml equivalent settings for other services
• File storage integration with AWS? This would be a huge lift, maybe not justified.
• Branch defaults and build.js updates to capture non-Netlify context settings

No gameplan for the landing page yet, but it should be structured such that it offers some documentation about the eleventy-podcast project, while allowing a user to update the content and produce an acceptable podcast home page.

Review some other standalone podcast sites to see how they handle "Home Page" versus "Episode List Page."

We may want a custom home page template with frontmatter switches to control how the page is built.

Out of box we're using the vanilla "media library" configuration for NetlifyCMS that stores everything (images, mp3s, etc) in an uploads folder in the git repo itself. It works for the demo site and is probably even fine for some simple podcasts but it'd be great to handle things better for more complex ones.

Issues to consider:

• NetlifyCMS integration — add a media provider or just turn off library management and let them enter the mp3 filepath as a string?
• Filesize/Duration detection — we're using an eleventy plugin that checks local files, moving to external hosting would require fancier treatment or manual entry of size/duration in the episode frontmatter. We have properties for that but it feels like better handling would be nice.
• URL Generation — it'd be nice if the remote/local question was abstracted away by the time "what's the URL for this podcast episode" is asked at the template level. Maybe a helper filter or shortcode that wraps all of the if/then checking.

Anticipating three episode-related templates:

• Dedicated page for a single episode. Include full show notes, etc.
• Featured Episode template for episode lists
• Normal Episode template for episode lists

On the general episode listing page, the most recent episode would use the Featured template while all others would use the Normal template.