Nova Youtube Field Laravel Package

Product Decisions This Supports

• Feature scoping for media-heavy admin workflows. If your roadmap includes editorial content types where YouTube is the primary asset (marketing video blocks, course/lesson catalogs, help-center tutorials, product demo galleries), this package represents a discrete, low-cost capability: a Nova form field that captures a YouTube URL/video and renders it meaningfully in the admin rather than as a raw string.
• Build vs. buy for the admin layer. The real decision this informs is whether to (a) adopt a third-party Nova field, (b) fork this one, or (c) build it in-house. Because the field's core value is roughly "validated URL input + video ID parsing + thumbnail/embed preview," the build cost is small — likely 1–2 engineering days including tests. That reframes the buy decision from "is this package good?" to "is a dependency worth avoiding two days of work?"
• Data modeling decisions. Whether video references live as a plain string column with accessor/parsing logic (portable, no lock-in) versus a field-specific storage format (convenient, but couples your schema to a Nova package). The package implicitly pushes toward the former, which is the safer long-term call.
• Editorial UX investment. A preview-in-form field measurably reduces content-entry errors (wrong video, broken link, wrong timestamp) for non-technical editors. This supports prioritizing admin ergonomics in a content ops roadmap.
• Vendor/technical-debt triage. With an archived 2018 repo at 24 stars, this is a useful data point for establishing a dependency policy: Nova-ecosystem packages age quickly because Nova's own major versions move fast, and an unmaintained field becomes a blocker at every Nova upgrade.

When to Consider This Package

Consider it when:

• You are running a Laravel Nova 1.x/2.x-era install (the 2018 release predates Nova 3+) and need a video field quickly for an internal, low-traffic admin.
• You want a reference implementation to fork or crib from — reading its source is faster than starting from Nova's field documentation, and MIT licensing permits it.
• The admin is internal-only, the field is non-critical, and a broken render degrades UX rather than blocking revenue.
• You are prototyping and can accept throwaway code while validating whether editors actually benefit from inline video preview.

Look elsewhere (or build) when:

• You are on Nova 3, 4, or 5, or PHP 8+. Compatibility is unverified and the repo is archived — assume it does not work without a fork.
• You need maintained dependencies, security patching, CI, or a support path. An archived package is a permanent "no" from a security/procurement review.
• Requirements extend beyond a single video: playlists, channels, private/unlisted videos, oEmbed metadata, duration/thumbnail caching, or multi-video ordering — this field does not address them.
• You need strict validation (URL canonicalization, video-existence checks via the YouTube Data API, timestamp parsing). Expect to write this yourself regardless.
• Your team already treats Nova customization as in-house territory; introducing a stale dependency creates an upgrade tax with no offsetting benefit.

Practical recommendation: do not adopt as a runtime dependency. Budget a short spike to fork the field's parsing/preview logic into your own Nova\Fields\Field subclass, store the raw URL plus a derived video ID, and pin tests around URL formats you care about.

How to Pitch It (Stakeholders)

For executives: This is a small, MIT-licensed admin-panel add-on that lets editors paste a YouTube link and see it rendered inline instead of as a raw URL. The capability is genuinely useful for content-heavy admin screens, but the package itself was last released in 2018 and is archived — meaning no maintenance, no security updates, and likely incompatibility with our current Nova version. Recommendation: do not take it as a dependency. Treat it as a free reference design and spend roughly one to two engineering days building the equivalent in-house. Cost is negligible; the benefit is avoiding a dead dependency that will complicate our next admin upgrade.

For engineering: The field's substance is YouTube URL parsing, video ID extraction, and a thumbnail/embed preview — plus Nova field plumbing. The repo is a reasonable prior-art read under MIT, but it predates Nova 3 and will not drop into a modern install. Proposed approach: vendor a small custom field, store the canonical URL as a plain string column with a derived video_id accessor (portable, no Nova coupling in the schema), and add validation for the URL shapes we actually accept. If we later need oEmbed metadata, thumbnails caching, or playlist support, that is a separate, scoped piece of work — the package offers no head start there.

For product/QA: Success looks like editors entering valid video references on the first attempt and catching mistakes before publish. Acceptance criteria should cover: accepted URL formats (watch, short links, with/without timestamps), rejection messaging for invalid input, and preview behavior when a video is deleted or made private.