Nova Page Builder Laravel Package

Product Decisions This Supports

• Feature scoping for editorial tooling: The 1.6.0 release adds the ability to sort page builder layouts by title in Nova. This is an admin-facing usability improvement, not a content-model change — it reduces friction for editors managing large layout libraries (e.g. dozens of reusable blocks like "Hero", "Testimonial Row", "CTA Banner").
• Roadmap signal on maintenance health: A small, targeted PR merged by a named contributor (@jaymeh) indicates the package is actively maintained but iterating incrementally. Treat this as a low-risk, steady-state dependency rather than a package on a major trajectory.
• Build vs. buy for page composition: Reinforces the case for buying — the vendor is absorbing the long tail of CMS admin UX work (sorting, ordering, browsing) that would otherwise consume your own sprint capacity.
• Prioritisation input: If your editors have complained about finding layouts in a long dropdown/list, this release partially addresses that pain at zero implementation cost beyond a version bump. Good candidate for a low-effort "quick win" slot in a maintenance sprint.
• Not a decision driver: This release does not change content modelling, storage, API surface, or authoring capabilities. Do not use it to justify new roadmap investment.

When to Consider This Package

Adopt when:

• You are building on Laravel Nova and need structured, reusable page composition (layouts/blocks) without building a bespoke builder.
• Your editorial team is small-to-medium and primarily operates inside the Nova admin rather than a separate headless CMS.
• You want a maintained, narrowly-scoped module from a vendor (Creode) rather than a sprawling page-builder framework.
• You value incremental, low-churn maintenance — 1.6.0 is additive and non-breaking (minor version, single feature PR), so upgrade risk is minimal.

Look elsewhere when:

• You are not on Nova — this package is effectively unusable outside that admin stack, and Nova licensing is itself a cost consideration.
• You need first-class headless/API content delivery, versioning, workflow/approvals, or localisation of layouts. This release adds none of that.
• You require a large public component ecosystem or visual front-end editing; a dedicated builder product will serve better.
• Long-term single-maintainer risk is unacceptable — verify contributor breadth and release cadence before committing.

Upgrade guidance for 1.6.0: Safe minor bump from 1.5.0. No deprecations or breaking changes noted; standard regression pass on layout listing screens is sufficient.

How to Pitch It (Stakeholders)

For executives: This is a routine, low-risk maintenance release for a page-building module already in our admin stack. It adds one small usability improvement — sorting layouts by title — that makes it faster for content editors to find and reuse page sections. No migration work, no breaking changes, no additional cost. The broader message is that the dependency is alive and being improved, which supports keeping it rather than commissioning a custom build.

For engineering: Version 1.6.0 is an additive minor release from 1.5.0 containing a single feature PR that introduces title-based sorting for page builder layouts in Nova. No API changes, schema changes, or deprecations. Recommended action: bump the constraint, run the existing layout-admin test path, and ship in the next maintenance window. Flag for tracking: single-contributor commit on this release — worth monitoring bus factor over the next few releases.

Caveat to state plainly: This release does not expand what the product can do for end users; it improves admin ergonomics only. Set expectations accordingly.