Publishing Studio

Publishing Studio

Publishing Studio is Capell's flagship editorial timeline workflow. It gives content teams a premium, Statamic-style publishing experience for Capell: preview, compare, approve, editorial calendar, schedule, publish, and rollback every meaningful content change without editing live records directly.

At A Glance

• Package: capell-app/publishing-studio
• Namespace: Capell\PublishingStudio\
• Surfaces: Filament admin, Livewire, console, HTTP, database
• Service providers: packages/publishing-studio/src/Providers/AdminServiceProvider.php, packages/publishing-studio/src/Providers/ConsoleServiceProvider.php, packages/publishing-studio/src/Providers/PublishingStudioServiceProvider.php
• Capell dependencies: capell-app/admin, capell-app/core, capell-app/html-cache, capell-app/migration-assistant, capell-app/navigation
• Third-party dependencies: jfcherng/php-diff

Why It Helps Your Capell Workflow

• Adds preview, compare, approval, editorial calendar, scheduling, publishing, restore, rollback, and release workspace workflows for Capell content.
• Helps owners manage editorial risk by making review state, publish readiness, and rollback paths visible in admin.
• Gives developers draftable contracts, workspace registries, release contributors, and focused Actions for publishing behavior.

Best Used With

• SEO Suite
• Document Lifecycle
• Notes

What It Adds

Publishing Studio is Capell's flagship editorial timeline workflow. It gives content teams a premium, Statamic-style publishing experience for Capell: preview, compare, approve, schedule, publish, and rollback every meaningful content change without editing live records directly.

• Draft publishing-studio with copy-on-write editing for Draftable content.
• Signed live preview links, expiry/revocation management, access tracking, and a frontend workspace preview banner.
• Compare and readiness views with diff, dry-run validation, field comments, review assignments, URL-collision checks, stale workspace warnings, and publish checks.
• Release Workspaces for grouping coordinated content, navigation, SEO, media, layout, and package-owned draftable changes into one previewable, approvable, schedulable, atomic publish.
• Approval history for submit, approve, reject, and request-changes decisions, including reviewer notes and required approval levels.
• Scheduled publishing with release-window guards, unpublish dates, embargo windows, review reminders, immediate publishing, version history, rollback, and entity-level restore.
• Editorial calendar aggregation for page/workspace scheduler events plus tagged package contributors from Blog, Campaign Studio, Newsletter, and Events.
• Activity timeline widgets, stale draft management, import recovery screens, load-test fixtures, and prune commands for audit-friendly editorial operations.

Why It Matters

For developers: Adds copy-on-write, draftable model support, workspace events, review policies, preview signing, and page resource extenders without moving domain logic into Filament pages.

For teams: Gives editors the confidence of a content history product: they can see what changed, preview it safely, gather approval, schedule the release, publish when ready, and restore a previous version if production needs to move back.

Built With

This package makes its Composer dependencies visible because they are part of the value proposition, not just plumbing. When an upstream package has a public repository, its linked preview card points readers back to the maintainers so their work gets proper credit.

Capell packages used here

• Capell Admin
• Capell Migration Assistant
• Capell Core
• Capell Navigation

Open-source packages used here

• php-diff - diff generation that powers editorial comparisons and publishing review workflows.

Linked package previews

Screens And Workflow

Screenshots are generated from docs/screenshots.json during package deployment. The step-by-step workflow screenshots with overlay text live in docs/publishing-workflow.md.

• Editorial timeline dashboard.
• Live preview, preview link management, and preview banner.
• Compare, dry-run validation, and publish readiness panel.
• Approval history, reviewer assignments, and field comments.
• Scheduled publishing queue with embargo, unpublish, and review-reminder metadata.
• Stale drafts, recovery imports, activity history, and audit trail.
• Rollback, entity restore, and version history flow.

Technical Shape

• PublishingStudioServiceProvider, AdminServiceProvider, ConsoleServiceProvider register package surfaces.
• Routes include capell/preview/exit and scheduler iCal feeds.
• Migrations create publishing-studio, versions, preview links, approvals, field comments, review assignments, and workspace columns on core/external tables.
• Events track state changes and version rollback.
• Publish checks include accessibility, broken links, missing alt text, SEO meta, stale workspace state, URL collisions, and release-window rules.

Code Map

Admin Surface

