Collection Field Bundle Laravel Package

Product Decisions This Supports

• Content modeling / feature scope: This unlocks "repeatable field groups" inside a single content type — ordered lists of structured items (FAQs, speakers, pricing tiers, gallery entries, feature bullets). The decision it informs is whether to model these as first-class entities (own table, own admin screens, relations) or as an embedded collection field. The latter is materially cheaper and faster for editor-owned, low-cardinality lists.
• Build vs. buy (narrow): If you are on Unite CMS and need this field type, you are choosing between building a custom field type in-house (schema + admin UI + serialization + validation) and consuming this bundle. The bundle is a small, bounded artifact — treat it as a head start on a component you would otherwise own.
• Roadmap acceleration for content-heavy surfaces: Marketing pages, landing-page builders, and component-driven frontends frequently need variable-length arrays of props. This lets content teams change list length and contents without an engineering ticket per change — a shipping-velocity decision, not a technical one.
• Architecture decision it implicitly forces: Whether structured content lives in the CMS (single source of truth, editor-governed) or in frontend code/config (developer-governed, faster to iterate early). Repeatable fields shift that line toward the CMS.
• Vendor/ecosystem commitment: Adopting this is only meaningful as part of committing to Unite CMS. It is a Symfony bundle, not a Laravel package — the real decision on the table is your CMS platform choice, and this bundle is a down-stream consequence, not an independent one.

When to Consider This Package

Consider it when:

• You have already standardized on Unite CMS and this field type is the missing primitive in your content model.
• Your repeated data is editor-facing and small — tens of items per record, read-mostly, authored by humans.
• You want the list to be ordered and presentation-coupled (position matters, items have no independent lifecycle, no cross-record references).
• You are willing to vendor/fork and own it: pin the Composer version, review the source, and assume no upstream support.

Look elsewhere when:

• You are not on Unite CMS. This is not a general Laravel/PHP package and will not drop into a Laravel app. For Laravel-native equivalents, use Filament/Nova repeaters, or a JSON column plus a form object and validation rules.
• You need to query, sort, filter, or aggregate individual items at the database level. Embedded collections are an anti-pattern for that; model them as related entities.
• You need referential integrity, per-item permissions, per-item versioning, or per-item workflow state. Those are entities, not fields.
• You need multi-language or revision semantics on individual items that your CMS's field-level handling doesn't already provide.
• Supply-chain risk matters. Zero stars, zero dependents, and no visible community means no security review, no maintenance guarantee, and no upgrade path. That is acceptable for a small internal tool; it is not acceptable for a core platform dependency without a fork-and-own plan.
• Data volume or payload size is a concern. Large embedded arrays bloat records and slow content API responses; paginate-able entities scale better.

How to Pitch It (Stakeholders)

Executive framing: This is a small, narrowly-scoped plugin that removes bespoke development work for repeatable content — the kind of structured lists editors ask for constantly. It is not a platform bet on its own, and it should not be presented as one. The honest version: "If we commit to Unite CMS, this closes a known content-modeling gap at near-zero cost. If we don't, it's irrelevant."

To engineering: Small surface area, straightforward to read and fork, no exotic dependencies. The real cost is ownership — there is no community, no dependents, and no maintenance signal, so we should pin the version, review the code before first use, and plan to maintain our own fork rather than depend on upstream releases.

Recommendation: Adopt only as a consequence of an existing Unite CMS commitment, and only after a code review and a decision to vendor it. Do not introduce Unite CMS to the stack for the sake of this package. If the platform decision is still open, evaluate Laravel-native alternatives (Filament, Nova, Statamic) first — they carry community, support, and hiring advantages this bundle does not.