Video Field Type Laravel Package

Product Decisions This Supports

• Content modeling without migrations. As a Streams Platform field type, this lets editors attach a video reference to any stream entry (page, product, article, course lesson) through configuration rather than a schema change. That directly shortens the loop between "marketing wants video on X" and shipping it.
• Build vs. buy for media fields. The package is a thin wrapper around storing a URL and rendering an embed. The honest comparison is against ~half a day of in-house work (a video_url column, provider detection, an embed partial, an admin form field) — not against a media platform. This is a "vendor one file" decision, not a strategic dependency.
• Roadmap input on media richness. If video-in-content is on the roadmap for editorial pages, landing pages, video galleries, or tutorial content, this is the cheapest possible proof of concept to validate the editorial workflow before investing in anything heavier.
• Platform lock-in check. Adopting this is only rational inside a Streams/PyroCMS codebase. Choosing it is implicitly a decision to stay on that stack for the content layer — worth surfacing explicitly rather than letting it happen by default.
• Risk triage. 0 stars, 0 dependents, and a low health score mean the PM decision is not "adopt" but "evaluate as reference implementation, then own the code." Treat any adoption as a fork.

When to Consider This Package

Consider it when:

• You are already running Streams Platform / PyroCMS and need a field that stores a video reference and renders it in templates. In that context it is a small convenience that keeps admin UI consistent with other fields.
• The requirement is genuinely "embed a YouTube or Vimeo URL" — a link-out, not a media asset. No uploads, no transcoding, no storage costs.
• You are comfortable forking and maintaining a few hundred lines yourself, and the MIT license makes that clean.
• You want a starting point or reference for how Streams field types are structured (field type class, configuration, views) rather than a runtime dependency.

Look elsewhere when:

• You are on plain Laravel without Streams. This package will not function; use a URL column plus an oEmbed library or a lightweight embed package instead.
• You need self-hosted or uploaded video, transcoding, adaptive streaming, or a real media pipeline (S3/Mux/Cloudflare Stream territory).
• You need privacy and consent handling — GDPR-compliant YouTube nocookie domains, click-to-load placeholders, cookie gating. Assume this is absent and budget for it.
• You need provider breadth (Wistia, Brightcove, TikTok, Loom), thumbnails, durations, or accessible player controls. Provider detection in packages this small is usually hardcoded.
• You require active maintenance, security response, or community support. Zero dependents means no one else will find the bugs first.
• Your editorial team needs preview thumbnails or validation at authoring time — verify this exists before committing; likely it does not.

How to Pitch It (Stakeholders)

To executives: This is a very small, MIT-licensed add-on for our CMS that lets editors drop a video into a page without engineering involvement. It is not a media platform and it will not handle hosting, encoding, or privacy compliance on its own. Because it has essentially no user base, I do not recommend taking it as a dependency — I recommend we copy the approach into our own codebase, which is a few hours of work and leaves us in full control. Expected cost is low; expected strategic value is modest but the ROI on editorial speed is real if video-in-content is on the roadmap.

To engineering: This is a Streams Platform field type — a URL input plus an embed renderer. It only runs inside PyroCMS/Streams; if we are on vanilla Laravel it is a pattern to copy, not a package to install. Given 0 stars, 0 dependents, and clear staleness signals, plan to fork it, pin it in-repo, and own it. Wrap the embed rendering behind a single service/partial so we can swap in a maintained oEmbed library or add consent gating later without touching content records. Check compatibility with our Streams version before estimating, and confirm whether provider support extends past YouTube and Vimeo.