Skip to main content

Laravel CMS Operations

Operations console

Site operations, not just content editing.

This page helps maintainers understand what happens after content is edited, packages change, or public output needs repair.

Capell should show maintainers what changed, what needs attention, and how public output is affected. Example: editing a page can refresh cached HTML, update sitemap output, queue search indexing, and require redirect checks when the URL changes.

Console

Health checks and recent jobs

A maintainer can scan cache, queue, package, and publish state before touching production.

Cache
Fresh
Jobs
Clear
Packages
2 alerts
Status

One-line operational state

The site should surface whether publishing, cache, search, imports, and packages are healthy.

Publish OK Cache warm Search queued
Redirects

URL changes keep a trail

Aliases and redirects stay connected to content changes instead of living in a forgotten config file. 

/old-guide -> /learn/content/layout-builder
Rollback

Recovery notes near the change

Launch notes, import sessions, and previous versions should be available before a fix is urgent.

  • Import created 14 pages
  • Preview approved
  • Cache refreshed
Lockdown

Incident control is deliberately narrow

Close public output, preserve cache, and keep trusted admin access available during an incident.

Publish Know what public URLs changed. Publishing should explain affected URLs, cache refreshes, and follow-up checks.
Operational detail : Know what public URLs changed.

A useful publish note says what changed, which URLs were affected, which cache entries refreshed, whether search or sitemap output needs work, and how to reverse the change.

Workflow
Upgrade Package changes should be reviewable. Version, migration, support, advisory, and rollback context should be available before update.
Install impact : Package changes should be reviewable.

A package upgrade can change admin fields, add migrations, touch frontend output, or alter commands. Those changes should be visible before a maintainer runs them in production.

Upgrades
Recover Incidents need obvious controls. Lockdown and recovery notes should be findable before the site needs them.
Operational detail : Incidents need obvious controls.

Recovery content should name the control, the expected public response, the admin access path, and the cache or rollback notes a maintainer needs under pressure.

Incident control
Next steps

Next steps for site operations.

Publishing Previous concept Review the publishing workflow that creates most operational follow-up work. Continue Upgrades Practical next step Check package upgrade visibility before a production release. Continue Lockdown Related reference Read Lockdown before an incident makes the controls urgent. Continue