Resource Rest Bundle Laravel Package

Product Decisions This Supports

• Legacy System Modernization: Accelerate API integration for older Symfony-based CMS projects (e.g., content-heavy sites) without full rewrites.
• Build vs. Buy: Justify using this package for internal tools or low-risk MVP APIs where maintenance burden is acceptable (vs. building from scratch or adopting newer alternatives like API Platform).
• Roadmap Prioritization: Defer new feature development for REST APIs if the team is already invested in Symfony CMF’s routing ecosystem (e.g., dynamic content routing).
• Use Cases:
  • Exposing Puli resources (e.g., documents, media) as REST endpoints for headless CMS or mobile apps.
  • Rapid prototyping of content APIs in legacy Symfony 4/5 projects.
  • Integrating with third-party systems that require Symfony CMF’s resource model.

When to Consider This Package

• Adopt if:

  • Your project already uses Symfony CMF (e.g., for routing or resources) and needs a lightweight REST layer.
  • You’re working on a legacy system where maintenance risk is outweighed by immediate API needs.
  • Your team has Symfony/PHP expertise to handle potential gaps (e.g., no active maintenance).
  • You need JMS Serializer support (for complex resource serialization) and are using PHP 7.2+.

• Look elsewhere if:

  • You require active maintenance, security patches, or long-term support (consider API Platform or Nelmio API Doc).
  • Your project is new or uses modern Symfony (6+/7+)—opt for Symfony’s built-in Mercure/UX or API Platform.
  • You need GraphQL (use API Platform or Symfony GraphQL).
  • Your resources are not Puli-based (this bundle is tightly coupled to Symfony CMF’s resource system).

How to Pitch It (Stakeholders)

For Executives: "This package lets us quickly expose our Symfony CMF content (e.g., articles, media) as a REST API with minimal dev effort—ideal for our legacy [Project X] migration. While unmaintained, it’s a stable, MIT-licensed solution that aligns with our existing tech stack. We’d treat it as a short-term bridge while evaluating longer-term options like API Platform. Risk is mitigated by our PHP team’s ability to patch or extend it if needed."

For Engineering: *"Pros:

• Zero setup for CMF users: Plugs into existing Puli resources with JMS Serializer support.
• Lightweight: No heavy framework dependencies (unlike API Platform).
• Works with PHP 7.2–7.4: Compatible with our legacy codebase.

Cons:

• No updates: Last release in 2021; we’d need to fork or patch for critical issues.
• Limited docs: Relies on Symfony CMF’s broader docs (some gaps expected).
• Not future-proof: Better for internal tools than customer-facing APIs.

Recommendation: Use for [Internal Tool Y]’s API needs, but pair with a migration plan to API Platform within 6 months."*