Source Laravel Package

Product Decisions This Supports

• Build vs. Buy Decision:

  • Adopt REDAXO for enterprise-grade, multilingual CMS solutions requiring high customization (e.g., modular content structures, workflow automation, or legacy system integration). Ideal for teams prioritizing developer flexibility over rapid prototyping (e.g., German-speaking markets, government, or complex intranets).
  • Avoid if needing a headless CMS, JAMstack compatibility, or real-time collaboration (e.g., compare to Strapi or Directus).

• Feature Roadmap Alignment:

  • Prioritize if roadmap includes:
    • Modular content architectures (e.g., "slices" for reusable UI components).
    • Workflow automation (e.g., approval chains, custom actions).
    • Multilingual SEO (built-in language fallbacks, category/permission granularity).
    • Legacy system migration (PHP 8.3+ compatibility, Symfony 7.4 integration).
  • Deprioritize if roadmap focuses on:
    • Low-code/no-code editor experiences (e.g., Webflow, Framer).
    • Serverless deployments (REDAXO requires PHP/MySQL).

• Use Cases:

  • Corporate websites with dynamic content (e.g., news portals, product catalogs).
  • Intranets needing role-based access control (RBAC) and document management.
  • E-commerce backends (via extensions like mediapool for product media).
  • Regulatory compliance (e.g., GDPR-friendly user management, audit logs via systemlog).

When to Consider This Package

Adopt REDAXO If:

• Technical Fit:
  • Your stack includes PHP 8.3+, MySQL/MariaDB, and Symfony familiarity.
  • You need fine-grained permissions (e.g., per-category language/user access).
  • Your team prefers modular PHP development over JS frameworks (e.g., React/Vue for frontend).
• Business Needs:
  • Targeting German-speaking markets (native documentation/community support).
  • Requiring long-term maintenance (active 5.x branch, MIT license).
  • Building content-heavy sites with custom templates/modules (e.g., 100+ page types).
• Integration Requirements:
  • Need legacy system bridges (e.g., SAP, ERP via custom addons).
  • Prioritizing offline-first workflows (e.g., local Docker dev, CLI tools).

Look Elsewhere If:

• Non-PHP Stack: Using Node.js, Python, or Go.
• Headless Needs: Requiring GraphQL/REST APIs out-of-the-box (REDAXO needs extensions).
• Real-Time Collaboration: Need live editing (e.g., Google Docs-like).
• Budget Constraints: Limited dev resources for custom addon development.
• Cloud-Native Focus: Prefer serverless (e.g., Vercel, Netlify) or containerized microservices.

How to Pitch It (Stakeholders)

For Executives:

"REDAXO is a battle-tested, enterprise-grade CMS that gives us full control over content and workflows—without vendor lock-in. Think of it as the ‘Lego blocks’ for building scalable websites:

• Cost-Effective: Open-source (MIT license) with no per-seat fees; only pay for custom development.
• Future-Proof: Actively maintained (PHP 8.3+, Symfony 7.4), with a roadmap aligned to modern PHP practices.
• Competitive Edge: Ideal for complex, multilingual sites (e.g., global corporate intranets, regulatory portals) where off-the-shelf solutions fall short.
• Risk Mitigation: German-based community + Yakamara’s long-term support (since 2004).

Use Case Example: If we’re building [Project X]—a [describe: e.g., ‘multilingual employee portal with dynamic approvals’]—REDAXO lets us customize every workflow while keeping costs predictable. Alternatives like WordPress or Drupal would require more plugins/themes, increasing technical debt."

For Engineering Teams:

"REDAXO is a modular PHP framework disguised as a CMS—perfect for teams that want:

• Developer Velocity:
  • Symfony 7.4 under the hood (familiar for PHP devs).
  • Custom modules/addons (like WordPress plugins but with PHP classes).
  • API-first design: Extend core via events (e.g., MEDIA_LIST_QUERY) or hooks.
• Architectural Flexibility:
  • Slice-based templates: Reuse UI components (like Storyblok but self-hosted).
  • Permission granularity: Restrict content by category/language/user role.
  • CLI/Docker-ready: Local dev with docker-compose or composer scripts.
• Performance:
  • Caching layers (e.g., rex_finder for race-condition-safe file ops).
  • Optimized for PHP 8.3+: No legacy bloat (e.g., PHPMailer 7, Symfony updates).
• Migration Path:
  • Legacy system integration: Custom addons can bridge to SAP, databases, etc.
  • Progressive enhancement: Start with core, add modules as needed.

Trade-offs:

• Steep learning curve: Not a ‘drag-and-drop’ CMS (expect 2–4 weeks for onboarding).
• Frontend work: Requires custom templates (Twig, Blade, or raw HTML).
• Community: Smaller than WordPress but highly responsive (Slack, GitHub).

Proposal:

1. Pilot: Spin up demo_base (English demo) to test workflows.
2. Skeleton: Use redaxo/project skeleton for new projects.
3. Customization: Build 1–2 critical addons (e.g., a custom media uploader) to validate extensibility.
4. Scale: Migrate legacy content via CLI tools or custom scripts.

Alternatives Considered:

• WordPress: Less flexible for custom workflows; plugin bloat.
• Drupal: Overkill for non-enterprise needs; steep learning curve.
• Strapi: Headless-first but lacks REDAXO’s modularity for structured content."