Filament Support Laravel Package

Product Decisions This Supports

• Admin/back-office roadmap: v1.0.0 provides ready-made Filament components for Forms, Actions, Tables, Infolists, and Summarizers, letting the team prioritize product-specific admin workflows instead of rebuilding generic UI primitives.
• Build vs. buy/adopt: For Laravel products already using Filament, adopting this package is likely cheaper than maintaining in-house coordinate pickers, publish-status selects, media uploads, and enum helpers.
• Content workflow decisions: PublishStatusSelect and the PublishStatuses enum standardize draft/pending/published/rejected states with colors, icons, and labels. This supports editorial approval and publishing UX decisions without custom status logic.
• Geo/location use cases: Coordinate and CoordinateMap enable admin-side location capture and read-only map display for records such as stores, assets, events, or service areas.
• Media/DAM decisions: SpatieMediaLibraryFileUpload with visibility configuration reduces effort for image/document upload flows in admin panels.
• Rollout and feature-flag decisions: Config toggles for modifiers.forms, actions, tables, infolists, and summarizers allow staged adoption or selective disabling by environment.
• Operational linking: FilamentAdminUrls supports notifications, emails, and support tooling that need deep links to model records in admin.
• Integration cost: Auto-registration lowers setup effort, making this a credible accelerator for internal tools and admin-heavy products.

When to Consider This Package

Consider adoption when:

• The product is built on Laravel + Filament and needs standard admin UI components quickly.
• The roadmap includes content publishing workflows, media uploads, or location-aware admin records.
• The team wants config-driven enable/disable behavior and wants to avoid maintaining similar custom components.
• You can accept dependencies on Filament conventions, Google Maps for coordinate features, Spatie Media Library for upload features, and the package’s enum/status assumptions.
• You are comfortable adopting a v1.0.0 package after checking Laravel/Filament version compatibility, upgrade policy, test coverage, and maintainer responsiveness.

Look elsewhere or build custom when:

• The app is not on Filament or uses a different admin stack.
• You need a full CMS, workflow engine, GIS/mapping platform, or digital asset management system beyond these admin primitives.
• Google Maps API usage, licensing, or API-key handling is a blocker.
• You need guaranteed long-term support/SLA or mature enterprise support not evident at v1.0.0.
• Your status model differs materially from draft/pending/published/rejected and would require forking the enum/select.

How to Pitch It (Stakeholders)

For executives: This is a low-cost admin acceleration package for Laravel/Filament products. It can shorten delivery of back-office screens for publishing, media, and location data, while config toggles let us roll out safely. It is not a full CMS or GIS platform; value depends on already using Filament.

For engineering: v1.0.0 adds auto-registered Filament modifiers plus concrete form/infolist components, a publish-status enum, a media upload component, and an admin URL trait. It reduces duplicate component code and provides config-based feature toggles. Main diligence items are Filament/Laravel compatibility, Google Maps and Spatie Media Library dependencies, and v1.0.0 maturity.

For product: Treat it as a build-vs-adopt lever for admin workflows: use it to ship editorial status, media upload, and coordinate capture/display faster, and keep bespoke work focused on product-specific rules rather than generic Filament UI.