Statamic External Link Laravel Package

Product Decisions This Supports

• Framework upgrade sequencing (the headline decision). v1.9.0 adds Statamic 5 and Laravel 11 support. This is the gating signal that lets the team schedule the Statamic 4→5 / Laravel 10→11 upgrade without carving out a replacement workstream for external-link handling. Treat this release as the "green light" input to that roadmap item.
• Build vs. buy for link hygiene. External link handling (target="_blank", rel="noopener noreferrer", and consistent link semantics in the CMS) is a solved, low-differentiation problem. The existence of a maintained addon that tracks current Statamic majors supports a "buy/adopt" decision rather than spending sprint capacity building custom fieldtypes or Antlers modifiers.
• Editorial UX scope. This package lets content editors author external links in the control panel without hand-writing attributes, which shifts link-attribute correctness from editorial discipline (unreliable) to system behavior (reliable). That influences whether we invest in editor training/guidelines or in tooling — the package moves budget toward tooling.
• Accessibility and SEO posture. Consistent rel attributes on outbound links are a small but real input to accessibility audits and to how we treat outbound link equity. Adopting a vetted addon is a cheap, defensible answer in an audit rather than an open question.
• Support-matrix decisions for the wider addon portfolio. Because this package now declares Statamic 5 / Laravel 11, it can be marked "cleared" in the upgrade dependency checklist. That unblocks other decisions — e.g., whether the remaining unmaintained addons force us to delay the upgrade or drop features.

When to Consider This Package

Adopt when all of the following hold:

• The site runs Statamic (this is a Statamic addon, not a general Laravel package) and is on, or moving to, Statamic 5 / Laravel 11 — which is exactly the compatibility window v1.9.0 opens.
• Editors author outbound links in the control panel and the team wants consistent external-link behavior (new tab, safe rel attributes) without editorial training or manual review.
• You want a small, single-responsibility addon rather than extending a broader SEO/link package.

Look elsewhere or skip when:

• You are still on Statamic 3 or Laravel 10 and have no near-term upgrade path — verify the older tagged release supports your versions before adopting, and pin accordingly.
• Your link attributes are already handled centrally (a shared Antlers/Blade partial, a link fieldtype with attribute presets, or a CDN/HTML post-processor). Duplicating that logic adds a dependency with no new capability.
• You need link auditing, broken-link detection, redirect management, or external-link analytics. This addon is scoped to markup behavior, not link governance — that is a separate buy decision.
• The package's maintenance cadence is the deciding factor and cannot be verified. v1.9.0 is a compatibility release, not a feature release; confirm commit history and issue responsiveness before making it a hard dependency of the upgrade plan.

How to Pitch It (Stakeholders)

To executives (one paragraph): We use a small open-source addon that makes outbound links on our Statamic site behave correctly — opening in a new tab and carrying the standard security attributes — without relying on editors to get it right by hand. The new release (v1.9.0) is a compatibility update: it confirms the addon works with Statamic 5 and Laravel 11, the framework versions our platform upgrade depends on. That removes one blocker from the upgrade and costs us nothing to adopt. It is a maintenance release, not a new capability, so there is no new budget ask — the decision is simply to keep the dependency and proceed with the upgrade.

To engineering: v1.9.0 is purely a support-matrix release — Statamic 5 and Laravel 11 added, no new features, no documented breaking changes, no deprecations. Recommended actions: (1) bump the constraint and run the upgrade branch against it; (2) add it to the "cleared" list in the dependency tracker; (3) confirm the previous tag still covers any environments we are not upgrading this cycle, since the addon now spans multiple Statamic majors; (4) smoke-test external link rendering in the CP and on the front end after the bump — compatibility releases widen supported ranges, they do not guarantee behavior is unchanged on every code path. Note that this release contains no data beyond the compatibility declarations, so treat feature-level regression risk as low but unverified.