stefans-o / jupiterbroadcasting-hugo-mvp Goto Github PK

naming convention for Shows should be consistent, either:

JB shorthand:

• coder
• extras
• lan or LAN
• lup or LUP
• office
• ssh or SSH

lower-kebab-case:

(likely the better choice)

• coder-radio
• extras
• linux-action-news
• linux-unplugged
• office-hours
• self-hosted

currently - a mix of naming conventions

/content/coderradio
/content/extras
../linux-action-news
../linuxun
../officehours
../selfhosted

make all content also available via JSON

https://podlove.org/podlove-web-player/#features

Once the Frontmatter for episodes is figured out, create archtypes for episodes

Currently markdown formatting in body of index.md appears to render html correctly (lists, headers, links).

However, no formatting is applied despite the code.

This could be a theming issue.

Can we please add basic formatting to the theming to facilitate page content editing? Currently text appears as an unformatted blob.

To Reproduce:

edit the "Archive" index.md with formatting as below, and observe no formatting applied to live webpage:

# title
* list item 1
* list item 2

## subtitle
text without formatting
[link](http://example.com)

Consider using the Podverse embedded player to enable/facilitate Podcasting 2.0 features such as boosts/v4v, clips, chapters, etc.

demo: https://podverse.fm/embed/player-demo

code: https://github.com/podverse/podverse-web/pull/820/files

Value-4-value

This widget connects to your WebLN compatible browser extension to allow you to send Bitcoin over the Lightning Network to content creators.

Output tags in episode, tag list page

figure out a good way to integrate search. Clientside like Lunr.js will probably not perform due to index size.

shows like Beer is tasty missing a lot of videos due to blip.tv shut down.
Extract those from archive.org

right now it's only one static link in the single template of an episode

use paginator... basically on each listing page :D

make Sponsors managable like hosts

add management of guests

Build also own sites for each show with own TLD.
Might work with different build pipelines and different configs.

Also shared content for guests, hosts, sponsors

start with 1TB and than scale up

integrate Blog

Since the README makes mention of a TBD for Docker, I went ahead and created a basic Dockerfile and docker-compose.yml that will enable building the static site and copying it over to an nginx container for deployment. This will need to be refined over time once the final decision about container registry is determined.

My PR:
#26