Skip to main content
50% off Capell extensions Claim
Capell home
Live demo

Manage cookie preferences

Choose which optional cookies Capell may use.

Essential
Always on

Required for Capell to work — login, security, page rendering.

Analytics

Anonymous usage telemetry to improve editor performance.

Marketing

Personalization for the Capell marketing site.

Cookie policy
Publishing Studio marketplace hero artwork.
Released Included with Capell Membership

Publishing Studio

Publishing Studio turns Capell publishing into a review-first workflow: draft, compare, approve, schedule, publish, restore, and roll back.

Buyer outcome

What Publishing Studio helps you do

Licence Unavailable
Unavailable

This private package is outside the Released and Beta channels, so no public install path is available.

12 captures

Publishing Studio turns Capell publishing into a review-first workflow: draft, compare, approve, schedule, publish, restore, and roll back.

Editors work in an isolated draft so visitors never see unfinished changes.

Teams get release confidence from readiness checks, review assignments, and atomic publish steps.

Use it when Capell content needs professional review and recovery, not only a publish button.

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 Publishing Studio adds when enabled.

  • Workflow
  • Editorial Timeline
  • Live Preview
  • Preview Link Management
  • Content Compare
  • Revisions
  • Content History
  • Approvals
  • Review Assignments
  • Field Comments
  • Publish Readiness
  • Dry Run Validation
  • Release Window Guards
  • Url Collision Checks
  • Scheduled Publishing
  • Embargo Windows
  • Review Reminders
  • Version History
  • Rollback Restore
  • Entity Restore
  • Activity History
  • Stale Draft Management
  • Recovery Imports
  • Workspace Pruning
  • Load Testing
  • Audit Trail
Installation impact

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.

Support
priority
Data access
Reads and writes Capell content structures required by the package; public output receives rendered content only.
  1. 01

    Require the package

    composer require capell-app/publishing-studio
  2. 02

    Register the extension

    php artisan capell:extension:enable publishing-studio
  3. 03

    Clear schema cache

    php artisan capell:admin:clear-schemas-cache

Evaluator scenarios

What to inspect in Publishing Studio

Switch the evaluation lens to see how different roles should assess this package before installing it.

Site owner representing this editorial scenario.

A mistake on the live site is reversible — what to verify

Publish a multi-record release, delete one item and then exercise both full-release and single-item recovery. Each restore should produce an exact prior state without erasing unrelated later work.

Read more

Verify in the product: Each publish is captured as a numbered version site owners can restore in seconds, with guards that stop two rollbacks colliding, and the delivery team drafts in a workspace before anything goes live. The evaluator should confirm that a mistake remains one revert away before widening publish access.

Trade-off to assess: For a solo editor on a small site it is more process than the job needs. The value arrives the moment more than one person can publish, and site owners still keep a developer for upkeep.

Site Owner

Evaluator scenario for a site owner

Scenario audience
History

Release and download evidence

Total downloads
0
Last downloaded
No downloads yet

Version history

0 releases

No 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.

Review from an eligible customer

Share what happened while installing or using this extension. Sign in with an account that has bought, downloaded, or installed it before submitting.

Sign in first. Review eligibility is checked against marketplace purchase, download, or install access.

No approved reviews yet. Reviews from eligible customers appear here after moderation.

Editor managing draft changes in an isolated workspace