Statamic Super Location Laravel Package

Product Decisions This Supports

• Statamic 6 upgrade planning: v2.0.0 adds Statamic 6 support for the Super Location fieldtype, making this package relevant to CMS/platform migration decisions. If the product roadmap includes a Statamic 6 move, this release removes a compatibility blocker for location-based content fields.
• Build vs. buy for location content: Supports buying/adopting a maintained fieldtype instead of building custom location capture, geocoding, or editorial location workflows. The value is highest when teams need structured location data in Statamic without owning addon maintenance.
• Content modeling use cases: Enables PM decisions around store locators, event venues, real-estate/property listings, regional landing pages, office directories, and other content types requiring address/coordinate-style fields.
• Roadmap dependency management: Treat v2.0.0 as a compatibility release rather than a net-new feature release. PM should track it as an upgrade enabler and validate whether v2 introduces breaking changes for existing field data, templates, or editorial workflows.
• Risk decision: Major-version support for Statamic 6 is positive, but PM should confirm ongoing maintenance, licensing, and migration path before standardizing on it across products.

When to Consider This Package

Consider this package when:

• The product uses Statamic 6 or is actively planning a Statamic 6 migration.
• Editorial teams need a location-oriented fieldtype for structured address/location content in the CMS.
• The team wants a buy/adopt path instead of custom-building Statamic fieldtype behavior, validation, and editorial UX.
• The location field is a standard content-modeling need, not a deeply specialized GIS or geospatial analytics requirement.
• The team can absorb a major-version upgrade and test field data, templates, and editor workflows.

Look elsewhere or defer when:

• The product remains on an older Statamic version and has no Statamic 6 roadmap; pin the prior compatible version instead.
• Requirements include advanced GIS, routing, spatial queries, or proprietary geocoding pipelines beyond a CMS fieldtype.
• The package has unclear maintenance, licensing, or upgrade support after the major release.
• The team cannot validate breaking changes or field-data compatibility before upgrading.

How to Pitch It (Stakeholders)

For executives: v2.0.0 is a compatibility release that supports Statamic 6 for the Super Location fieldtype. It matters because it protects the CMS upgrade path and reduces the need to custom-build location content fields. The decision is whether to standardize on this addon for location-based content or defer until the Statamic 6 migration is funded and tested.

For engineering: Treat v2.0.0 as a major-version compatibility update. Validate Statamic 6 addon APIs, fieldtype registration, stored field data, template rendering, and editorial workflows. Confirm whether existing content requires migration or re-saving, and pin v1 for projects not yet on Statamic 6. The release is valuable primarily as an upgrade enabler, not as a new product capability.