Laravel Mutable Content Filament Laravel Package

Product Decisions This Supports

• Deciding whether to treat durations as first-class product data—e.g., lesson length, media runtime, recipe prep/cook time, session duration—instead of custom strings or raw numeric fields.
• Supporting editorial format choices for text content: plain text vs Markdown, with Markdown edited in a dedicated editor and rendered in detail views.
• Roadmap planning for content-heavy Laravel admin experiences without building custom field types for durations and formatted text.
• Build-vs-buy evaluation for flexible content modeling: adopt when standard duration/Markdown fields cover the use case; build custom when editorial workflows, approvals, localization, or advanced rich-text behavior are core differentiators.
• Prioritizing admin UX improvements that reduce training/support burden and make content entry more consistent across forms, detail pages, and tables.

When to Consider This Package

• Your Laravel application already uses mutable content blocks and admin forms/infolists/tables where flexible field types are valuable.
• You need duration entry with a display unit—seconds, minutes, or hours—rather than forcing users to convert values manually.
• You want Markdown as a supported text format, including editor support and rendered output in detail views, while keeping tables plain-text for scanability.
• You are comfortable adopting a pre-1.0 package and managing its dependency constraint on amarenkov/laravel-mutable-content ^0.7.11.
• Look elsewhere if you need full WYSIWYG/rich-text editing beyond Markdown, complex content governance, localization workflows, granular permissions, versioning, or a stable 1.x API guarantee.
• Also look elsewhere if your stack is not Laravel or does not use compatible form/infolist/table admin surfaces.

How to Pitch It (Stakeholders)

For executives: v0.8.2 is an additive release that improves content authoring without requiring a custom admin build. It adds duration fields with user-friendly unit display and Markdown formatting for text fields, which can speed delivery of content-heavy features and improve editorial consistency. The main caveat is that the package is still pre-1.0, so engineering should treat upgrades with normal dependency discipline.

For engineering: the release adds duration fields and a text-field “Format” setting for plain text vs Markdown, including Markdown editor support and rendered infolist output. It requires amarenkov/laravel-mutable-content ^0.7.11. No breaking changes are called out in the notes, but the 0.x versioning and dependency coupling should be validated in the target app before adoption or upgrade.