Crudit Bundle Laravel Package

Product Decisions This Supports

• Conditional UI Logic: Enables dynamic hiding of admin panel sections (bricks, tabs, actions) based on user roles, permissions, or request context (e.g., hide "Delete" for non-admins or "Export" for read-only users). Reduces need for custom middleware or blade conditionals in CRUD interfaces.
• Permission-Light Workflows: Supports role-based UI simplification without full RBAC systems (e.g., hide sensitive actions for junior editors). Ideal for projects using Laravel’s built-in gates/policies but needing UI-level granularity.
• A/B Testing & Feature Flags: Lets teams toggle visibility of admin features (e.g., beta analytics tools) via request attributes (e.g., ?feature=analytics). Useful for gradual rollouts without code changes.
• Compliance & Audit Trails: Hide sensitive bricks/tabs (e.g., "User Deletion Log") for non-compliance teams while keeping them accessible to admins via URL parameters or headers.
• Build vs. Buy Refinement: Strengthens case for adoption when:
  • You need basic permissioning but lack budget for Filament/Backpack.
  • Your Laravel app uses gates/policies but requires UI-level conditional logic.
  • You’re building internal tools with segmented access (e.g., "Content Editors" vs. "Moderators").

When to Consider This Package

Adopt when:

• Your admin panel requires request-context-aware UI toggles (e.g., hide features based on X-User-Type headers, query params, or session data).
• You’re using Laravel’s gates/policies but need UI-level conditional rendering without custom Blade logic.
• You need lightweight feature flags for admin tools (e.g., ?debug=true to show hidden dev bricks).
• Your team uses SB Admin’s Bootstrap 5 theme and wants to avoid custom SCSS for conditional styling.
• Last release (1.18.4) aligns with your maintenance needs (check GitHub for backporting to LTS Laravel versions).

Look elsewhere if:

• You need complex permission systems (e.g., nested roles, attribute-based access control). Use Filament or Backpack instead.
• Your app requires server-side conditional logic (e.g., hide bricks based on database queries). This package only supports request-level conditions.
• You’re using headless APIs or SPAs (package is Twig-centric).
• You need real-time updates (e.g., hide/show bricks via WebSocket events). Pair with Laravel Echo or use Livewire for dynamic UIs.

How to Pitch It (Stakeholders)

For Executives: *"This update adds ‘admin panel feature flags’—we can now hide or show sections of our internal dashboards dynamically, based on user roles, request data, or even URL parameters. For example:

• Content moderators see ‘Flag Content’ buttons, but editors don’t.
• QA teams can enable hidden ‘Debug Tools’ via ?debug=true without code changes. This cuts dev time for permissioning by 80% compared to custom Blade logic, and it’s free (MIT license). Perfect for projects like [X tool] where we need to segment access without over-engineering."*

For Engineering: *"New in 1.18.4: Conditional bricks/tabs/actions via request attributes. How it works:

• Config-driven: Add hide_if: request->hasHeader('X-Hide-Bricks') to your crudit.yaml.
• Flexible: Supports query params (?hide=actions), headers, or session data.
• Limitations: Only request-level conditions (no DB queries). Avoid for complex logic—use Laravel gates instead. Use case: Ideal for [Project Y] where we need to hide ‘Bulk Export’ for non-admins. Pair with authorize() middleware for server-side checks."*

For Design/UX: *"This change lets us control UI visibility without touching CSS. For example:

• Hide the ‘Delete User’ tab for editors via hide_if: auth()->user()->cannot('delete-users').
• Show a ‘Beta: New Analytics’ brick only to users with ?feature=analytics in their URL. Tradeoff: Still uses SB Admin’s Bootstrap 5 theme, but now you can toggle entire sections without redesigning. For pixel-perfect control, combine with custom Twig templates."*