Weave Code
Nova Drafts Laravel Package
optimistdigital/nova-drafts
A Laravel Nova package that adds draft and publish workflows to resources, letting editors save unpublished changes, preview drafts, and publish content when ready, with simple integration into Nova resource forms and tools for smoother editorial control.
A Laravel Nova package that allows you to make drafts of your current resources.
Frequently asked questions about Nova Drafts
- What does optimistdigital/nova-drafts do in Laravel Nova?
- optimistdigital/nova-drafts is a Laravel Nova package that adds draft and publish workflows to Nova resources. Editors can save unpublished changes, preview drafts, and publish content when ready, with integration into Nova resource forms and tools. It is an admin-layer convenience rather than a general content-versioning platform.
- How do I install optimistdigital/nova-drafts?
- Install it with Composer using the optimistdigital/nova-drafts package name, then follow the package documentation to add any required model traits, migrations, and Nova resource changes. Because the package is archived, pin an exact version and test in a sandbox first. Do not rely on a floating Composer constraint for production.
- Which Laravel, Nova, and PHP versions does nova-drafts support?
- The package was last released on 2022-11-18 and is archived, so current Nova, Laravel, and PHP compatibility is not guaranteed. Pin your Nova, Laravel, PHP, and database versions in a proof of concept and run a compatibility matrix. Validate migrations, traits, Nova fields and actions, policies, file uploads, and relationship fields before committing.
- Is optimistdigital/nova-drafts still maintained?
- No, optimistdigital/nova-drafts is archived and has low adoption, with 29 stars and no upstream fixes. Treat it as a reference implementation or an internal fork candidate rather than an unowned long-term dependency. If you adopt it, assign an internal owner for patching, Nova upgrade compatibility, and schema evolution.
- How are draft records linked to published records in nova-drafts?
- You must verify how draft records are linked to published records in your schema and what happens when publishing fails. Test partial publishes, duplicate slugs, stale drafts, and orphaned media before rollout. Publishing should be transactional and concurrency-safe for your editorial volume.
- Are nova-drafts previews authorization-scoped?
- Preview authorization scoping is a key evaluation point, not something to assume. Confirm that draft previews respect Nova policies and do not expose unpublished content to unauthorized users. Review permissions and gate preview access behind explicit policy checks.
- Can nova-drafts handle relationships, media, and localized fields?
- Validate relationships, file and media attachments, slugs, and localized fields in a one-resource proof of concept. Draft duplication can create orphaned media or stale relationship references. Confirm behavior for nested resources and any fields that must stay in sync between draft and published records.
- What are the production risks of using an archived package like nova-drafts?
- The main risks are lifecycle and data integrity: no upstream fixes, dependency drift, partial publishes, duplicate slugs, stale drafts, orphaned media, and permission leaks around previews. Draft records can roughly double storage for affected tables and add relationship or media duplication. Test indexing, Nova table performance, publish transaction size, and cleanup at your expected content volume.
- What alternatives should I consider to optimistdigital/nova-drafts?
- Because the package is archived, safer alternatives are an internally owned fork, a minimal in-house draft and publish pattern, or a maintained Nova package that fits your workflow. Avoid adopting it for headless or API-first publishing, non-Nova admin UIs, or complex approvals and scheduling. Choose based on ownership and upgrade path, not just feature fit.
- How should I test and roll out nova-drafts safely?
- Start with a sandbox proof of concept on one low-risk Nova resource, confirm schema changes are additive, and backfill existing published records. Gate the feature behind a flag, pilot with a small editor group, and run old and new workflows in parallel. Define rollback, maintenance ownership, and upgrade testing before expanding resource by resource.
Weaver
How can I help you explore Laravel packages today?