Vidiq Laravel Package

Product Decisions This Supports

• Build vs. buy for video embedding: Rather than maintaining bespoke player markup, script tags, and embed parameter handling, this package lets the team treat video embeds as a configurable dependency. That frees engineering time for product-differentiating work (playlists, gating, analytics) instead of player plumbing.
• Feature scoping for media surfaces: Because embed output is centralized in the package, "add video to X" becomes a small, estimable story rather than a mini-integration project. Useful for prioritizing where video shows up next (article pages, product pages, gated content).
• Roadmap risk on third-party player scripts: Release 3.1.3 removes the legacy sdnplayer.js script from JavaScript embeds. That is a change in rendered output, so it belongs on the roadmap as a low-risk-but-verifiable migration item: confirm existing pages still play, check CSP/CSP-report noise drops, and confirm no downstream code was targeting the legacy global.
• Maintenance posture as a signal: A vendor shipping small, targeted patch releases (3.1.2 → 3.1.3) suggests active upkeep. That supports a "keep, pin, and monitor" decision rather than a "fork and own" decision.
• Use cases it plausibly serves: embedding hosted video in Laravel-rendered views, standardizing embed markup across templates, and letting non-engineers configure video references through application config rather than hand-edited HTML.

When to Consider This Package

Adopt when:

• You are on Laravel/PHP and need first-class video embeds in Blade-rendered views without building and maintaining your own embed layer.
• You want embed markup generated in one place so that player/script changes (like this one) are a single dependency bump rather than a codebase-wide find-and-replace.
• Your team has the discipline to pin the version, read patch notes, and smoke-test embeds after upgrades — this release is a reminder that even patch bumps can alter what gets served to browsers.
• You are willing to accept vendor-controlled embed behavior in exchange for lower build cost.

Look elsewhere when:

• You need deep control over player UI, DRM, ad insertion, or playback telemetry — that argues for owning the player integration or choosing a player SDK directly.
• Your CSP or privacy requirements demand a strict, auditable allowlist of third-party scripts; you would need to verify the package's output yourself and possibly wrap or override it.
• The project is not Laravel, or the team cannot absorb a dependency whose release cadence and support commitments are not documented.
• You already have a working embed layer; the migration cost likely exceeds the benefit unless you are actively fighting maintenance burden.

Specific to 3.1.3: existing adopters should verify embeds in a staging environment before rolling out. Dropping a legacy script is usually a cleanup win (smaller payload, fewer legacy surfaces, cleaner CSP), but any page that relied on sdnplayer.js globals or side effects will regress silently.

How to Pitch It (Stakeholders)

For executives: This is a small, actively maintained Laravel dependency that lets us ship video embedding without building a player integration ourselves. The latest patch removes an outdated player script from our embeds — a maintenance and security-hygiene improvement, not a feature change. Cost is a version bump plus a short verification pass; risk is low and contained to pages with video.

For engineering: Treat embeds as an owned dependency, not invisible plumbing. Pin the version, read the patch notes, and smoke-test playback after each bump — 3.1.3 changes rendered output by dropping the legacy sdnplayer.js script from JavaScript embeds. Confirm nothing in our templates or analytics hooks depended on that script's globals, check whether CSP violations or console warnings decrease, and confirm the player still initializes across our supported browsers. If we need player-level control or a strict script allowlist, that is the moment to discuss whether we wrap the package or replace it.