Core Laravel Package

Product Decisions This Supports

• Build vs. Buy for Restaurant Tech: Justify adopting TastyIgniter/core as a foundational layer for a B2B restaurant ordering/reservation platform instead of building from scratch. The package provides pre-built admin panels, extension systems, and core workflows (e.g., table reservations, geolocation), reducing dev time by 60–80% for MVP features.
• Roadmap Acceleration: Prioritize Phase 1 (Core Platform) by leveraging the package’s extension system to modularize features (e.g., payments, loyalty) as reusable components, enabling parallel development.
• Monetization Strategy: Use the admin panel and customization tools to offer white-label solutions for small restaurants, targeting a $500–$2,000/year SaaS tier.
• Compliance & Security: Mitigate risks in user-generated content (e.g., menu descriptions, email templates) via the TemplateSandbox, aligning with PCI-DSS for payment integrations and GDPR for reservation data.
• Tech Stack Standardization: Standardize on PHP 8.3–8.4 + Laravel to attract mid-tier dev talent and reduce hiring costs, while the package’s geolocation providers (Google/Nominatim) simplify location-based features.

When to Consider This Package

• Adopt If:
  • You’re building a restaurant tech platform (ordering, reservations, menus) and need pre-built admin interfaces without reinventing Laravel’s scaffolding.
  • Your target market includes SMBs who lack dev resources—use the extension system to offer plug-and-play features (e.g., delivery tracking, POS integrations).
  • You require multi-language/currency support out of the box (e.g., for international chains) with fixes like zero-decimal currency formatting.
  • Your security team prioritizes template sanitization over custom solutions, given the TemplateSandbox’s XSS protections.
  • You’re targeting Laravel 12 compatibility and need minimal migration effort (e.g., for existing Laravel apps).
• Look Elsewhere If:
  • Your project is non-restaurant (e.g., e-commerce, SaaS)—the package’s domain-specific features (e.g., table reservations, kitchen workflows) may not apply.
  • You need real-time sync with external systems (e.g., kitchen display systems) beyond the package’s event-driven architecture.
  • Your team lacks Laravel/PHP expertise—the package assumes familiarity with Eloquent, Blade, and Laravel’s service container.
  • You require headless APIs—the package is admin-heavy with limited GraphQL/REST endpoints.
• Avoid If:
  • You’re building a highly customized ordering system where the package’s default workflows (e.g., order status transitions) would require extensive overrides.
  • Your scaling needs exceed the package’s monolithic architecture (e.g., microservices for payments, inventory).

How to Pitch It (Stakeholders)

For Executives: *"TastyIgniter/core lets us launch a restaurant ordering platform in 3 months instead of 12 by using its pre-built admin panel, extension system, and geolocation tools. For example:

• Admin Panel: Ready-made dashboards for reservations/orders cut UI dev time by 70%.
• Extensions: Add features like loyalty programs via plugins (e.g., igniter:install) without custom builds.
• Security: The TemplateSandbox automatically sanitizes user-generated content (e.g., menu descriptions), reducing audit risks. Cost: ~$5K for a white-label SaaS tier, with $20K/year in dev savings. ROI: 4x faster time-to-market for [Product X]."*

For Engineering: *"Key leverage points for v4.2.3+:

1. Admin Panel: Use the built-in navigation system (with permissions field) to scaffold role-based access. Tradeoff: Customize via config/admin.php or extend the NavigationService.
2. Extensions: Deploy features like payments via Composer (composer require tastyigniter/payments). Caveat: Test extension conflicts early—some rely on core hooks.
3. Geolocation: The Google/Nominatim providers handle autocomplete + distance calculations for delivery zones. Note: Cache responses to avoid API costs.
4. Templates: The TemplateSandbox replaces manual Str::of() calls for sanitizing email templates or menu descriptions. Warning: Override sanitize() if you need custom rules. Recommendation: Start with the TastyIgniter app repo for a full stack example, then extract core modules (e.g., OrderService) for your project."*

For Security/Compliance: *"The TemplateSandbox (v4.2.3+) mitigates XSS in user-generated templates by default, aligning with:

• PCI-DSS: Sanitizes dynamic content in order confirmation emails.
• GDPR: Protects reservation data in customizable forms. Limitations: The sandbox uses HTML Purifier-like defaults—audit TemplateSandbox::sanitize() for edge cases (e.g., SVG support). Pair with Laravel’s validate() for additional input checks."*