Content Reveal Widget
Keep supporting content close without showing it all at once.
- Version
- 1.1.0-beta.54
- Released
- 10 November 2026
- Requires
- Layout Builder
- 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 who want to offer more detail can send visitors away from the page to find it.
What your site gets
A page has teasers that reveal registered widget content in place.
Questions buyers ask
- Where can revealed content appear?
- Editors can choose modal, slide-over, inline or replacement presentation.
- Which content can a teaser open?
- A teaser connects to another registered widget; targets stay within the widget registry.
- How many reveal cards are allowed?
- A reveal must contain between 1 and 12 cards.
Use it in your project
Connect a teaser to a registered widget, then choose how its content should open. Visitors can explore the detail without leaving the page.
Picture it on your site
For a page with optional detail, decide which teaser deserves more information and connect it to the supported widget on that same page. Try opening and closing the result on mobile. Progressive detail can keep a page readable, but important information should not disappear behind an unexplained control or an unrelated teaser.
3 captures
In the admin
On your site
Add a focused interaction to a page
- Reveal supporting widgets from teaser cards.
- Choose modal, slideover, inline or replacement presentation.
Is this right for your project?
Give the widget a job
Choose the point in a page where the interaction helps a visitor complete something: understand a deadline, find a record or move to the next step. Set the widget up with real content and place it in the intended Layout Builder container. Its supported behaviour is the starting point; the page around it determines whether the interaction is useful and understandable.
Check the surrounding page
Test the widget at narrow and wide widths, with the longest expected label and with optional data absent. Check keyboard access and the result of the interaction, not only its initial appearance. Your application still owns the layout, theme and any destination or service the widget connects to. A demonstration of one state should not be mistaken for evidence of the whole workflow.
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.
Works with Content Reveal Widget
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. 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/widget-content-reveal:^1.1.0@beta -
02
Install the extension
php artisan capell:extension-install capell-app/widget-content-reveal
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.54 Nov 10, 2026
- Recent activity
- 13 approved releases in the last 12 months
Review evidence for this release
Progressive content reveal widget that opens further page content in a panel or in place, reviewed with no internal identifiers reaching the published page.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.1.0-beta.54
- 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
- Reveal targets depend on the layout builder's public fragment addressing; a card renders as plain text when its target is unavailable.
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.54Nov 10, 2026 -
v1.1.0-beta.53Nov 2, 2026 -
v1.1.0-beta.52Oct 28, 2026 -
v1.1.0-beta.51Oct 20, 2026 -
v1.1.0-beta.50Oct 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.