Nova Laravel News Laravel Package

Product Decisions This Supports

• Internal developer-experience investment (small, discretionary): This package funds a "stay current without leaving the dashboard" convenience—framework releases, tutorials, and community announcements surfaced in the Nova admin. Frame it internally as a morale/awareness nicety, not a capability. If it ships, it ships as a time-boxed DX experiment with a success signal (does anyone click it?) and a kill date.
• Build vs. buy vs. fork: The PM call is build in-house or fork, not composer require. The entire product surface is one card class and one Blade view wrapping a cached feed fetch—hours of engineering, not a procurement decision. This package's real value is as a free reference implementation that has already settled the design questions; the artifact itself is not the asset.
• Dependency-policy precedent: 17 stars, 0 dependents, last release March 2019. Approving this sets a precedent that a stale, single-maintainer package can enter admin tooling on the strength of being trivial. If you approve it, approve it as vendored internal code with a named owner, not as an upstream dependency—otherwise you're writing a policy exception for a widget nobody asked for.
• Audience segmentation: Defensible only for internal, engineering-facing Nova panels. On client-facing or agency dashboards, third-party Laravel News content is off-brand and out of scope regardless of package quality. This is a decision about whose dashboard, made before the decision to build.
• Roadmap triage and demand validation: Use it as a signal for latent appetite in "internal dashboards" or "developer portal" work, not as a roadmap line item. Run a cheap spike, measure engagement, and sunset it fast if engineers don't touch it—rather than carrying recurring maintenance across Nova upgrades for a widget.
• Pattern existence proof: When stakeholders ask for team dashboards or internal comms surfaces, this repo demonstrates the "pull external content into the admin" pattern. Cite it as a reference, not as a product bet.

When to Consider This Package

Adopt the ideas, and only adopt the code when all of the following hold:

• You are on Nova 1.x / early 2.x (2018–2019 era); later majors will likely break card registration, service-provider conventions, or the published view.
• The dashboard is internal and engineering-only—low stakes if it silently fails.
• You will fork, vendor, and own the code, with a named internal owner in your tools inventory.
• The admin host has outbound HTTPS egress, and you will add caching (30–60 min TTL), explicit HTTP timeouts, a neutral failure state, and output escaping.
• You accept the security and maintenance review burden of a stale, zero-dependent package for a cosmetic surface.
• Someone has actually asked for it. Not "the team thinks it's neat."

Look elsewhere or build in-house when:

• You are on Nova 3, 4, or 5—expect incompatibility; write a minimal card against the installed API instead.
• The dashboard is client-facing or customer-visible.
• The environment is air-gapped, egress-restricted, or policy forbids unmaintained dependencies in admin tooling.
• You need more than a static headline list—filtering, read-state, notifications, or curation are out of scope and out of reach.
• There is no demonstrated demand; cosmetic surfaces should not consume security-review or upgrade capacity.

How to Pitch It (Stakeholders)

To executives: This is a free, MIT-licensed widget that puts Laravel News headlines on our internal Nova admin dashboard. It has no customer impact, no revenue path, and no integration surface—it is developer awareness and morale. The package is effectively abandoned (last release March 2019, 17 stars, zero downstream users), so the recommendation is not to adopt it as a dependency. If we want the feature, engineering can rebuild the equivalent in about an afternoon and own it outright—lower risk at roughly zero cost. The only decision I'm asking for is whether that afternoon is worth spending; I'd rather validate demand first than approve a dependency.

To engineering leads: Treat this repo as a reference implementation, not a dependency. The durable value is the pattern—a Nova card wrapping a cached feed fetch—and reproducing it against our installed Nova version is cheap. If we pull the code in anyway: fork it under an internal namespace, lift Composer constraints to our current Laravel/Nova/PHP matrix, cache the feed with a 30–60 minute TTL, set explicit HTTP timeouts, render a neutral fallback on failure, escape all third-party content, log fetch failures rather than swallowing them, and assign a named owner. Run a half-day compatibility spike first—success is a rendered card with live data, not a resolved dependency graph—then decide build vs. fork on the findings, not on the README. Budget expectation: reviving the package costs more than replacing it.