• Resources: PreviewLinkResource, WorkspaceResource.
• Pages: ActivityTrailPage, ActivityTrailTable, CompareVersionPage, DiscardDraftsBulkAction, ManagePreviewLinks, ManagePublishingStudio, PageVersionHistoryPage, PublishPageAction, PublishingWorkflowPage, RequestReviewBulkAction, ResubmitForReviewAction, SaveAsDraftFormAction, ScheduledPublishingPage, and related pages.
• Widgets: ContentSchedulerCalendarWidget, ContentSchedulerOverviewWidget, PageAlertsWidget, WorkspaceActivityWidgetAbstract, WorkspaceMergeHistoryWidgetAbstract.
• Settings: PublishingStudioSettings.

Runtime Surface

• Livewire: DiffPanel, FieldCommentThread, PageApprovalStatus, PublishStatusPanel, ReleaseWorkspaceSummaryPanel, WorkspaceApprovalHistory, WorkspaceContextBanner, WorkspaceSwitcher.
• Controllers: ExitWorkspacePreviewController, SchedulerIcalFeedController.
• Routes: packages/publishing-studio/routes/web.php.

Commands

• capell:publishing-studio-install (packages/publishing-studio/src/Console/Commands/InstallCommand.php)
• capell:publishing-studio:load-test {--publishing-studio=10 : Number of publishing-studio to create} {--rows-per-workspace=100 : Fixture rows per workspace} {--fresh : Truncate the fixture workspace tables first} {--publish= : Publish the first N publishing-studio after populating (defaults to 0)} {--force : Allow running outside local/testing environments} (packages/publishing-studio/src/Console/Commands/LoadTestPublishingStudioCommand.php)
• capell:publishing-studio:prune {--id=* : Prune a specific workspace id instead of every abandoned workspace} {--dry-run : Report what would be pruned without making changes} (packages/publishing-studio/src/Console/Commands/PruneAbandonedPublishingStudioCommand.php)

Data And Persistence

• publishing-studio stores uuid, slug, status, base version, cloned-from workspace, submitted/approved/publish timestamps, and timeline status metadata.

• versions stores uuid, number, live flag, manifest, source workspace, and rollback links.

• preview_links, workspace_approvals, workspace_review_assignments, and workspace_field_comments support preview, compare, approval, comments, assignments, and activity history.

• Core tables receive workspace_id columns.

• Models: PreviewLink, Version, Workspace, WorkspaceApproval, WorkspaceFieldComment, WorkspaceReviewAssignment.

• Migrations: 2026_05_10_190866_01_create_preview_links_table.php, 2026_05_10_190866_02_create_publishing-studio_table.php, 2026_05_10_190866_03_create_versions_table.php, 2026_05_10_190866_04_create_workspace_approvals_table.php, 2026_05_10_190866_05_create_workspace_field_comments_table.php, 2026_05_10_190866_06_create_workspace_review_assignments_table.php, 2026_05_10_190866_07_seed_bootstrap_workspace_version.php, 2026_05_10_190866_08_z_add_workspace_columns_to_core_tables.php, 2026_05_10_190866_09_z_add_workspace_id_to_external_tables.php, 2026_05_10_190866_10_z_add_workspace_id_to_import_sessions_table.php.

• Data objects live in src/Data/; use them for payloads, form state, and view models.

Extension Points

• Contracts: ReleaseWorkspaceItemContributor, WorkspaceTableActionContributor.
• Events: VersionRolledBack, WorkspaceEventDispatcher, WorkspaceEventSubscriber, WorkspaceStateChanged.
• Listeners: SendWorkspaceStateNotification, StampWorkspaceOnActivity.
• Register Capell extension points, routes, migrations, settings, render hooks, and resources from service providers.

Install Impact

• Adds workspace and versioning tables.
• Adds workspace_id columns to core and external tables.
• Adds admin resources/pages/widgets and frontend preview route.
• Adds middleware to resolve workspace context.
• Adds commands for install, load testing, and pruning abandoned publishing-studio.
• Adds Migration Assistant adapters so page imports can stage content into Publishing Studio workspaces.

Install And Setup

• Install with composer require capell-app/publishing-studio in the host Capell application.
• Run migrations through the host application package install flow.
• In this repository, verify package changes with vendor/bin/pest; do not use php artisan.

Admin And Access

• ActivityTrailPage (packages/publishing-studio/src/Filament/Pages/ActivityTrailPage.php, slug reports/activity-trail)

