Content Sections
Publish repeated page content from one shared section.
- Version
- 1.0.52
- Released
- 20 October 2026
- Requires
- Block Library, Layout Builder
- Licence
- Free
Price Free
Check access and installationCheck your application before checkout
Use it in your project
Use a section for copy that should stay consistent wherever it appears. Edit and publish it centrally, then reuse it on the pages that need it.
Picture it on your site
If the same approved introduction appears across several pages, identify the shared text and keep page-specific material outside it. Review a central edit on each place that reuses the section before publishing. This is a good fit for genuinely shared information, rather than several pages that merely happen to start with similar wording.
6 captures
Reuse content across your pages
- Create reusable sections from registered blueprints.
- Publish shared sections for supported pages and layouts.
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.
Paid checkout adds access to the purchasing account after payment. Add a free package to your account, then review compatibility and site impact before installing it.
Explore the available extensions on the demo site.
Before you install
Run the commands below in your Capell application. Required dependencies are listed above. After installing a theme, select it for your site in Admin.
-
01
Require the package
composer require capell-app/content-sections -
02
Install the extension
php artisan capell:extension-install capell-app/content-sections
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.0.52 Oct 20, 2026
- Recent activity
- 18 approved releases in the last 12 months
Access follows the account that owns the extension. Review the release trail and verification evidence here before installing.
Release notes and maintenance evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
10 releasesv1.0.52Oct 20, 2026v1.0.51Oct 17, 2026v1.0.48Oct 9, 2026v1.0.47Oct 8, 2026v1.0.46Oct 8, 2026v1.0.45Oct 7, 2026v1.0.44Oct 4, 2026v1.0.43Oct 1, 2026v1.0.42Sep 29, 2026v1.0.41Sep 23, 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?
Use the order link on the Lemon Squeezy receipt and request the refund through the Lemon Squeezy order receipt. If the receipt or order link is unavailable, contact Capell support so the payment and access record can be traced.
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.