Nova Drafts Laravel Package

Product Decisions This Supports

• Editorial safety in Nova-administered content: Enables draft/publish workflows so editors can stage changes to Nova resources without immediately affecting live records.
• Feature vs. build decision: Provides a low-cost way to validate demand for drafting before committing to a custom Nova field/action, separate draft tables, or a broader CMS workflow.
• Workflow scope decisions: Forces clarity on single-draft vs. version history, who can save vs. publish, whether drafts cover relationships/localized fields, and whether drafts require review or approval.
• Roadmap prioritization: Useful for MVPs or admin UX improvements in CMS pages, product catalogs, policy content, internal knowledge bases, or landing pages where premature publishing is costly.
• Build/buy/borrow decision: Because the package is archived, treat it as an accelerator or reference implementation; decide explicitly whether to fork/vendor it, rebuild the pattern internally, or adopt a maintained alternative.

When to Consider This Package

Consider it when:

• The product already uses Laravel Nova as its admin interface and needs simple draft support for Nova resources.
• The immediate need is an MVP or internal editorial workflow, not enterprise-grade publishing governance.
• Engineering can fork, vendor, pin, and own the package because it is archived and last released in 2022.
• Compatibility with the current Laravel/PHP/Nova versions has been verified, with rollback and backup plans in place.
• The team accepts limited workflow features and can validate draft/publish value before expanding scope.

Look elsewhere when:

• Requirements include approval chains, scheduled publishing, audit trails, version diffing/rollback, granular permissions, localization workflows, or complex relationship handling.
• The product needs a long-term maintained dependency with security updates and active support.
• There is no engineering ownership capacity to maintain a fork or manage migrations.
• Nova/Laravel version compatibility is uncertain or unsupported.
• The organization needs a full CMS or regulated content workflow rather than a lightweight admin drafting aid.

How to Pitch It (Stakeholders)

For executives: This is a small, MIT-licensed Laravel Nova package that can accelerate a draft/publish workflow in the admin panel, reducing the risk of incomplete or premature content changes going live. The key caveat is that it is archived, so it should be framed as a low-cost accelerator or reference—not a strategic long-term dependency—unless engineering is prepared to own a fork.

For engineering: Evaluate compatibility with the current Nova/Laravel/PHP stack, fork and pin the package, document the draft storage and publish path, and define a fallback if maintenance becomes a burden. The package reduces initial build effort but shifts responsibility to the team for security, upgrades, and edge cases.

For product: Use it to test whether draft/publish controls improve editorial confidence and reduce accidental publishing. Measure accidental publishes, editorial cycle time, and review friction; only invest in approvals, scheduling, and audit trails if the simpler draft workflow proves valuable.