fyyd podcast shortcodes
Blogging about podcasts is a thing now. Of course it’s good practice to link to the podcast’s website and include some additional information, maybe inside an information block.
This plugin provides shortcodes to display podcasts’ information inside your blogposts. This includes general information about the podcast and single episodes’ information, including the option of an HTML5 audioplayer for those episodes. In addition there are infoboxes for collections and curations.
To get the data needed, the plugin makes use of podcasts’ data provided by fyyd.de, a podcast directory and service point. fyyd’s API (https://github.com/eazyliving/fyyd-api) is the interface to all those podcasts.
All displayed content is dynamically fetched by the clients browser, there’s no server-side action/caching/etc…
This plugin provides shortcodes to include infoboxes for
[fyyd-podcast podcast_id=57585] [fyyd-podcast podcast_slug=silence] [fyyd-podcast podcast_slug=silence color=#008000] [fyyd url=https://fyyd.de/podcast/silence]
episodes (optional with HTML5 audioplayer)
[fyyd-episode episode_id=3970971] [fyyd-episode episode_id=latest podcast_slug=silence] [fyyd-episode episode_id=3970971 color=#008000] [fyyd-episode podcast_slug=anerzaehlt player=true] [fyyd url=https://fyyd.de/episode/3989950]
You can set episode_id to “latest” or leave it out to provide the latest episode published. In this case you have to provide the podcast_id or podcast_slug of the podcast.
For podcasts and episode you can provide a background color (#rrggbb). Default when left out is the dominant color of the podcast’s logo.
curations (custom feeds with episodes from different podcasts)
collections (podcasts collected under a certain topic)
To create and manage curations and collections, you need to have an account at fyyd.de.
This plugin provides 1 block.
Upload the contents of the plugins zip-archive to the
Activate the plugin through the ‘Plugins’ menu in WordPress
Does this plugin require some kind of authentification for the API?
No, the API-requests used are open to all without any authentification.