Core Bundle Laravel Package

Product Decisions This Supports

• Internal Developer Platform (IDP) or Backstage Integration:

  • Accelerate adoption of Backstage.io (Spotify’s open-source developer portal) within a PHP/Laravel ecosystem by providing a standardized bundle for core functionality (e.g., scaffolding, theming, and service integration).
  • Use case: If your team manages microservices, APIs, or internal tools and needs a unified portal for documentation, discovery, and onboarding—leverage this to bridge Backstage with PHP-based legacy systems or new Laravel projects.

• Roadmap: Modernization of Legacy Systems:

  • Justify build vs. buy by adopting Backstage as a low-code/no-code portal layer over existing PHP/Laravel monoliths or microservices.
  • Example: Migrate a custom internal wiki or service catalog to Backstage while keeping backend logic in PHP.

• Feature: Unified Developer Experience:

  • Pitch this as part of a platform team initiative to reduce context-switching for engineers (e.g., consolidating Jira, Confluence, and custom tools into Backstage).
  • Metric: Reduce onboarding time for new hires by 30% via centralized documentation and service discovery.

• Use Case: Hybrid Tech Stacks:

  • If your org uses both PHP/Laravel and modern stacks (Node.js, Go, etc.), this bundle enables Backstage to act as a neutral hub for all services, with PHP components integrated via the bundle.

When to Consider This Package

• Adopt if:

  • Your team already uses Backstage.io and needs PHP/Laravel integration (e.g., exposing legacy APIs or templating components).
  • You’re building a developer portal and want to avoid reinventing core features (auth, menus, HTML sanitization, etc.).
  • Your PHP stack relies on Symfony bundles (this package is Symfony-compatible via Laravel’s Symfony integration).

• Look elsewhere if:

  • You’re not using Backstage: This is a niche bundle with minimal adoption; evaluate standalone Symfony/Laravel packages for generic needs.
  • Your team lacks Symfony familiarity: The bundle assumes knowledge of Symfony bundles (e.g., Doctrine, KnpMenu), which may require upskilling.
  • You need active maintenance: With 1 star and no recent commits, prioritize packages with stronger community support (e.g., API Platform for Laravel).
  • Your use case is pure Laravel: This is Symfony-first; consider Laravel-specific alternatives like Laravel Backstage plugins or custom packages.

How to Pitch It (Stakeholders)

For Executives: "We’re proposing to adopt Backstage.io—Spotify’s open-source developer portal—to unify our fragmented tools (wikis, APIs, docs) into one searchable, self-service platform. This PHP bundle lets us integrate our existing Laravel/Symfony services seamlessly, reducing dev ramp-up time by 30% and cutting support costs. It’s a low-risk way to modernize our internal tools without rewriting everything."

Key Ask:

• Approval to pilot Backstage with this bundle for one high-value service (e.g., API documentation).
• Budget for Symfony upskilling (if needed) or hiring a consultant to configure the bundle.

For Engineering: *"This bundle gives us a head start on Backstage integration for PHP projects. It handles:

• Core scaffolding (avoid reinventing menus, auth, or HTML sanitization).
• Symfony bundle compatibility (Doctrine, CKEditor, etc.)—useful if we’re already using these.
• Laravel-friendly via Symfony integration (though we’ll need to test edge cases).

Risks:

• Minimal community support (1 star, outdated). We’ll need to fork or contribute if we hit blockers.
• Assumes Symfony knowledge; may require pairing with a Symfony expert initially.

Proposal:

1. Start with the standard distribution (recommended by the README).
2. Use this bundle to wrap a single Laravel service in Backstage (e.g., expose our user management API).
3. Measure impact on dev onboarding time before scaling."*

For Developers: *"This is a Symfony bundle that plugs into Backstage to provide:

• Pre-built templates for PHP/Laravel components.
• Dependency management for Doctrine, CKEditor, and menus (no need to configure these from scratch).
• Laravel compatibility via Symfony’s bridge.

How to Use It:

1. Install via Composer: composer require bkstg/core-bundle.
2. Follow the standard distribution for setup.
3. Extend it for your Laravel app’s needs (e.g., custom Backstage plugins).

Gotchas:

• Not Laravel-native: Expect some Symfony quirks (e.g., YAML configs, event listeners).
• Limited docs: You’ll need to debug by comparing with the standard distro.
• Community: If you find issues, consider contributing or forking.

Quick Win: Use it to expose a Laravel API in Backstage as a proof of concept."*