Nova Pennant Laravel Package

Product Decisions This Supports

• Feature Flag Management in Nova: Enables product teams to manage feature flags (via Pennant) directly within Laravel Nova’s admin interface, reducing reliance on external tools or manual database updates. This aligns with a "single pane of glass" approach for product and engineering teams.
• Roadmap for Gradual Feature Rollouts: Supports A/B testing, canary releases, and phased rollouts without requiring custom backend logic or third-party integrations. Ideal for teams using Pennant for feature flagging.
• Build vs. Buy Decision: Avoids reinventing feature flag management UI in Nova, leveraging an existing, maintained package. Reduces dev time and technical debt compared to a custom solution.
• Use Cases:
  • Product managers controlling feature toggles without engineering intervention.
  • Engineering teams needing a centralized dashboard for feature flag states.
  • Marketing teams managing campaign-specific flags (e.g., promotions, experiments).
  • Compliance/legal teams requiring audit trails for feature activations.

When to Consider This Package

• Adopt if:
  • Your team already uses Laravel Nova for admin management and Pennant for feature flags.
  • You need a low-code/no-code way to expose feature flags to non-technical stakeholders (e.g., PMs, marketers).
  • Your feature flagging workflow requires real-time visibility and bulk updates (e.g., enabling a flag for a segment of users).
  • You prioritize consistency in tooling (avoiding disparate dashboards for flags and admin panels).
• Look elsewhere if:
  • You’re not using Pennant for feature flags (this package is Pennant-specific).
  • Your team lacks Laravel Nova or prefers a standalone feature flagging tool (e.g., LaunchDarkly, Flagsmith).
  • You need advanced analytics or multi-environment flag management (this package focuses on UI, not analytics).
  • Your feature flags are static or managed via config files (no need for a dynamic UI).
  • You require role-based access control (RBAC) beyond Nova’s default permissions (custom authorization logic may be needed).

How to Pitch It (Stakeholders)

For Executives:

"This package lets us manage feature flags directly in Nova, giving product teams the power to toggle features on/off without waiting on engineering. It’s like giving PMs a self-service dashboard for experiments, promotions, or beta features—saving time and reducing bottlenecks. Since it’s built on Pennant (our existing feature flag system), it’s a no-risk upgrade that aligns with our tech stack. Think of it as a ‘traffic cop’ for our product releases, with full visibility for the whole team."

Key Benefits:

• Faster iterations: PMs/marketers can enable/disable features instantly.
• Reduced dev overhead: No custom UI work needed for flag management.
• Single source of truth: Flags live alongside user/admin data in Nova.
• Scalable: Supports A/B tests, regional rollouts, and compliance checks.

For Engineering:

*"This integrates Pennant feature flags into Nova, so we can expose flag management to non-dev stakeholders without building a custom tool. It’s a lightweight wrapper that:

• Saves dev time: No need to build or maintain a separate flag dashboard.
• Leverages existing auth: Uses Nova’s permissions (e.g., restrict flag edits to specific roles).
• Plugs into Pennant: Full access to Pennant’s targeting rules, environments, and analytics (via Pennant’s native tools).
• Minimal setup: Just add PennantTool::make() to your Nova resource—no complex migrations or APIs.

Trade-offs:

• Not a replacement for Pennant’s core functionality (e.g., no advanced analytics here).
• Requires Pennant to be already in use.
• Custom authorization may be needed for granular control (e.g., ‘only PMs can toggle feature_x’)."*

Ask for:

• Confirmation that Pennant is the primary feature flagging tool (no redundant systems).
• Alignment on who needs access (e.g., ‘Can marketers edit flags?’).
• Budget for minor customization if default permissions aren’t sufficient.