Exp Platform Ng Subtree Copy With Layouts Laravel Package

Product Decisions This Supports

• Content operations at scale: This package (a PHP extension in the Ibexa/eZ Platform family, distributed via Composer) automates duplicating content subtrees including layout definitions. That removes a recurring manual task from editorial operations — spinning up a new site section, regional/locale variant, or campaign microsite from an approved content template.
• Build vs. buy (vs. build-internally): If your roadmap includes multi-site rollouts, content templating, or "clone this section for a new market" workflows, this is a candidate to adopt rather than hand-rolling subtree-copy logic against the content repository API. The internal build cost is not the copy itself — it's the edge cases around references, locations, and layout bindings.
• Platform/stack roadmap signal: Note the ecosystem mismatch. Despite the "PHP package" framing, this is not a Laravel package — it targets the Ibexa/eZ Platform (Symfony) content model. Adopt it only if your platform roadmap is Ibexa-based. If your roadmap is Laravel, this is a no-go and the decision is closed.
• Risk/upgrade planning: v1.0.0 is an initial tagged release, and the only published artifact is an auto-generated changelog link — no feature list, no migration notes, no support statement. Treat this as "exists and is tagged," not "production-ready." That is a decision input, not a blocker.
• Vendor/fork governance: The se7enxweb namespace indicates a fork or vendor-specific derivative of upstream subtree-copy tooling. If you adopt, you inherit a fork-maintenance dependency and should budget for the possibility of upstreaming or self-maintaining.

When to Consider This Package

Consider it when all of the following hold:

• Your CMS is Ibexa/eZ Platform (or a compatible derivative) — not Laravel, not a generic PHP app.
• You have a repeatable need to duplicate content subtrees with layout configuration preserved, and doing it by hand is error-prone or slow.
• You can pin to v1.0.0 (or a specific commit) and validate it in a staging environment against your own content model before it touches production.
• You have engineering capacity to read the source — because the release notes give you nothing to read.

Look elsewhere when:

• You're on Laravel. This doesn't apply. Don't spend roadmap time on it.
• You need vendor-backed SLAs, LTS guarantees, or documented upgrade paths. A v1.0.0 with an empty changelog offers none of that.
• Your content model uses custom layouts/field types that the fork may not have been tested against; the absence of release documentation means the compatibility surface is unknown until you test it.
• A supported upstream package (e.g., the Netgen subtree-copy tooling this appears to derive from) already covers your need and has a maintained release history — prefer the upstream unless this fork adds something specific you require.

How to Pitch It (Stakeholders)

For executives: This is a small, free, open-source extension that automates copying a section of our website — content and its page layouts — so we can stand up new markets, campaigns, or site sections without rebuilding them by hand. It's a tactical efficiency gain for the content team, not a strategic platform bet. The catch: it's a version 1.0.0 with no published documentation or support, and it only works on our Ibexa-based stack, not on Laravel. Recommendation: pilot it on one low-risk section, measure hours saved per rollout, and only then decide whether it becomes standard tooling. Cost is engineering evaluation time, not licensing.

For engineering: Initial tagged release, fork namespace (se7enxweb), no changelog content beyond an auto-generated commit link. Please (1) diff against upstream Netgen subtree-copy to understand what this fork changes, (2) confirm layout-copy behavior against our content type definitions, (3) pin the dependency to a commit hash and wrap it behind our own service so we can swap it out. Report back on test coverage and whether the fork is actively maintained before we commit to it in a production path.