Nova Single Record Resource Laravel Package

Product Decisions This Supports

• Admin UX for singleton resources. Any model where the product only ever has one row — site settings, global branding, a single "About page" record, company profile, feature-flag config, terms-of-service text — currently forces admins through a pointless list view of one item. This package collapses that to a single nav link, removing a click and a "which one do I edit?" moment from every admin session.
• Build vs. buy on admin polish. It's a narrow, low-risk convenience layer over Laravel Nova. The decision it informs is not "should we change our data model" but "do we spend an afternoon of engineering time replicating this, or adopt 40 lines of someone else's code?"
• Roadmap sequencing for internal tooling. If the current quarter already includes admin-panel cleanup, this is a cheap, demoable win to bundle in. If admin tooling isn't on the roadmap, this isn't worth carving out time for.
• Whether to expose an index at all. It subtly pushes a product position: singleton resources shouldn't have index pages. That's a reasonable convention worth agreeing on across the admin, since it affects how future resources are modeled and documented for the team.
• Nova upgrade planning. Because the last release predates Nova 4, evaluating this package is really a checkpoint on "how much of our admin depends on unmaintained Nova 3-era extensions?" — useful input for budgeting an eventual Nova upgrade.

When to Consider This Package

Consider it when all of the following hold:

• You're on Laravel Nova and have at least one, ideally several, genuine singleton resources in the admin.
• Your Nova version is compatible with the package's 2021-era release (verify against your composer.json before committing; Nova 4+ is a real risk).
• The admin is internal-facing, low blast radius, and a broken nav link is an annoyance rather than an outage.
• You're comfortable with a small, low-star, single-maintainer dependency — or you're willing to vendor/fork it, which for a package this size is entirely reasonable.
• Your team has no policy requiring actively maintained dependencies or security review for every Composer package.

Look elsewhere — or just build it in-house — when:

• You're on Nova 4 or later, or plan to upgrade within the year. Compatibility is unverified and the release cadence suggests it won't be patched.
• Your dependency policy flags unmaintained packages, or the admin handles regulated/sensitive data and every dependency needs an audit trail.
• The singleton problem is a one-off. Adding a dependency to save a single afternoon isn't a trade worth making; a small custom Nova card or a custom Nova::resources() registration gets you there.
• You need richer behavior — per-role visibility, multiple singletons per resource, or redirect-after-save semantics — which this package doesn't attempt to cover.

How to Pitch It (Stakeholders)

To executives: A small, free open-source add-on that removes friction from our internal admin panel — admins editing one-off content like site settings or the company profile land directly on the record instead of clicking through a list containing a single item. Low cost, low risk, no customer-facing impact. The only caveat is that it's a small community package last updated in 2021, so we should treat it as a convenience we can replace ourselves in a few hours if it ever breaks.

To engineering: It's a thin Nova extension that registers singleton resources as a direct nav link to their sole record. The scope is deliberately narrow: no data-model changes, no migrations, no runtime overhead beyond nav rendering. Two things to verify before we merge: Nova version compatibility against our pinned version, and whether we're comfortable taking a 18-star, single-maintainer dependency with no release in three years. If either answer is uncomfortable, the fallback is a ~half-day in-house equivalent — I'd rather we decide consciously than inherit it by accident.