Blog Sections Open
managerNav: Faster Document Navigation Inside the Evolution CMS Manager
managerNav was built to reduce manager friction by letting editors move through nearby documents without constantly returning to the tree.
One of the most practical manager-side ideas from the old Evolution ecosystem was simple: editors should be able to move between nearby documents without returning to the tree every time.
What managerNav Added
The managerNav plugin introduced document-to-document navigation directly in the manager edit flow. That made repetitive editing much faster for content-heavy projects.
Why It Was Useful
- fewer clicks back to the resource tree
- faster review of a sequence of documents
- better workflow for managers updating ordered content
Implementation Notes
The original release mentioned configurable source fields, with menuindex being the natural default for ordered navigation. It also referenced a cyclic navigation option so editors could loop through a set instead of stopping at the edge.
Changelog Notes from the Time
The 1.1 update specifically improved save behavior so the navigation state stayed reliable after OnDocFormSave.
Why This Still Matters
Even today, manager productivity improvements are often more valuable than flashy frontend features. managerNav is a good example of an ecosystem tool that solved a very real editorial pain point with a focused scope.
Source: Evolution CMS on GitHub.
Updating Evolution Through the Extras-Evolution Repository
An old ecosystem note about updating Evolution from the Extras-Evolution repository and why teams still needed to treat repository-based upgrades carefully.
Using MultiTV as a Practical Alternative to mm_ddMultipleFields
Why MultiTV became the practical answer when teams needed repeatable grouped fields, including rich text, instead of older ManagerManager-style helpers.