Shariff Bundle Laravel Package

Product Decisions This Supports

• Privacy/compliance roadmap: Shariff is the reference implementation for GDPR/DSGVO-conscious social sharing — buttons render as static links, and the share count is fetched server-side (or not at all), so no user data leaks to Facebook, X, LinkedIn, etc. on page load. This package is one delivery mechanism for that capability in a Symfony2 codebase.
• Build vs. buy on the “share” surface: The decision is really “adopt the Shariff PHP backend” vs “keep native share buttons or a third-party widget.” This bundle is a thin Symfony2 wrapper around that backend; the strategic commitment is to Shariff, not to this repo.
• Legal-risk reduction: German case law (e.g., the Google Fonts ruling) has made third-party embeds a live liability. Moving share buttons behind Shariff is a defensible, auditable posture that product and legal can point to.
• Feature scope: Shariff supports a fixed set of networks and share-count services. If the roadmap includes niche networks or rich share previews, this constrains the UX you can ship.
• Not a Laravel decision: The package is a Symfony2 bundle, not a Laravel package. For a Laravel codebase, this specific repo informs “should we adopt the Shariff backend?” — not “can we composer require this?”

When to Consider This Package

Consider it when:

• You are maintaining a Symfony2 application (or genuinely evaluating one) and need Shariff integrated quickly as a bundle.
• The driving requirement is EU/German privacy compliance for social sharing, and you want the canonical Heise/Shariff behavior rather than a homegrown approximation.
• You need a small, stable, read-only integration — Shariff's backend surface is narrow and low-churn, so even a lightly maintained wrapper can be acceptable if you vendor and pin it.

Look elsewhere when:

• You are on Laravel. A Symfony bundle cannot be dropped in. Use the underlying Shariff PHP backend directly, or write a thin service/controller adapter — a few hours of work, and you own the maintenance.
• You are on modern Symfony (4/5/6/7). Symfony2 is long EOL; this bundle's service definitions and PHP constraints will not load. Integrate the backend directly or use a maintained bundle.
• Maintenance signal matters. Zero stars and zero dependents means no community, no security review, and no upgrade path. Treat it as unmaintained source code, not a dependency.
• You need anything beyond the classic share-button UX — analytics, A/B tests, custom network sets, or share-count aggregation beyond what Shariff's backend exposes.

How to Pitch It (Stakeholders)

To executives: “Social share buttons are a legal and privacy exposure: today, loading a page hands user data to Meta, X, and LinkedIn before anyone clicks. Shariff is the established German-made pattern that removes that exposure while keeping the share buttons users expect — this package is one way to wire Shariff into an older Symfony codebase. The strategic call is whether we adopt Shariff as our sharing standard. The wrapper itself is small and low-risk; the compliance benefit is the reason to do it.”

To engineering: “This is a Symfony2 bundle around the Shariff PHP backend — not a Laravel package, despite how it's often labeled. If we're on Symfony2, it saves integration time; on Laravel or modern Symfony, skip the bundle and integrate the backend directly with a thin adapter we control.”