Url Field Type Laravel Package

Product Decisions This Supports

• Content modeling for link-centric content. Gives the Streams/PyroCMS content model a first-class url field type, so "external link," "source URL," "CTA destination," or "resource link" becomes a typed, validated attribute on an entry rather than free-text in a body field. That distinction matters later — typed fields can be validated, queried, validated again at render time, migrated, and audited. Generic text fields cannot.
• Build vs. buy (buy-small). For a team already on Anomaly Streams, this is a sub-day build replaced by a composer require. It is a legitimate "buy" in the narrow sense: the cost is a dependency line and a code review, not a license or integration project.
• Roadmap enablers it unlocks cheaply. Once URLs are structured data, link health checks, outbound-link reporting, canonical URL management, and "related resources" blocks become additive features rather than schema migrations. It is a cheap down-payment on a link-management roadmap.
• Use cases it directly serves: resource/press/directory entries, partner and integration endpoint listings, CTA and navigation targets in a CMS, external reference tracking in editorial workflows.
• Decision it does not support: any evaluation outside the Anomaly ecosystem, or any requirement for advanced link behavior (link text, target, rel/no-follow policy, internal route resolution, click tracking). Those are not in scope for a bare URL field type and should not be assumed.

When to Consider This Package

Consider it when:

• You are already running the Anomaly Streams Platform (or PyroCMS built on it) and are assigning fields to streams. This is the only context in which the package is more than dead weight.
• You want a URL field that participates in the platform's existing field-type contracts (validation, configuration, presenter) rather than a bespoke text field plus a regex.
• You value auditability over features: MIT, one class of responsibility, small enough to read in full before merging.
• The requirement is genuinely "store and validate a URL" — nothing more.

Look elsewhere when:

• You are on vanilla Laravel or any CMS that is not Streams. There is no meaningful integration path; Laravel's built-in url validation rule plus a cast or value object covers the same ground in an afternoon.
• You need link semantics beyond a string: link text, target, rel, internal vs. external resolution, or link-rot monitoring. Budget for a custom field type.
• You need maintenance assurance. One star, zero dependents, and no visible downstream usage means no community validation and no de facto support contract. Pin the version, vendor it if it is load-bearing, and assume you own the code.
• You are making a platform-level or long-horizon architectural bet. This is a utility, not a foundation.

How to Pitch It (Stakeholders)

To executives: This is a small, MIT-licensed add-on that adds a URL field type to our CMS's content model. It costs nothing, carries no license or procurement overhead, and is small enough that our engineers can fully review it before use. The strategic value is modest but real: it turns links into structured, validated data, which is the prerequisite for any future link-reporting or link-health feature. The strategic risk is also modest: adoption is effectively zero, so we should treat it as code we are adopting rather than a vendor we are relying on. Recommendation: approve for evaluation only if we are already on the Anomaly Streams platform; do not treat it as a reason to adopt that platform.

To engineering: One composer dependency, standard field-type registration, no transitive dependency surface worth worrying about, MIT so we can fork freely. Two conditions: pin the version and review the source before merge, because the project shows no signs of active maintenance; and confirm the fallback cost is genuinely low — if the package disappears, replacing it is roughly a day of work, which is the best risk mitigation available here. If we are not on Streams, do not evaluate it — use Laravel's url rule and move on.