• ScheduledPublishingPage (packages/publishing-studio/src/Filament/Pages/ScheduledPublishingPage.php, slug scheduled-publishing)

• StaleDraftsPage (packages/publishing-studio/src/Filament/Pages/StaleDraftsPage.php, slug stale-drafts)

• PageVersionHistoryPage (packages/publishing-studio/src/Filament/Resources/Pages/Pages/PageVersionHistoryPage.php, slug {record}/history)

• ManagePreviewLinks (packages/publishing-studio/src/Filament/Resources/PreviewLinks/Pages/ManagePreviewLinks.php)

• PreviewLinkResource (packages/publishing-studio/src/Filament/Resources/PreviewLinks/PreviewLinkResource.php)

• CompareVersionPage (packages/publishing-studio/src/Filament/Resources/PublishingStudio/Pages/CompareVersionPage.php, slug {record}/compare)

• ManagePublishingStudio (packages/publishing-studio/src/Filament/Resources/PublishingStudio/Pages/ManagePublishingStudio.php)

• WorkspaceResource (packages/publishing-studio/src/Filament/Resources/PublishingStudio/WorkspaceResource.php)

• Policy: WorkspacePolicy (packages/publishing-studio/src/Policies/WorkspacePolicy.php)

• Gate: ContentSchedulerOverviewWidget: admin, super_admin

• Gate: ScheduledPublishingPage: Filament Shield page permissions

• Gate: StaleDraftsPage: Filament Shield page permissions

• Gate: WorkspaceActivityWidgetAbstract: admin, super_admin

• Gate: WorkspaceMergeHistoryWidgetAbstract: super_admin

Common Pitfalls

• Models participating in draft/publish must implement Draftable and be registered.
• Run migrations in order before using copy-on-write.
• Publish checks, stale workspace analysis, URL collisions, and release windows can block publishing.
• Preview links need expiry, revocation, and access-count review.
• Schedule release windows, unpublish dates, embargo rules, and review reminders must match site operations.
• Recovery Center page import screens are owned by Migration Assistant; Publishing Studio contributes workspace target, context, and collision adapters when both packages are installed.

Docs

• docs index
• credits-and-acknowledgements.md
• extending-publishing-studio.md
• overview.md
• page-creation-and-approval-flow.md
• page-drafts-and-publishing.md
• publishing-studio-draftable-contract.md
• publishing-studio.md
• publishing-workflow.md
• release-workspaces.md

Testing

Run package tests from the repository root:

vendor/bin/pest packages/publishing-studio/tests --configuration=phpunit.xml

Maintenance Notes

• Put behaviour changes in src/Actions/; UI classes, commands, and controllers should call actions instead of owning domain logic.
• Use package Data classes at boundaries instead of passing anonymous arrays between layers.
• Use backed enums for persisted values and enum labels for Filament options.

PublishingStudio

Status: Available, schema-owning · Kind: package · Tier: premium · Bundle: publishing-pro · Contexts: admin, console · Product group: Capell Publishing Pro

This page is the consolidated implementation overview for the PublishingStudio package. It is extracted from the package README, service providers, migrations, config files, routes, resources, models, actions, and the shared Capell ERD notes where available.

What This Package Adds

Publishing Studio is Capell's premium editorial timeline package. It brings the publishing loop into one workflow: preview, compare, approve, editorial calendar, schedule, publish, and rollback content changes while preserving a readable history of what happened and why.

• Draft publishing-studio for safe copy-on-write editing.
• Signed live preview links with expiry, revocation, access counts, and a frontend preview banner.
• Compare, diff, dry-run validation, field comments, review assignments, publish readiness checks, URL-collision checks, and stale workspace warnings.
• Release Workspaces for grouped editorial releases that move coordinated content and package-owned draftable changes live atomically.
• Approval history for submit, approve, reject, and request-changes decisions.
• Scheduled publishing with release windows, unpublish dates, embargo windows, review reminders, immediate publishing, version history, rollback, and entity restore.
• Editorial calendar aggregation across core page schedules, Publishing Studio workspace schedules, Blog articles, Campaign Studio campaign dates, Newsletter sends, and Events occurrences through EditorialCalendarEventContributor.
• Activity timeline, stale drafts, Migration Assistant import adapters, load-test fixtures, and prune commands for editorial and operational audit trails.

Developer Notes

