Statamic Uuid Laravel Package

Product Decisions This Supports

• CMS upgrade planning: v2.4.0 adds Statamic v6 support, removing a dependency blocker for teams planning or evaluating a Statamic v6 upgrade.
• Build vs. buy: Validates using a small open-source add-on for UUID generation/field behavior instead of maintaining custom UUID logic in application code.
• Integration roadmap: Supports stable, externally referenceable content identifiers for APIs, content sync, analytics, webhooks, and third-party systems that should not depend on internal CMS IDs.
• Risk management: A compatibility-only release is low product risk; the main decision is whether the add-on remains in the critical path for content identity during the CMS upgrade.
• Use cases: External content references, import/export matching, deduplication, audit trails, stable links, and systems that need UUIDs on Statamic-managed content.

When to Consider This Package

• You are using Statamic and need UUID-based identifiers for content or fields.
• You are planning a Statamic v6 migration and need the add-on to remain compatible.
• You want a maintained, narrowly scoped package rather than custom UUID field logic.
• You need stable IDs for integrations but do not need a broader content modeling or sync platform.

Look elsewhere if:

• You are not using Statamic, or native Statamic/Laravel identifiers already satisfy the use case.
• You need full PIM/content-sync, custom ID governance, or UUID lifecycle management beyond a field/add-on.
• You are staying on an older Statamic version and have no near-term upgrade path; v2.4.0 is mainly relevant for v6 compatibility.
• You require vendor-backed SLAs or extensive support commitments.

How to Pitch It (Stakeholders)

Executives: v2.4.0 is a small but important compatibility release: it keeps the UUID add-on usable with Statamic v6, reducing a potential blocker in the CMS upgrade roadmap. It is low-cost, low-scope, and supports stable content identifiers for integrations without custom development.

Engineering: Treat v2.4.0 as a Statamic v6 compatibility update rather than a feature release. Validate it in the upgrade branch, confirm UUID field behavior and existing content references, and check dependency constraints before rollout. No broad feature migration is implied, but regression testing around content IDs and integrations is warranted.