Laravel Filament Publishable Laravel Package

Product Decisions This Supports

• Accelerated CMS Development: Enables rapid creation of publishable content workflows (e.g., blogs, marketing pages) within Filament, reducing time-to-market for editorial teams by 30–50% compared to custom builds.
• Unified Publishing Logic: Standardizes publishable fields (PublicationStatus, PublishedAt) across all Filament resources, ensuring consistency in UX and reducing cognitive load for content editors.
• Strategic Tech Stack Alignment: Reinforces Laravel Publishable as a core dependency, justifying its adoption if not already in use (e.g., for teams migrating from custom publishable logic).
• Roadmap Priorities:
  • Phase 1: Integrate into high-impact resources (e.g., PostResource, ProductResource).
  • Phase 2: Extend to Filament widgets (e.g., "Recently Published" dashboards).
  • Phase 3: Explore custom bulk actions (e.g., "Publish All Drafts").
• Build vs. Buy:
  • Buy: Justified for teams already using Laravel Publishable; saves weeks of dev effort vs. building Filament fields from scratch.
  • Build: Only if needing highly bespoke publishable UX (e.g., multi-step approval workflows) or avoiding AGPL.

When to Consider This Package

• Adopt if:
  • Your primary admin panel is Filament 4+ and you manage publishable content (e.g., CMS, e-commerce, internal docs).
  • You’re already using Laravel Publishable or willing to adopt it for model-level publishing logic.
  • Your team prioritizes developer velocity over deep customization (e.g., 80/20 rule applies).
  • You need quick wins for publishing workflows without sacrificing Filament’s native UI/UX.
• Look elsewhere if:
  • You’re not using Filament (e.g., Nova, Backpack, or custom admin panels).
  • Your publishable logic is highly complex (e.g., recursive relationships, custom validation rules beyond basic publish/schedule).
  • You require enterprise support or long-term maintenance guarantees (package has low adoption; evaluate risk tolerance).
  • Your project cannot use AGPL (check legal/compliance teams).
  • You’re on Laravel <11.0 or Filament <4.0 (compatibility constraints).

How to Pitch It (Stakeholders)

For Executives: "This package lets us ship publishable content workflows (like blog posts or product launches) 3x faster by integrating Laravel Publishable’s fields directly into Filament. Instead of building custom UI for ‘publish,’ ‘schedule,’ or ‘expire’ actions, we reuse battle-tested components—saving dev time and reducing technical debt. Low risk since it’s a lightweight wrapper for existing tools we’re already using. Ideal for our [CMS/e-commerce/internal tools] roadmap."

For Engineering: *"The package provides pre-built Filament fields for publishable models (PublicationStatus, PublishedAt, etc.), cutting boilerplate for CRUD resources. Key tradeoffs:

• Pros:
  • Zero custom code for standard publishable fields.
  • Works out-of-the-box with Filament 4+ and Laravel 11+.
  • Extensible via Filament’s modifyFormFields if defaults don’t fit.
• Cons:
  • Tight coupling to Laravel Publishable (but that’s a given if we’re using it).
  • Low community adoption (2 stars); monitor for updates.
  • AGPL license (confirm compliance). Recommendation: Pilot with one resource (e.g., PostResource) to validate before broader adoption."*

For Design/UX Teams: *"This package gives us consistent, Filament-native controls for publishing content without losing the admin panel’s polished UI. For example:

• A status badge (Draft/Published/Expired) in tables.
• A date picker for scheduling posts.
• Bulk actions to publish multiple drafts at once. No need to design custom components—we get Filament’s default styling and behavior."*