Layup Laravel Package

Product Decisions This Supports

• Build vs. buy for in-app page authoring. crumbls/layup provides a Filament-native page builder with templates, so a CMS/marketing-page surface can be shipped as configuration and content operations rather than a bespoke editor build. This release doesn't change that calculus, but it de-risks the "templates" pillar that most directly replaces custom engineering work.
• Template-driven content operations. Built-in and saved custom templates are the mechanism by which non-engineers (marketing, ops, regional teams) spin up landing pages without a developer. v1.7.0 fixes the case where a page created from a template opened empty — the most visible failure mode for that workflow and the one most likely to generate "the tool is broken" support tickets and abandonment.
• Feature and roadmap confidence in the editor surface. The fix is scoped to the New Page creation action in Filament 5 / Livewire 4, with six failing regression cases reproduced and nine now passing. That's a signal the package is actively maintained against the current Filament major, which matters if your roadmap assumes a Filament 5 admin.
• Upgrade timing decision. No migrations, asset rebuilds, or config changes — a low-cost patch upgrade that can ride along with a routine composer update. Reasonable to schedule in the current cycle rather than batching.
• Security/roadmap input. The release notes explicitly flag that the development lockfile audit reports advisories, including a high-severity CommonMark advisory, and recommend supported, patched dependency versions. That's a decision input for a dependency-review or security sign-off, not a blocker for this patch itself.

When to Consider This Package

Consider it when:

• Your admin is on Filament 5 / Livewire 4 — this release explicitly targets and regression-tests that stack.
• You need structured page authoring with reusable templates (built-in and saved custom) rather than a freeform rich-text field, and you'd otherwise build that editor yourself.
• You want the editor embedded in the existing Filament admin rather than standing up a separate CMS.
• You can absorb a patch-level upgrade with no schema or config changes, and you have a routine dependency-audit process.
• Your content model tolerates the documented limitation: previously created empty pages are not automatically repaired. Only newly created pages pick up template content.

Look elsewhere when:

• You need guaranteed, supported dependency hygiene out of the box — the noted advisories (including high-severity CommonMark) mean you'd be pinning/overriding transitive dependencies yourself.
• You need a migration path for already-broken content; this fix is forward-only, so existing blank pages require manual recreation.
• You're on older Filament/Livewire majors — the verification here is specific to Filament 5 / Livewire 4.
• You need localization, workflow/approval, or multi-site publishing — nothing in this release suggests that scope.

How to Pitch It (Stakeholders)

For executives: A small, low-risk bug fix in the page-builder package we use for in-admin content authoring. Pages created from a template were opening blank; they now retain the template's content. No database migrations, no config changes, no rebuilds — it ships with a normal dependency update. It protects the self-serve content workflow our marketing/ops teams rely on, and the package remains actively maintained against our current admin stack (Filament 5 / Livewire 4).

For engineering: Patch release v1.7.0 fixes template resolution at page-creation time (issue #78, PR #79). Template selection is resolved on create; clearing the selection yields a blank page, and changing templates honors the final selection. Verified through the real Filament 5 / Livewire 4 creation action — six regression cases failed pre-fix, all nine now pass, full suite at 1,239 tests / 3,930 assertions plus docs lint and PHP formatting. Dependency constraints unchanged. Two caveats to note in the upgrade ticket: existing empty pages are not backfilled, and the dev lockfile audit still reports advisories (including a high-severity CommonMark one) — worth triaging separately, not as a blocker for this bump. Upgrade: composer update crumbls/layup --with-dependencies.