Statamic Ytlistr Laravel Package

Product Decisions This Supports

• Content-driven feature launches: If your roadmap includes video galleries, resource hubs, changelogs, or marketing pages that pull from YouTube, this package covers the ingestion and display layer, reducing the build-vs-buy question to configuration rather than custom API work.
• Build vs buy on media integrations: YouTube Data API plumbing (auth, pagination, quota handling, caching, refresh) is well-trodden work with no product differentiation. v1.2.0’s automated sync and scheduler support make “buy/adopt” the defensible default over an in-house integration.
• Roadmap sequencing for “fresh content” guarantees: Hourly or daily scheduled sync lets you promise stakeholders that published videos appear on the site without manual editorial intervention — a concrete commitment you can make in a roadmap review rather than a vague “we’ll keep it updated.”
• Editorial vs automated content workflow: YAML storage support signals a viable middle path — content teams can hand-author or version-control video metadata in flat files while the package still handles YouTube sync. This unlocks decisions about whether editorial owns video curation or an automated feed does.
• Risk reduction on a dependency: Pest unit tests materially change the reliability story. A package with a real test suite is one you can put on a critical path (e.g., a launch page tied to a campaign date) rather than a nice-to-have side project.
• Scope decisions for front-end work: Blade and Antler example documentation shortens the spike needed to estimate UI work, which improves accuracy on sprint planning for any video-surfacing initiative.

When to Consider This Package

Adopt when:

• Your product surfaces YouTube content and you want it to stay current without a manual publishing step.
• You’re on Laravel and want a solution that uses native framework primitives (job scheduler, data_get) rather than introducing a parallel scheduling or data-access idiom.
• You need low-ops content storage — YAML flat files are appropriate if video metadata volume is modest and version-controlled content is a plus for your team.
• You want a package with an actual test suite before you commit engineering time or tie it to a dated deliverable.
• Your team is small and you’d rather spend the sprint on differentiation than on API integration and refresh logic.

Look elsewhere when:

• Video volume or traffic is large enough that flat-file/YAML storage becomes a bottleneck — a database-backed or headless-CMS approach will scale better.
• You need multi-source content (Vimeo, self-hosted, DAM) rather than a YouTube-centric integration; the YouTube-specific depth here is a strength only if YouTube is your platform.
• YouTube API quota limits or rate policy are a hard constraint for your sync cadence — hourly sync is convenient, but validate it against your channel size and quota budget.
• You require vendor SLAs or commercial support; this is a community package and the risk profile reflects that.
• Your sync needs are event-driven or near-real-time (webhooks, publish triggers) rather than scheduled polling.

Adoption caveats: hourly sync is a meaningful increase in outbound calls — confirm quota headroom before enabling it broadly, and start with daily. Treat YAML storage as an intentional architectural choice, not a default; migrating to a database later is work you should price in now if growth is expected.

How to Pitch It (Stakeholders)

To executives: This release turns a convenience library into something we can build customer-facing commitments on. The additions that matter commercially are automated YouTube sync on a schedule — meaning published videos appear on our site without human intervention — and a test suite, which lowers the risk of putting this on a launch-critical path. It’s a small dependency that removes a recurring manual workflow and avoids us paying engineers to rebuild a commodity integration. The recommendation is adoption for video-surfacing work, with a deliberate decision on storage depending on expected content volume.

To engineering: v1.2.0 addresses the main gaps that would have blocked production use. Pest tests mean we can trust upgrades and integrate into CI. Scheduled sync via the native Laravel job scheduler means no bespoke cron infrastructure — it fits our existing operational model. data_get($video, 'youtube_url') is a small but sensible performance and null-safety improvement. YAML storage gives us a flat-file option for content that benefits from version control, but it’s a real architectural commitment — if we expect metadata volume or query complexity to grow, plan the database path from the start rather than migrating under pressure. Watch YouTube API quota against hourly cadence, and note this is a community package without commercial support, so we should pin the version and own our upgrade testing.