Commongroundbundle Laravel Package

Product Decisions This Supports

• Dutch Government API Integration: Accelerates compliance with VNG Common Ground standards (e.g., BSN validation, KVK lookups) for Dutch public-sector projects, reducing custom development time.
• API Platform Extension: Enables rapid adoption of Dutch-specific API features (e.g., event-driven workflows, resource lifecycle hooks) in Symfony/API Platform projects without reinventing the wheel.
• Build vs. Buy: Justifies buying this package over custom development for Dutch government projects requiring Common Ground compliance, especially if the team lacks expertise in VNG standards.
• Roadmap Prioritization: Validates investment in Dutch public-sector APIs by providing a standardized, maintainable foundation for:
  • Citizen data validation (e.g., BSN checks).
  • Integration with Dutch registries (e.g., KVK for business validation).
  • Event-driven extensions (e.g., pre/post-save hooks for auditing).
• Use Cases:
  • Public Sector: Municipalities, provinces, or national agencies needing to comply with Dutch API standards.
  • Third-Party Integrations: Vendors building solutions for Dutch government clients (e.g., healthcare, tax, or social services).
  • Legacy Modernization: Upgrading monolithic systems to API-first architectures with Common Ground compliance.

When to Consider This Package

• Adopt When:

  • Your project is targeting the Dutch public sector (e.g., government agencies, municipalities, or Dutch-focused SaaS).
  • You’re using Symfony/API Platform and need VNG Common Ground compliance (e.g., BSN validation, KVK lookups).
  • You require event-driven extensions for Common Ground resources (e.g., auditing, workflows) without building from scratch.
  • Your team lacks deep expertise in Dutch API standards but needs to integrate with Common Ground quickly.
  • You prioritize open-source, MIT-licensed solutions with minimal vendor lock-in.

• Look Elsewhere When:

  • Your project is outside the Dutch context (e.g., international or non-public-sector).
  • You need active maintenance or commercial support (package has 0 stars/dependents; check Conduction’s roadmap).
  • Your stack is not Symfony/API Platform (e.g., Laravel, Django, or custom PHP).
  • You require advanced customization beyond Common Ground’s scope (e.g., non-Dutch registries or unique validation rules).
  • You need enterprise-grade SLAs (this is a community-maintained package).

How to Pitch It (Stakeholders)

For Executives:

"This bundle lets us comply with Dutch government API standards (Common Ground) in weeks instead of months—saving development costs and reducing risk. By leveraging open-source tools from Conduction, we can integrate with Dutch registries (e.g., BSN, KVK) and build event-driven workflows without custom code. It’s a strategic move for [Dutch public-sector projects], aligning us with government digitalization initiatives while cutting time-to-market."

Key Outcomes: ✅ Faster compliance with VNG standards (no reinventing the wheel). ✅ Lower development costs (MIT-licensed, no per-seat fees). ✅ Scalable integrations for Dutch registries (e.g., citizen/business validation). ✅ Future-proof for API-first government projects.

Risk Mitigation:

• Low maintenance: Package is open-source; we can contribute or fork if needed.
• Dutch-specific: Only relevant for our target market (no international bloat).

For Engineering/Tech Leads:

"This Symfony bundle plugs into API Platform to add Dutch Common Ground functionality—think BSN validation, KVK lookups, and resource lifecycle events—with minimal setup. It’s a drop-in solution for projects needing VNG compliance, offering:

• Pre-built events (e.g., commonground.resource.save) for auditing/workflows.
• Standardized API responses aligned with Dutch government specs.
• No dependency on proprietary tools (MIT license, PHP 7.1+).

Why Not Build It?

• Time: Avoids 2–4 weeks of custom validation logic for Dutch registries.
• Quality: Leverages Conduction’s expertise (maintained by a Dutch platform startup).
• Extensibility: Events let us hook into resource operations without modifying core logic.

Trade-offs:

• Immaturity: 0 stars/dependents → validate with Conduction’s roadmap.
• Symfony-only: Not portable to Laravel or other stacks.

Proposal:

1. Pilot: Use it in a non-critical Dutch project to test integration.
2. Customize: Extend events/hooks for project-specific needs.
3. Monitor: Track Conduction’s updates for long-term viability."*