A slug looks like a presentation detail until other systems start depending on it. Once a page is published, that identity appears in bookmarks, search metadata, links and editorial records. Moving just one field can split those systems into contradictory states.
The AbhisecWorks implementation gives the move to the backend. It checks the entity and destination, writes the new identity and metadata together, and updates redirects. The normal CMS editor refuses a direct identity edit while the content is published.
A practical checklist
- Make route ownership explicit.
- Keep identity and metadata changes atomic.
- Flatten old paths to the current destination.
- Exclude stale or unpublished mappings from public discovery.
A database transaction establishes consistency for the local write. Public caches still need invalidation or a documented expiry window. A redirect check before rendering handles old paths even while content caches refresh.