Publishing Studio
Review page changes before they reach the live site.
- Version
- 1.0.54
- Released
- 20 October 2026
- Requires
- Html Cache, Migration Assistant, Navigation
- Licence
- Commercial
Price £59.00
Check access and installationCheck your application before checkout
Use it in your project
Prepare Capell Pages in an isolated draft, ask a reviewer to approve them and publish when ready. The supported launch workflow covers Capell Pages; custom content types need their own integration.
Picture it on your site
For a campaign launch involving several editors, prepare the Capell Pages in draft and agree who reviews the final change. Compare the proposed page state before approving publication and plan how the team would recover a mistake. Keep custom content-type integration as a separate requirement rather than assuming the page workflow automatically covers every model.
12 captures
Keep publishing work moving
- Assign reviewers and retain approval and activity history.
- Schedule or publish page changes as an atomic release.
- Validate recovery when a published release needs reversing.
Is this right for your project?
A publishing process people can follow
Start with the journey from a draft to a published page, not a list of status names. Who writes it, who checks it and who is responsible for the publication date? Choose the controls that match that journey. The benefit is a repeatable editorial process with fewer changes made outside the CMS; your team still supplies the content standards and the people who make publishing decisions.
Prove one complete release
Use a representative article or page to check editing, review, publication and the public result together. Include the site, language and related content that matter to your project. A scheduled record or approved status is only part of the result: visitors must see the right content at the right URL, and editors need to know how to correct it afterwards.
You may ask Capell for a full refund within 14 days of purchase. Requests are assessed case by case against the recorded order, access and support history. This applies to live paid first-party packages; third-party author sales have separate terms. Read the Refund Policy
Your renewal price stays locked while you renew continuously, including during the grace period. After a full lapse, renewal uses the current list price.
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.
Works with Publishing Studio
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/publishing-studio -
02
Install the extension
php artisan capell:extension-install capell-app/publishing-studio
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.54 Oct 20, 2026
- Recent activity
- 20 approved releases in the last 12 months
Review evidence for this release
Publishing Studio provides draft workspaces, review and approval workflow, scheduled publishing, and revision history for Capell content. The review examined preview-link and scheduler iCal token handling, workspace access policies, and public-facing preview output, and found no unresolved security or correctness defects. The reviewed calendar update adds request throttling and a private five-minute cache scoped to the issued token, with current owner permissions checked before use.
Review reduces risk, but it is not a permanent security guarantee.
- Reviewed version
- 1.0.54
- 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
- The scheduled-publishing iCal feed re-checks the token owner's current permissions on each request but does not itself notify a site owner when a token's original issuer is deactivated; site admins should periodically review issued tokens. 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. The MySQL/MariaDB-specific timestamp-repair branch was reviewed in source but was not executed by this SQLite attestation run. The existing page-copy modal snapshot test was skipped by the package suite and remains unverified.
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
- 4
- Last downloaded
- Sep 17, 2026
Version history
10 releasesv1.0.54Oct 20, 2026v1.0.53Oct 17, 2026v1.0.50Oct 9, 2026v1.0.49Oct 8, 2026v1.0.48Oct 8, 2026v1.0.47Oct 7, 2026v1.0.46Oct 4, 2026v1.0.45Oct 1, 2026v1.0.44Oct 1, 2026v1.0.43Sep 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.