Site Tree Laravel Package

Product Decisions This Supports

• Build vs. buy for site navigation and information architecture: This package is a candidate to replace an in-house hierarchical menu/site-tree module in Laravel applications, particularly those using Filament admin panels. A PM can use it to avoid spending sprint capacity on tree CRUD, nesting, and reordering plumbing.
• Roadmap sequencing: Adopting the package can accelerate delivery of navigation management, content hierarchy, and multi-level menu features, freeing the team to focus on differentiated product work.
• Use cases supported: Multi-level site navigation, content/category trees, sitemap-style structures, and admin-managed menu hierarchies.
• Release 0.3.2 assessment: The change is a patch-level improvement to site tree resource property types (PR #16). It does not add product capabilities or introduce breaking changes; it improves type correctness and developer experience in the admin resource layer. The product decision impact is low, but it is a positive maintenance signal.
• Version risk: The package is pre-1.0 (0.3.x). Patch releases like 0.3.2 are low-risk, but the 0.x versioning means minor releases may include breaking changes. Roadmap commitments should account for upgrade overhead.

When to Consider This Package

Consider adoption when:

• You are building a Laravel application that needs an admin-managed, hierarchical site tree or navigation structure.
• Your team uses Filament and wants a resource-based UI for managing tree nodes rather than building one from scratch.
• You want to reduce custom code and maintenance burden for tree CRUD operations.
• You can tolerate a pre-1.0 dependency and are prepared to pin versions and review changelogs before upgrades.
• The package’s documented features and Filament compatibility match your current framework versions.

Look elsewhere when:

• You need enterprise CMS capabilities such as editorial workflow, versioning, localization, granular permissions, or audit trails.
• You require a stable 1.0+ API contract or long-term support guarantees.
• Your stack is not Laravel/Filament, or you need framework-agnostic tree management.
• You have complex custom routing, URL generation, or caching requirements that the package does not cover.
• The package’s maintenance cadence, test coverage, or documentation does not meet your risk threshold after a technical spike.

How to Pitch It (Stakeholders)

For executives: This is a small, open-source Laravel package that can shorten delivery time for navigation and site-structure features by replacing custom-built admin tooling. The latest patch (0.3.2) is a low-risk type-safety improvement and shows active maintenance. Because it is pre-1.0, we recommend a short, timeboxed evaluation before committing it to the roadmap.

For engineering: The package integrates with Laravel/Filament and handles hierarchical site-tree management, including admin resource property typing improved in 0.3.2. It reduces boilerplate for tree CRUD and nesting. Risks are typical of a 0.x dependency: API instability, limited long-term guarantees, and Filament version coupling. Mitigate by pinning the version, running a spike against our target Filament/Laravel versions, and reviewing test coverage and upgrade notes before adoption.

Recommendation: Run a one-to-two-day proof of concept. If it fits, adopt behind a pinned version and include upgrade review in routine maintenance. If requirements include workflow, localization, or enterprise permissions, retain or build an in-house solution instead.