Hero
Give a page a clear opening with reusable hero content.
- Version
- 1.1.0-beta.55
- Released
- 10 November 2026
- Requires
- Layout Builder, Theme Foundation
- Licence
- Free
Price Free
Check access and installationCheck compatibility before using this Beta extension
Beta does not mean production-ready. Review compatibility, support, site impact, and likely upgrade work before enabling it.
Check your application before checkout
What it solves
The problem
Editors need a developer to build a prominent page introduction with imagery and actions.
What your site gets
A page has a theme-rendered introduction that editors can configure.
Questions buyers ask
- Can a hero contain multiple slides?
- Yes. Editors can configure multiple slides in Layout Builder.
- Which media can the hero show?
- The widget supports responsive images or video.
- Where does the background come from?
- Editors can use theme or widget background fields, including inherited theme options.
Use it in your project
Choose the headline, actions and media for the page's opening section. Shared theme defaults keep the treatment consistent while individual pages supply their own message.
Picture it on your site
For a service page, choose an opening image that shows the actual work and a headline that names the offer. Check the action and crop on a phone as well as a desktop. Shared defaults keep the opening treatment coherent, while the editor remains responsible for a useful message and appropriate media on each page.
1 capture
Reuse content across your pages
- Compose hero copy, actions and responsive media.
- Use multiple slides and inherited background settings.
Is this right for your project?
Reuse without losing control
Reusable content earns its place when several pages need the same structure or information, but different people should not be inventing their own versions. Decide what editors can vary and what the application should keep consistent. That makes a shared block useful rather than restrictive, and lets a correction travel to the places that intentionally reference it.
Make the real page the test
Place the component inside an actual page layout and try both a short and a long piece of content. Check narrow screens, translated text and missing optional fields. The package supplies its registered editing or rendering capabilities; your theme, templates and allowed content choices determine how those capabilities fit the finished website.
Marketplace listings can describe install impact and data access.
This installs as a Composer package. Check its removal guidance and retained-data policy before uninstalling it.
Add this free package to your account, then review compatibility and site impact before installing it.
This listing has no page of its own in the demo. Open the demo to see Capell running.
Before you install
Review the impact below before running the commands in a covered Capell application, starting with a non-production environment. Required dependencies are listed above.
- Admin and public surfaces
- The package declares: administration screens, frontend integration, command-line operations. Review the release documentation for configuration and exposure in your application.
- Data and migrations
- The manifest declares no package migrations. This does not establish that installation or runtime operations make no data changes. Uses package-local configuration and Capell metadata needed to enable the feature.
- Background work
- A complete jobs and scheduler assessment is not available here. Confirm background processing and worker requirements with the publisher.
- Access controls
- Access-control changes are not described here. Confirm the required roles and grants with the publisher.
- Removal and retained data
- A verified uninstall and retained-data assessment is not available here. Removing the Composer package does not establish that its data is deleted. Confirm cleanup, retention and dependencies with the publisher before removal.
-
01
Require the package
composer require capell-app/hero:^1.1.0@beta -
02
Install the extension
php artisan capell:extension-install capell-app/hero
Release and review evidence
Release activity stays visible
These dates come from approved package releases, so you can see the release trail before installing.
- Latest approved release
- v1.1.0-beta.55 Nov 10, 2026
- Recent activity
- 13 approved releases in the last 12 months
Review evidence for this release
Hero banner package reviewed with no defects found; it contributes presentation-only schema and Blade components and exposes no public routes or stored visitor data.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.1.0-beta.55
- Approval date
- Nov 8, 2026
Areas reviewed
- Strict, maintainable PHP
- Presentation-only public views
- Actions and typed boundaries
- Clean anonymous public output
- Authorisation and input safety
- Declared package boundaries
- Manifest and migration integrity
- Compatibility and interoperability
- Meaningful behavioural tests
- Security and supply-chain checks
- Performance and operational behaviour
- Theme delivery quality where applicable
- Marketplace claims matched to behaviour
- AI-assisted analysis with human accountability
Accepted limitations
- No automated browser coverage for the rendered hero across every theme and breakpoint; visual checks are manual.
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Release notes and maintenance evidence
Version history
Showing the 10 most recent of 13 approved releases-
v1.1.0-beta.55Nov 10, 2026 -
v1.1.0-beta.54Nov 2, 2026 -
v1.1.0-beta.53Oct 28, 2026 -
v1.1.0-beta.52Oct 20, 2026 -
v1.1.0-beta.51Oct 17, 2026 -
v1.1.0-beta.47Oct 9, 2026 -
v1.1.0-beta.46Oct 8, 2026 -
v1.1.0-beta.45Oct 8, 2026 -
v1.1.0-beta.44Oct 7, 2026 -
v1.1.0-beta.43Oct 4, 2026
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy is the seller and hosts paid marketplace checkout. Any VAT due is calculated and added by Lemon Squeezy at checkout, and Lemon Squeezy issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the Capell licence, support history, and future install access. Capell surfaces a link to the tax receipt issued by Lemon Squeezy. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
How do I request a refund?
There is no self-service refund button. Email [email protected] within 14 days of purchase with the account email, the order or receipt reference, the package and your reason. Capell reviews the recorded purchase and, where approved, submits the refund through Lemon Squeezy. Read the Refund Policy
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.