Weave Code
Socials Laravel Package
capell-app/socials
Social media integration for Laravel and Capell applications. Manage social profiles, links, and sharing settings from a single package, with configurable networks and a simple API for adding social features to your site. Lightweight and easy to configure.
Capell Socials profiles, sharing preferences, and Block Library widgets
Frequently asked questions about Socials
- How do I install and use capell-app/socials in a Laravel app?
- Require the package with Composer, pinning the exact beta version you have reviewed, and let Laravel package discovery register its service provider. Publish the config and Blade views if you need to customize networks or markup. The package provides Blade components for social icon links and share buttons, plus a service-layer API for custom integrations. Test the integration in a sandbox Laravel app before deploying to production.
- What Laravel and PHP versions does capell-app/socials support?
- The release information referenced here does not publish explicit Laravel or PHP constraints, so check the package composer.json require block and the README for the supported range. Because the current line is a pre-1.0 beta at v1.0.0-beta.51, confirm compatibility with your project Laravel major version before scheduling integration work. Pin the exact beta version in Composer instead of using a floating constraint.
- Can I use capell-app/socials outside Capell CMS?
- The package overview says it is built for the Capell CMS and standard Laravel apps, so it should be usable in a normal Laravel application that already uses Composer, service providers, and Blade. You still need to verify whether its settings-driven approach depends on Capell-specific services or contracts. For non-Laravel services, it is not a framework-agnostic component and should not be introduced without a clear boundary.
- Does capell-app/socials handle OAuth or social login?
- Based on the package overview, it focuses on social profiles, links, and share buttons rather than OAuth authentication or token storage. If your use case requires social login, review the source and public API before adopting because auth flows carry materially higher risk. Keep this package at the presentation and configuration edge, and use a dedicated authentication solution for OAuth.
- How do I configure which social networks appear?
- Publish the package config and enable or disable each network there, since the package ships with a configurable set of networks and per-network settings. Editors can manage social profiles through the settings-driven approach without touching code when your Capell or Laravel settings layer is wired up. Publish the views as well if you need to change icons, ordering, or markup.
- Can I customize the Blade components and share button markup?
- Yes, the package provides ready-made Blade components for icon links and share buttons, and its publishable views let you override the markup. Publish the views in a non-production environment first, then adjust styling and verify the rendered output. Keep customizations in your application view overrides so future package upgrades are easier to review. The package is designed to keep output cache-friendly and easy to theme.
- Is capell-app/socials safe for production use?
- It is currently a pre-1.0 beta at v1.0.0-beta.51, so treat it as unverified until you review the changelog or diff, open issues, and test coverage. For low-risk social-link and sharing presentation, it can be adopted conditionally with exact version pinning and a documented rollback plan. Avoid it for authentication, token storage, or sensitive user-data flows until its scope and security posture are validated.
- How should I test capell-app/socials before deploying?
- Install it in a sandbox Laravel app first, run the package tests if available and your application smoke tests, then publish config and views outside production to validate output. Add feature tests that assert the rendered social links and share URLs for your configured networks. Use a feature flag in staging before a canary deployment, and document rollback to the previous pinned version or custom implementation.
- What changed between v1.0.0-beta.45 and v1.0.0-beta.51?
- The release note referenced here contains only a compare link and no human-readable changelog, so you need to review the diff on GitHub for API, config, view, or database changes. Check open issues and any migration or deprecation notes before upgrading. Pin the exact version you have reviewed and batch upgrades only after diff review.
- What are alternatives to capell-app/socials for Laravel social sharing?
- Alternatives include building a small config-driven Blade partial for profile links and share URLs, or using a general Laravel social-share package if you need broader network coverage. This package differentiator is its Capell CMS settings integration and publishable Blade components. Evaluate alternatives if you need a stable 1.0 release or stronger release governance.
Weaver
How can I help you explore Laravel packages today?