Craft Ray Laravel Package

Product Decisions This Supports

• Debugging & Developer Experience (DX) Roadmap: Accelerate debugging workflows for Craft CMS developers by integrating a modern, cross-language debugging tool (Ray) into the ecosystem. Reduces reliance on var_dump()/console.log() and improves visibility into complex state.
• Build vs. Buy: Avoid reinventing a debugging dashboard—leverage Spatie’s mature Ray infrastructure (already used in Laravel) to standardize debugging across PHP-based projects.
• Use Cases:
  • Debugging complex Craft CMS queries (e.g., Element API, GraphQL, or custom queries) with structured output.
  • AI/ML integrations: Debugging AI-generated content or dynamic template logic in Craft.
  • Performance profiling: Identify bottlenecks in Craft’s Twig templates, plugins, or custom modules.
  • Cross-team collaboration: Share debug sessions with designers/engineers via Ray’s interactive UI.
• Tooling Stack Alignment: Complements existing Laravel/PHP tools (e.g., Laravel Debugbar) by offering a unified debugging experience for hybrid stacks (PHP + JavaScript).

When to Consider This Package

• Adopt if:
  • Your team uses Craft CMS and struggles with fragmented debugging tools (e.g., browser dev tools + var_dump()).
  • You need real-time debugging for dynamic content (e.g., AI-generated entries, real-time updates).
  • Your stack includes multiple languages (PHP, JavaScript, etc.) and you want a unified debugging workflow.
  • You prioritize developer productivity and can justify the cost of Ray licenses for the team.
• Look elsewhere if:
  • Your team is heavily invested in Craft’s built-in debug tools (e.g., Twig Debugger) and lacks budget for Ray.
  • You’re debugging low-level PHP issues (e.g., kernel-level problems) where Xdebug or Blackfire is more appropriate.
  • Your project is small-scale with minimal debugging needs (e.g., simple templates).
  • Compliance/licensing restrictions prohibit third-party debugging tools (Ray requires a paid license for full features).

How to Pitch It (Stakeholders)

For Executives: "Craft CMS powers our content platform, but debugging complex workflows—like AI-generated content or real-time queries—can slow down development. spatie/craft-ray integrates Ray, a desktop debugging tool used by Laravel teams, to give our developers a unified, interactive way to inspect data, queries, and performance. This reduces context-switching (no more toggling between browser dev tools and PHP logs) and speeds up fixes. The free tier lets us test it with 20 messages/session, and the paid license (~$99/year per dev) is a small investment compared to the time saved. It’s a drop-in solution that aligns with our tech stack and improves DX for our engineering team."

For Engineering: *"Ray + craft-ray lets us debug Craft CMS like we do Laravel—with a real-time, interactive UI instead of scattered dump() calls or browser consoles. Key benefits:

• Structured output: See arrays, queries, and even Markdown-formatted data in one place.
• Performance insights: Pause execution and measure Twig/template performance.
• Cross-language: Debug PHP and JavaScript in the same tool (if using Ray’s JS extension).
• Collaboration: Share debug sessions with designers or QA via Ray’s UI. Setup is trivial—just install the package and configure Ray. The free tier is enough for testing; the paid license unlocks unlimited sessions and team features. Let’s pilot it on [Project X] to compare it to our current workflow."