Statamic Splash Laravel Package

Product Decisions This Supports

• Editorial velocity vs. tooling investment. The addon answers a concrete workflow question: should editors leave the CMS to source stock imagery, or should sourcing happen inside the Statamic Control Panel? Adoption is a cheap way to test whether in-CP image sourcing measurably reduces time-to-publish for content teams.
• Build vs. buy for a media integration. An Unsplash browser is a small but non-trivial integration (API auth, search UI, fieldtype wiring, asset handling). This package is the "buy" option — a free, MIT-licensed shortcut versus spending engineering days on an in-house equivalent.
• Roadmap signal for the media/asset layer. Usage data from this addon (how often editors insert stock images, which content types, how often they then replace them with owned assets) is evidence for or against investing in a proper DAM, licensed stock subscription, or a curated internal image library.
• Procurement and cost avoidance. For low-stakes imagery — blog headers, placeholder art, internal comms, prototypes, landing page drafts — it can substitute for per-seat stock subscriptions during discovery or for non-brand-critical properties.
• Use cases it fits: marketing microsites, editorial blogs, documentation illustrations, internal tools, agency prototypes and demos where speed matters more than brand-specific imagery.
• Use cases it does not fit: brand-controlled hero imagery, regulated content, anything needing license indemnification, or high-traffic pages where image delivery performance is a conversion lever.

When to Consider This Package

Consider it when:

• You are already on Statamic (Laravel-based flat-file CMS) and your editors work primarily in the Control Panel.
• The imagery need is generic and brand-agnostic, and "good enough" stock beats "perfect but slow."
• You can accept the Unsplash API terms: attribution to the photographer, hotlinking images from Unsplash's CDN rather than re-hosting, triggering the download endpoint on use, and respecting rate limits (the demo tier is small; production requires an application and higher limits).
• Your team is comfortable owning a small, low-adoption dependency (13 stars, effectively a single maintainer). MIT licensing means you can fork or vendor it if it goes stale, so the real question is whether you have appetite for that, not whether it's possible.
• You are running a pilot, an internal tool, or a content surface where a third-party image request failing is a cosmetic problem, not an outage.

Look elsewhere when:

• Brand or legal requires indemnified, licensed stock (Getty, Shutterstock, Adobe Stock) or an enterprise DAM with rights metadata.
• You need guaranteed support, an SLA, or a security review with a named vendor — a 13-star addon will not clear most enterprise third-party risk processes without an internal fork and owner.
• You need local image transformation, responsive variants, CDN optimisation, or offline/air-gapped operation. Hotlinked Unsplash assets can't go through your normal image pipeline, and every page view becomes a request to a third party — relevant for privacy posture (GDPR/consent), performance budgets, and availability.
• Editors need to manage assets (folders, alt text governance, usage tracking) rather than just find them.
• The stack is not Statamic — nothing here transfers to vanilla Laravel or another CMS.
• The last-release metadata (2026-08-30) reads as a forward-dated or anomalous entry; verify actual commit activity, Statamic version compatibility, and open issues before committing.

How to Pitch It (Stakeholders)

For executives: This is a small, free, MIT-licensed convenience layer that lets content editors search and insert Unsplash photography without leaving the CMS. It's a workflow accelerator, not infrastructure. The upside is editor speed and avoided stock-subscription cost on low-stakes content; the downside is that it depends on a third-party API and a single-maintainer open-source project. Treat it as a pilot with a clearly bounded scope — a handful of content types, non-brand-critical pages — and a removal cost near zero if it doesn't earn its place.

For engineering: Thin addon, small surface area, MIT and forkable, so vendor risk is manageable if someone owns it. Requirements: an Unsplash API key and secret in config, awareness of rate limits, and a compliance check against Unsplash's attribution and hotlinking rules before it reaches production. Confirm compatibility with your Statamic version and review how it handles inserted assets (hotlink vs. download) — the latter matters for both terms compliance and your image pipeline. Budget half a day for install, key management, and a content-type pilot; budget a fallback path (manual upload) so an Unsplash outage is never a publishing blocker.

Recommendation: Pilot on one non-critical content collection, measure editor time-to-publish and how often stock images survive to final copy, and revisit in one quarter. If it sticks, assign an internal owner and pin a fork; if it doesn't, delete the addon.