Form Bundle Laravel Package

Product Decisions This Supports

• Feature scoping for forms: Use this package as a reference for what a basic form builder needs: admin-managed forms, configurable fields, submission storage, and submission export (CSV/XLSX). It helps define MVP requirements, but it is not a Laravel-native implementation.
• Requirements validation from maintenance activity: The latest patch (v2.3.14) fixes newline handling in exported choice fields — a reminder that export correctness and data hygiene are real, recurring product requirements, not edge cases. Add explicit acceptance criteria for export escaping/sanitization in any form-builder scope.
• Build vs. buy/integrate: This remains a strong signal to avoid building a form builder from scratch for simple CMS-style use cases. The decision should still lean toward a maintained Laravel form package or commercial form builder rather than adopting this bundle.
• Roadmap prioritization: Forms and exports are usually table stakes, not differentiation. This package supports a “defer custom form infrastructure” roadmap decision unless forms are core to the product.
• Use-case validation: Relevant for marketing pages, contact forms, simple dynamic forms, CMS page-part forms, and basic submission export. Less relevant for complex workflows, approvals, payments, conditional logic, or high-compliance submission handling.
• Platform fit: Still a Symfony/Kunstmaan bundle tied to KunstmaanPagePartBundle, not a Laravel package. For a Laravel product it should inform requirements and UX expectations, not be treated as a candidate dependency. v2.3.14 does not change this.
• Risk assessment: Patch releases are still shipping, which softens — but does not remove — the maintenance concern. Adoption still carries low ecosystem confidence (small star count, no meaningful dependent base), and patch-level maintenance does not constitute a security or upgrade roadmap we can rely on.

When to Consider This Package

• Only consider it if the product is already on a legacy Symfony/Kunstmaan CMS stack and needs simple page-part-based form management with submission export.
• Consider it as a requirements/design reference when defining a form builder MVP, especially for admin-managed fields, submissions, and CSV/XLSX export behavior.
• Consider code reuse under MIT only after engineering review confirms the bundle can be isolated, updated, and supported internally — including the export/serialization paths that v2.3.14 touched.
• Look elsewhere if the stack is Laravel or modern PHP; the integration model, dependencies, and platform assumptions make it a poor fit.
• Look elsewhere for maintained packages with security support, active community, Laravel validation/authorization integration, richer export options, spam protection, notifications, conditional logic, multi-step forms, and compliance features.
• Do not adopt if the team cannot own a fork or absorb upgrade risk; occasional patch releases do not guarantee responsive maintainership or a published support policy.

How to Pitch It (Stakeholders)

For executives: forms are a common product need, but this package is not a strategic dependency. It is a Symfony/Kunstmaan bundle, not a Laravel package, and its latest release is a small correctness fix to form-export output — evidence that basic export quality matters, not evidence of strategic fit. We should use it as a checklist for basic form-builder capabilities, then select or buy a maintained solution aligned with our stack. Building custom form infrastructure is justified only if forms are a core differentiator; otherwise it is avoidable cost and risk.

For engineering: do not integrate this bundle into a Laravel application. Treat it as a reference implementation for admin-managed forms, fields, submissions, and export formatting — v2.3.14 is a useful pointer that embedded newlines and unescaped values in choice-type fields break CSV/XLSX output, so cover that in our own test cases. If we need a form builder, evaluate maintained Laravel ecosystem options or a commercial tool, and require active maintenance, a security posture, compatibility, and clear ownership before adoption.