Structured Content Library
Update a testimonial, person or service once and reuse it.
- Version
- 1.1.0-beta.47
- Released
- 20 October 2026
- 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
Use it in your project
Keep repeated entries in the library, then select them from supported sections and themes. Choose this when several pages need the same approved information.
Picture it on your site
For a team member or testimonial used on several pages, keep the approved facts in one reusable entry and select it through supported sections. Review a central change in its actual page contexts. Shared records prevent copies drifting, but page-specific framing still belongs to the editor composing the surrounding story.
6 captures
In the admin
On your site
Reuse content across your pages
- Manage reusable testimonials, FAQs, people and services.
- Share records with supported themes and Content Sections.
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/structured-content-library -
02
Install the extension
php artisan capell:extension-install capell-app/structured-content-library
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.47 Oct 20, 2026
- Recent activity
- 17 approved releases in the last 12 months
Review evidence for this release
Stores reusable structured content items (FAQs, definitions, and similar reference content) with site-scoped visibility, draft, published and archived status, and an import path for bulk loading. Review found the authorisation, public-payload sanitisation, and slug-uniqueness handling to be sound; no unresolved defects were identified.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.1.0-beta.47
- Approval date
- Oct 19, 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
- Public payload fields are limited to a fixed set of safe types (plain text, validated URLs, validated email addresses); other field shapes in a payload are silently dropped from public output rather than rendered. Cross-package integration was not exercised by this per-package review; the local suites used SQLite, and live browser flows and server-database behaviour were not exercised.
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 releases-
v1.1.0-beta.47Oct 20, 2026 -
v1.1.0-beta.46Oct 17, 2026 -
v1.1.0-beta.45Oct 9, 2026 -
v1.1.0-beta.44Oct 9, 2026 -
v1.1.0-beta.43Oct 8, 2026 -
v1.1.0-beta.42Oct 8, 2026 -
v1.1.0-beta.41Oct 7, 2026 -
v1.1.0-beta.40Oct 4, 2026 -
v1.1.0-beta.39Oct 1, 2026 -
v1.1.0-beta.38Sep 29, 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.