Skip to main content

Laravel Publishing Workflow

From page edit to published output.

A realistic publishing path should show the work, not just list the features.

Capell keeps the publishing path visible: edit the page, check the URL, preview the draft, ask for review, publish the approved version, refresh the public cache, and leave a rollback note where the next maintainer will find it.

Task-led screenshots

One page change, shown as tasks.

Each screenshot should make the next editor or maintainer task obvious.

Workflow checklist

The page edit checklist.

Use one small content change to judge whether the CMS makes daily work clearer, or simply gives the team more places to click.

Create Open or create the page. Check that the page type, title, URL, language, layout, media, and reusable sections are in named fields.
Change Edit one meaningful section. Update copy, swap a screenshot, or adjust a LayoutBuilder widget without changing the public template.
Preview Review the draft in context. Use preview links or the project preview path so reviewers see the real page rather than a form.
Approve Record the decision. When Workspaces is installed, capture assignment, comments, readiness checks, and approval state near the page.
Publish Promote the approved version. Publish the page, refresh affected URLs, and make the public cache reflect the approved content.
Recover Leave a rollback trail. Keep version history, import notes, and recovery steps visible for the next maintainer.
Related proof

Connect the workflow to the rest of Capell.

Open examples Content modeling examples See how reusable content shapes pages before workflow is added. Continue Review packages Package trust Check how packages declare fields, schema impact, support, compatibility, and upgrade notes. Continue Open operations Site operations Follow what happens after publish: redirects, cache refreshes, Lockdown, imports, audits, and rollback. Continue