Adds copy-on-write, draftable model support, workspace events, review policies, preview signing, and page resource extenders without moving domain logic into Filament pages.

• PublishingStudioServiceProvider, AdminServiceProvider, ConsoleServiceProvider register package surfaces.
• Routes include capell/preview/exit.
• Migrations create publishing-studio, versions, preview links, approvals, field comments, review assignments, and workspace columns on core/external tables.
• Events track state changes and version rollback.
• Publish checks include accessibility, broken links, missing alt text, SEO meta, stale workspace state, URL collisions, and release-window rules.

Operational Notes

Gives editorial teams a Statamic-style content history feel while remaining a separate premium Capell package. Editors can move from draft to preview, review, schedule, publish, and restore without losing the context behind each decision.

• Adds workspace and versioning tables.
• Adds workspace_id columns to core and external tables.
• Adds admin resources/pages/widgets and frontend preview route.
• Adds middleware to resolve workspace context.
• Adds commands for install, load testing, and pruning abandoned publishing-studio.
• Adds Migration Assistant adapters so page imports can stage content into workspaces when import workflows are enabled.

Data And Retention

• publishing-studio stores uuid, slug, status, base version, cloned-from workspace, submitted/approved/publish timestamps, and kind/status metadata.
• versions stores uuid, number, live flag, manifest, source workspace, and rollback link.
• preview_links, workspace_approvals, workspace_review_assignments, and workspace_field_comments support preview, compare, comments, reviewer assignment, approval, and activity history.
• Core tables receive workspace_id columns.

Screenshot Plan

• Editorial timeline dashboard.
• Live preview, preview link management, and preview banner.
• Compare, dry-run validation, and publish readiness panel.
• Approval history, reviewer assignments, and field comments.
• Scheduled publishing queue with embargo, unpublish, and review-reminder metadata.
• Stale drafts, recovery imports, activity history, and audit trail.
• Rollback, entity restore, and version history flow.

Screenshots

The live preview, preview banner, recovery import, and activity history screenshots need seeded workspace/import data before they should be published.

Pitfalls

• Models participating in draft/publish must implement Draftable and be registered.
• Run migrations in order before using copy-on-write.
• Publish checks, stale workspace analysis, URL collisions, and release windows can block publishing.
• Preview links need expiry, revocation, and access-count review.
• Schedule release windows, unpublish dates, embargo rules, and review reminders must match site operations.
• Recovery Center page import screens are owned by Migration Assistant; Publishing Studio contributes workspace target, context, and collision adapters.

Verification

• Run vendor/bin/pest packages/publishing-studio/tests when package tests exist.
• Run the relevant host-app migration or package install flow in a disposable database.
• Open the listed admin or frontend surface and compare it with the screenshot plan.

Related Docs

• Release Workspaces

Package Manifest

• Composer name: capell-app/publishing-studio
• Product group: Capell Publishing Pro
• Kind: package
• Tier: premium
• Bundle: publishing-pro
• Contexts: admin, console
• Package catalog headline: Editorial timeline workflow for preview, compare, approval, scheduling, publishing, and rollback.
• Requires: capell-app/core, capell-app/admin
• Optional dependencies: None listed.

Admin Surfaces

• ActivityTrailPage (packages/publishing-studio/src/Filament/Pages/ActivityTrailPage.php, slug reports/activity-trail)
• ScheduledPublishingPage (packages/publishing-studio/src/Filament/Pages/ScheduledPublishingPage.php, slug scheduled-publishing)
• StaleDraftsPage (packages/publishing-studio/src/Filament/Pages/StaleDraftsPage.php, slug stale-drafts)
• PageVersionHistoryPage (packages/publishing-studio/src/Filament/Resources/Pages/Pages/PageVersionHistoryPage.php, slug {record}/history)
• ManagePreviewLinks (packages/publishing-studio/src/Filament/Resources/PreviewLinks/Pages/ManagePreviewLinks.php)
• PreviewLinkResource (packages/publishing-studio/src/Filament/Resources/PreviewLinks/PreviewLinkResource.php)
• CompareVersionPage (packages/publishing-studio/src/Filament/Resources/PublishingStudio/Pages/CompareVersionPage.php, slug {record}/compare)
• ManagePublishingStudio (packages/publishing-studio/src/Filament/Resources/PublishingStudio/Pages/ManagePublishingStudio.php)
• WorkspaceResource (packages/publishing-studio/src/Filament/Resources/PublishingStudio/WorkspaceResource.php)

