-
Notifications
You must be signed in to change notification settings - Fork 30
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
Player enhancements #191
Comments
@Sidsector9 I'm unassigning you here as there doesn't appear to be a WIP PR, so moving this out for others to pick up and work on |
Some good examples in https://wordpress.org/plugins/podcast-player/ |
@jeffpaul I think implementing the whole checklist in a single PR will be more maintainable. Because these content's should be organized in a single wrapper element and design structure. |
@jayedul if you've got the time and interest, go for it! |
Another good example: https://portlandartmuseum.org/podcast/black-artists-of-oregon-episode-1/ |
Quick followup on the prior art on WAMU's site referenced in #299 In addition to the player being persistent, the ability to play on-demand podcasts AND live radio streams is key. Not sure if that would make sense for a plugin focused on podcasting, but possibly as a stand-alone persistent audio player? Either way, we'd like to include the plugin and the persistent player(s) in the Newspack branches maintained by OpenProducer (see OpenProducer/newspack-platform#22) and would love to contribute/help where we can. |
Is your enhancement related to a problem? Please describe.
The existing player that is used with the plugin is the default core audio player with no additional enhancements even with various toggles/metadata set in the podcast block settings:
It might be nice to enhance the player to support the following functions:
Open to any/all of these items to roll into their own PR, best to update each item above with any linked PR # at the end of the line to better track completion of the work.
Designs
No response
Describe alternatives you've considered
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: