Weave Code
Podcast Categories Laravel Package
statamic/podcast-categories
Statamic addon for managing podcast categories in the control panel. Adds a fieldtype for selecting Apple Podcasts categories and subcategories, making it easy to tag episodes or shows with accurate podcast metadata.
At a glance
Frequently asked questions about Podcast Categories
- What does statamic/podcast-categories actually do?
- It is a Statamic addon that bundles Apple's podcast category taxonomy and exposes it as a control panel fieldtype, so editors can pick canonical category and subcategory values that flow into your podcast RSS feed. The integration surface is the Statamic CMS, not an independent PHP service. It is not a generic Laravel library you would pull into a non-Statamic app.
- Which Statamic and Laravel versions does it support?
- Version 2.0.0 is explicitly a Statamic 6 compatibility release, so it only applies if your site is on Statamic 6 or you are migrating this cycle. On Statamic 4 or 5 the v2 line does not apply, and the v1 line is effectively an unmaintained branch. Check the exact composer.json constraints for Statamic, Laravel, and PHP in the tag you install rather than assuming.
- How do I install statamic/podcast-categories?
- Run composer require statamic/podcast-categories and let Statamic's addon autoregistration pick it up, then add the fieldtype to the relevant blueprints and optionally republish its config. There is no external API, no credentials, no queue, and no storage concern, so the mechanical setup is trivial. Realistic effort is a few hours of engineering plus an editorial pass, not a project.
- How do I add podcast categories to an episode or show blueprint?
- Add a field using the addon's fieldtype handle to the blueprint YAML for your show or episode collection, either through the control panel blueprint editor or by editing the file directly. Editors then choose a category and subcategory from the Apple taxonomy when saving an entry, and those stored values can be rendered into your feed template. Verify the stored value shape before writing feed markup.
- Does this package call the Apple Podcasts API or need an API key?
- No. The Apple category taxonomy is bundled with the addon as static data, so there are no external requests, credentials, or rate limits to manage. That also means the list only changes when the addon is updated, which is the main reason to care about maintenance.
- Does it work on Statamic 4 or 5?
- Not at v2.0.0, which is a Statamic 6 compatibility release. On Statamic 4 or 5 you would have to adopt the latest v1 tag and log an end-of-support date, or defer adoption entirely. Classify your stack fit before doing any evaluation work, because the answer changes the whole plan.
- Will upgrading from v1 to v2 break my existing field data?
- No upgrade guide is published, so assume none exists and verify by diff. Pin the currently installed version explicitly, diff composer.json between your installed v1 tag and v2.0.0, and diff the package source for renamed config keys, changed field config options, and changed stored value shape. Confirm whether a migration or reindex step is needed on a scratch branch before rolling out.
- How do I check whether other addons block the v2 upgrade?
- Run composer why-not statamic/podcast-categories 2.0.0 in a scratch branch to surface sibling addons that pin Statamic 5 and would deadlock resolution. That is the cheapest possible failure and should happen before you write any code. Only then diff the constraints and plan the migration.
- Is there a test suite or CI matrix I can rely on?
- There is no visible test suite and no published CI matrix, so you own correctness verification. Write a smoke test that saves an entry with a category value, asserts the stored shape, and renders it into your podcast feed. Given the small blast radius, that is a reasonable cost, but it is a cost you absorb rather than borrow from the maintainer.
- Should I use this addon or just vendor the Apple category list myself?
- The durable asset here is a static, publicly documented taxonomy; the code around it is a thin fieldtype wrapper. Buying in is justified only if the maintainer's ongoing curation of that list is worth more to you than roughly a day of engineering to copy the taxonomy into repository-owned config and register a select field. For most teams, vendoring removes the dependency entirely and makes the next Statamic major a non-event.
Weaver
How can I help you explore Laravel packages today?