Product Decisions This Supports
- Feature scoping for content distribution. Social sharing links are a recurring "table stakes" requirement on any publishing surface (blog, news, docs, changelog, landing pages). This package answers the question "how much build effort should that get?" with very little — it's a thin renderer of share URLs, not a distribution or analytics system.
- Build vs. buy, resolved toward "buy cheap." At MIT license and near-zero integration surface, the cost of adopting is a few lines of template config; the cost of building is roughly a Blade/Antlers partial plus per-network URL maintenance. The decision is only interesting if you're already on Statamic.
- Roadmap placement. Treat as an enabler for a "share your content" line item, not a roadmap item itself. It does not unlock share counts, referral attribution, Open Graph image generation, or social scheduling — scope those separately or explicitly deprioritize them.
- Use cases it fits: editorial sites where marketers/editors want per-collection control over which networks appear; Statamic sites where content authors want share links without a developer touching templates each time a network is added or removed.
- Use cases it does not fit: growth experiments that need click-through measurement, mobile-first products where the native Web Share API is the better UX, or any product where the share button is a measurable funnel step.
- Dependency posture. Six stars and zero dependents means this is not an ecosystem-blessed choice; it's a small utility with a single maintainer. That's acceptable for a leaf-node UI concern, and unacceptable if share links ever become business-critical (they usually don't).
When to Consider This Package
Consider adoption when:
- The product already runs Statamic (this is a Statamic addon, not a general Laravel package — confirm before anyone adds it to a Laravel-only service).
- You want config-driven network selection per collection or page type rather than hardcoding four anchors in a template.
- You want the share-link concern to live in CMS configuration so editors can toggle networks without a deploy.
- You're comfortable with a single-maintainer, MIT, low-star dependency whose blast radius is a handful of
<a href> tags — i.e., a bug produces broken links, not broken checkout.
- The maintenance signal is current (recent release), so the immediate abandonment risk is low.
Look elsewhere or build in-house when:
- The stack is plain Laravel/Livewire or another framework — write the seven URL strings yourself; you'd spend more time on the dependency than the feature.
- You need share counts, UTM/attribution plumbing, or click analytics — this class of package is a URL builder, not an instrumentation layer.
- You need native mobile sharing (Web Share API) or a JS SDK-driven experience (e.g., rich embeds, per-platform previews).
- You're subject to procurement or security review that penalizes zero-dependent, low-visibility dependencies; a 20-line template is easier to defend than a third-party addon.
- You need a guaranteed SLA or vendor support contract.
How to Pitch It (Stakeholders)
To executives: This is a small, free, MIT-licensed addon that adds "share to social" buttons to our published content, configured by editors rather than engineers. Total cost is hours, not sprints, and there is no licensing, procurement, or vendor commitment. It does not give us share analytics or referral attribution — if social distribution becomes a growth channel we care about measuring, that's a separate initiative and a separate budget.
To engineering: It's a thin Statamic addon that renders per-network share URLs from config; the integration surface is a tag in a template and a YAML config block. Everything it does is reproducible in a single partial if we'd rather not carry the dependency. Risk is contained: MIT license, one maintainer, zero dependents, small codebase — forkable in an afternoon. Two guardrails: it's Statamic-specific (don't reach for it in plain Laravel services), and we should pin the version and keep our own smoke test on the rendered links, since there's no ecosystem backstop if a network's share URL changes.
Recommendation: Adopt if we're on Statamic and need editor-configurable share links; otherwise implement directly in the template. In either case, do not let this package's existence imply we've "solved" social distribution — it's the button, not the strategy.