Blog
Blog adds Capell article publishing with archives, tag pages, related-article widgets, and multilingual multi-site output.
What Blog helps you do
This private package is outside the Released and Beta channels, so no public install path is available.
Workflow screenshots
10 capturesBlog adds Capell article publishing with archives, tag pages, related-article widgets, and multilingual multi-site output.
Publishers get a first-party content type for news, resources, updates, and editorial marketing.
Editors stay inside Capell instead of running a separate blog system or hand-built article pages.
Use it when a Capell site needs regular publishing without leaving the platform.
Review the documentation and screenshots on this page before enabling it on a production Capell site.
What changes on your site
Review the admin, public, data, scheduled, and command surfaces Blog adds when enabled.
- Blog
- Rss
- Content Type
Install after you have checked the fit.
Confirm version compatibility, support, data access, migrations, retained data, and removal steps first. Then install the Composer package from the account that owns access.
-
01
Require the package
composer require capell-app/blog -
02
Register the extension
php artisan capell:extension:enable blog -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Evaluator scenarios
What to inspect in Blog
Switch the evaluation lens to see how different roles should assess this package before installing it.
The tenth post costs what the first did — what to verify
Publish a first and tenth article through the same fields, archive and URL rules. The later post should require no bespoke page build or extra layout work.
Read more Show less
The demonstration should show: Readers get consistent navigation and a known layout instead of a bespoke page each time, and site owners do not need to pay a developer to lay out post number ten. The channel scales without the effort scaling with it.
Scope check: For two static news pages it is more than the job needs. A dedicated content platform fits better when editorial publishing is the entire business.
Release and download evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
0 releasesNo package release history is published yet. Check the source and documentation before installing.
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 hosts paid marketplace checkout and 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 licence, receipt, support history, and future install access. 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.
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.
No approved reviews yet. Reviews from eligible customers appear here after moderation.
