Filament Blog Laravel Package

Product Decisions This Supports

• Build vs. buy for content primitives. Ink already covers posts, slugs, and soft-delete semantics; the v2.5.1 fix means slug uniqueness and reuse are now handled by the package rather than by custom application logic. This is evidence against building a bespoke content layer for a Laravel product.
• Roadmap: AI/agent-facing content operations. Adding slug to the package's MCP tools confirms an intentional investment in exposing content to AI agents/clients. If an "AI-assisted authoring" or "content ops automation" item is on the roadmap, this package now supplies part of the interface layer, reducing scope and timeline for that work.
• Feature decision — slug recycling policy. Freeing slugs held by soft-deleted posts is a product behavior change, not just a bug fix: deleting content now releases its URL for reuse. PMs must decide whether that is desired (avoids slug exhaustion, enables re-publishing under a clean URL) or whether permanently reserved permalinks are required for SEO and inbound-link stability. The former is now the default; the latter requires app-level handling (redirects, tombstone slugs).
• Use cases unlocked. Marketing/blog, docs, changelogs, and any slug-addressed resource — plus agent-driven creation/editing of that content via MCP tools.

When to Consider This Package

• Adopt when: you're on Laravel, need posts with human-readable slugs, want soft-delete behavior, and either already use or plan to use MCP-based AI tooling against your content.
• Look elsewhere when: you need a full CMS (editorial workflow, roles, scheduling, revisions), first-class multi-language content, or a non-Laravel stack.
• Watch out when: permanent permalinks matter. Because soft-deleted posts no longer hold their slug, a later post can claim a previously published URL. If SEO equity or existing backlinks are at stake, plan an app-level redirect/tombstone strategy before upgrading — otherwise old links may silently resolve to new, unrelated content.
• Caveat on MCP: treat the MCP surface as still maturing. Its tool contract changed in a patch release (slug added), so pin versions and re-verify agent tool schemas on each upgrade.

How to Pitch It (Stakeholders)

Executives: A small but strategically useful patch. It tightens content integrity (slug ownership now behaves predictably around deleted posts) and extends the package's AI-agent interface to include slugs — incremental progress on making our content operable by automated assistants, at zero additional build cost.

Engineering: v2.5.1 fixes a correctness bug where soft-deleted posts continued to reserve their slugs, and adds slug to the MCP tool payloads. No breaking API changes signalled, but the MCP tool contract did change in a patch — pin the version and re-check any agent integrations. Before rollout, confirm the product stance on slug reuse after deletion, since freeing slugs is a deliberate behavioral choice with SEO implications.