Nova Repeater Blocks Laravel Package

Product Decisions This Supports

• Feature scoping — flexible content editing: Informs whether to ship a typed, block-based content editor (each block is its own model/resource, attached via polymorphic relations) instead of free-text fields or rigid schema columns.
• Build vs. buy for admin tooling: A ready-made pattern to evaluate against building a custom block editor in Nova. MIT license removes licensing cost; the real cost is integration plus ongoing maintenance of a small, low-adoption dependency.
• Roadmap — content ops self-service: Supports a milestone where editors compose landing pages, blog bodies, FAQs, or testimonials by adding/reordering blocks without engineering tickets.
• Data-model decision: The polymorphic relation (one shared block linkage, reusable across Page/Post/Product, etc.) is a genuine architectural fork — informs whether to share block types across entities or duplicate fields per model.
• Workstream sizing: Can de-risk the "editing experience" portion of a CMS project, shifting team effort from CRUD plumbing toward block-type design and front-end rendering.

When to Consider This Package

Consider it when:

• You are already on Laravel Nova and need structured, repeatable content (page sections, flexible content) — not a full page builder.
• You want a typed block registry where each block type is a first-class Nova resource, and editors need add/remove/reorder.
• Multiple parent models should share the same block types — the polymorphic requirement is real for you.
• You have engineering capacity to own, vendor, or fork the package if needed.
• You can verify compatibility with your Nova major version.

Look elsewhere when:

• You are on a current Nova release — the last release was May 2022, so treat maintenance and compatibility as an open risk to validate, not an assumption.
• You need a true page builder: drag-and-drop layout, live preview, drafts/versioning, per-block permissions, or per-block localization.
• You require vendor support, security patching, or a sizable community — 34 stars and a 2022 release indicate minimal maintenance.
• You are not on Nova already; adopting Nova plus this package adds licensing and lock-in cost.

How to Pitch It (Stakeholders)

Executives: This is a lightweight, MIT-licensed add-on that would let marketing compose pages from reusable content blocks inside our existing admin — reducing engineering toil for routine page changes and shortening campaign launch cycles. The cost is integration time, not licensing. The main risk is maturity: it's a small, low-adoption project last updated in 2022, so I recommend a short spike to validate fit before committing it to the roadmap.

Engineering: It extends Nova with a block-model pattern built on standard polymorphic Eloquent relations — each block type is a model/resource, attached to parents through a shared polymorphic linkage, with add/remove/reorder in the admin. Integration is conventional. The concerns are Nova major-version compatibility, the age of the last release, and whether we vendor/fork it rather than depend on it. If it fits, it replaces a meaningful chunk of custom admin CRUD and lets us focus on block design and rendering.