Commands

• capell:publishing-studio-install (packages/publishing-studio/src/Console/Commands/InstallCommand.php)
• capell:publishing-studio:load-test {--publishing-studio=10 : Number of publishing-studio to create} {--rows-per-workspace=100 : Fixture rows per workspace} {--fresh : Truncate the fixture workspace tables first} {--publish= : Publish the first N publishing-studio after populating (defaults to 0)} {--force : Allow running outside local/testing environments} (packages/publishing-studio/src/Console/Commands/LoadTestPublishingStudioCommand.php)
• capell:publishing-studio:prune {--id=* : Prune a specific workspace id instead of every abandoned workspace} {--dry-run : Report what would be pruned without making changes} (packages/publishing-studio/src/Console/Commands/PruneAbandonedPublishingStudioCommand.php)

Routes And Config

• Route file: packages/publishing-studio/routes/web.php

Permissions And Gates

• Policy: WorkspacePolicy (packages/publishing-studio/src/Policies/WorkspacePolicy.php)
• Gate: ContentSchedulerOverviewWidget: admin, super_admin
• Gate: ScheduledPublishingPage: Filament Shield page permissions
• Gate: StaleDraftsPage: Filament Shield page permissions
• Gate: WorkspaceActivityWidgetAbstract: admin, super_admin
• Gate: WorkspaceMergeHistoryWidgetAbstract: super_admin

Migrations

• Migration: 2026_04_20_000001_2026_05_10_190866_02_create_publishing-studio_table.php
• Migration: 2026_04_20_000002_2026_05_10_190866_03_create_versions_table.php
• Migration: 2026_05_10_190866_01_create_preview_links_table.php
• Migration: 2026_05_10_190866_04_create_workspace_approvals_table.php
• Migration: 2026_05_10_190866_05_create_workspace_field_comments_table.php
• Migration: 2026_05_10_190866_06_create_workspace_review_assignments_table.php
• Migration: 2026_05_10_190866_07_seed_bootstrap_workspace_version.php
• Migration: 2026_05_10_190866_08_z_add_workspace_columns_to_core_tables.php
• Migration: 2026_05_10_190866_09_z_add_workspace_id_to_external_tables.php
• Migration: 2026_05_10_190866_10_z_add_workspace_id_to_import_sessions_table.php

ERD Excerpt

erDiagram
    WORKSPACES ||--o{ VERSIONS : publishes
    WORKSPACES ||--o{ WORKSPACE_APPROVALS : approval_history
    WORKSPACES ||--o{ WORKSPACE_REVIEW_ASSIGNMENTS : assigned_reviewers
    WORKSPACES ||--o{ WORKSPACE_FIELD_COMMENTS : inline_comments
    WORKSPACES ||--o{ PREVIEW_LINKS : preview_urls
    VERSIONS ||--o{ VERSIONS : rollback_chain
    USERS ||--o{ WORKSPACES : userstamps

    WORKSPACES ||--o{ PAGES : workspace_id
    WORKSPACES ||--o{ LAYOUTS : workspace_id
    WORKSPACES ||--o{ SITES : workspace_id
    WORKSPACES ||--o{ TRANSLATIONS : workspace_id
    WORKSPACES ||--o{ PAGE_URLS : workspace_id
    WORKSPACES ||--o{ NAVIGATIONS : workspace_id

    WORKSPACES {
        bigint id PK
        uuid uuid
        string slug
        string status
        bigint base_version_id
        bigint cloned_from_id
        timestamp submitted_at
        timestamp approved_at
        timestamp publish_at
    }

    VERSIONS {
        bigint id PK
        uuid uuid
        bigint number
        boolean is_live
        json manifest
        bigint source_workspace_id FK
        bigint rollback_of_version_id FK
    }

Screenshot Automation

Deployment should read screenshots.json, install the package with demo data, resolve each admin surface or frontend URL, and write images to packages/publishing-studio/docs/screenshots.

• Editorial timeline dashboard.
• Live preview, preview link management, and preview banner.
• Compare, dry-run validation, and publish readiness panel.
• Approval history, reviewer assignments, and field comments.
• Scheduled publishing queue with embargo, unpublish, and review-reminder metadata.
• Stale drafts, recovery imports, activity history, and audit trail.
• Rollback, entity restore, and version history flow.