Laravel Filament Publishable Laravel Package

Product Decisions This Supports

• Content Lifecycle Management: Enables seamless draft-to-published workflows in Filament, reducing reliance on third-party CMS tools (e.g., Strapi, WordPress). Ideal for internal editorial systems or headless CMS backends where content moderation and scheduling are critical.
• Roadmap Prioritization:
  • Short-term: Accelerate Filament resource development for publishable models (e.g., blog posts, product listings) by 30–50%, reducing time-to-market for content-heavy features.
  • Long-term: Justify adopting Laravel Publishable as a foundational trait for content models, ensuring consistency and scalability across the codebase. Aligns with a modular content architecture where publishable states are standardized.
• Build vs. Buy:
  • Buy: This package is a low-risk, high-reward choice for teams already using Laravel Publishable. Avoids reinventing Filament fields for publishable states (status, dates, bulk actions) while maintaining alignment with Filament’s design system.
  • Build: Only if you need highly customized publishable UX (e.g., multi-step publishing workflows, custom validation logic, or integration with third-party services like Webflow or Contentful) or are not using Laravel Publishable.
• Use Cases:
  • Editorial Systems: Manage articles, guides, or marketing pages with versioning, scheduling, and expiration (e.g., news sites, documentation portals).
  • E-commerce: Control product visibility (e.g., seasonal promotions, A/B tests, or regional releases) via Filament’s publishable workflows.
  • Internal Tools: Publishable statuses for internal documentation, announcements, or approval workflows (e.g., HR policies, project updates).
  • Localization: Combine with Filament’s localization features to manage multi-language publishable content (e.g., translating and publishing blog posts in multiple languages).
  • API-First Apps: Use publishable models as a backend for headless frontend apps (e.g., React, Vue, or mobile apps) where content is managed in Filament but consumed via APIs.

When to Consider This Package

• Adopt if:
  • Your team already uses or is committed to adopting novius/laravel-publishable for model-level publishing logic.
  • You’re building a Filament 4+ admin panel and need pre-built publishable fields (status, dates, bulk actions) to avoid custom development.
  • You prioritize developer velocity over deep customization, and the package’s defaults align with your design system and workflows.
  • Your content models require basic publishable workflows (draft → publish → expire) with minimal overhead, and you lack the bandwidth to build these from scratch.
  • You need to integrate publishable content into Filament’s table filters, bulk actions, and notifications without writing boilerplate code.
• Look elsewhere if:
  • You’re not using or not planning to use novius/laravel-publishable (this package is tightly coupled; consider custom Filament fields or alternatives like spatie/laravel-activitylog for audit trails).
  • You need advanced publishable features beyond standard status management (e.g., recursive publishing, custom validation rules, or workflows with approval chains).
  • Your team prefers Filament v3 or Laravel <11.0 (compatibility constraints may require significant workarounds).
  • You require enterprise-grade support or SLAs (the package has low adoption; evaluate maintenance risk and forkability).
  • Your application cannot use AGPL-licensed packages due to legal/compliance restrictions (consult legal teams before adoption).
  • You need highly customized UI/UX for publishable states (e.g., custom modals, multi-step publishing, or integration with design systems like Tailwind or Bootstrap).

How to Pitch It (Stakeholders)

For Executives: "This package allows us to manage publishable content—like blog posts, product listings, or internal announcements—directly within Filament with minimal development effort. By integrating Laravel Publishable’s fields into Filament, we can reduce development time by 30–50% while maintaining a consistent, scalable admin experience. It’s a low-risk, high-impact solution for teams already using Laravel Publishable, enabling faster launches of content-heavy features without sacrificing quality. Ideal for editorial systems, e-commerce visibility controls, or internal tools where content lifecycle management is critical."

For Engineering: *"The package provides pre-built Filament fields for publishable models (PublicationStatus, PublishedAt, ExpiredAt), eliminating weeks of manual UI development. Key benefits:

• Zero custom code for standard publishable workflows—just drop fields into your Filament resource.
• Works out-of-the-box with Filament 4+ and Laravel 11+, leveraging modern Laravel features.
• Extensible: Override defaults or add custom logic via Filament’s modifiers if needed. Tradeoffs:
• Tight coupling to Laravel Publishable (but this is a given if you’re using it).
• AGPL license (verify compliance with legal teams).
• Low adoption (3 stars, 0 dependents)—monitor for updates but low maintenance risk for basic use cases. Recommendation: Start with a pilot resource (e.g., PostResource) to validate fields, then expand. If gaps emerge, we can extend the package or build custom Filament components."*

For Design/UX: "This package gives us consistent, pre-built UI components for publishable content in Filament, ensuring a polished admin experience without custom design work. Fields like PublicationStatus (dropdown) and PublishedAt (date picker) align with Filament’s design system, reducing friction for content editors. If we need custom styling, we can override defaults using Filament’s theming system or CSS variables. It also supports bulk actions (e.g., publish/unpublish multiple items at once), which improves efficiency for moderators."

For Product Managers: *"This package directly supports our roadmap for content lifecycle management in Filament, enabling faster iterations for features like:

• Scheduled publishing (e.g., blog posts, product launches).
• Expiration workflows (e.g., limited-time promotions, time-sensitive announcements).
• Multi-language content (combined with Filament’s localization features). By adopting this, we can reduce dependency on third-party CMS tools and keep content management in-house, with full control over UX and integrations. It’s especially valuable for editorial teams who need intuitive tools to manage drafts, reviews, and publishing."*