Blog Sections Open
A Practical Cheat Sheet for Teams Moving from Other CMSs to Evolution CMS
A short orientation guide for teams coming from WordPress, MODX Revolution, or other CMS platforms and trying to understand which Evolution CMS tools map to familiar tasks.
When teams move to Evolution CMS from another platform, the first problem is rarely code. The real problem is vocabulary. People know what they want to build, but they do not yet know which Evolution tools solve the job.
The shortest useful map
- DocLister is the main listing engine. Use it for document lists, custom table output, menus, and many kinds of catalog views.
- FormLister handles forms, validation, hooks, and multi-step form logic.
- Chunks are reusable view fragments.
- Snippets execute logic and produce output.
- TVs add structured per-resource fields.
If you come from MODX Revolution
- DocLister often plays the role people expect from pdoTools-based output
- Chunks still separate markup from logic
- TVs remain the usual way to add extra content fields
If you come from WordPress
- resources are your pages and content nodes
- templates define the page structure
- TVs often replace custom fields plugins
- DocLister + chunks cover a lot of the “loop plus template” work
A few component combinations worth learning early
- DocLister + DLMenu for navigation
- DocLister + DLCrumbs for breadcrumbs
- FormLister for forms and registration flows
- simpleGallery / simpleFiles / simpleTube for attached media where available in your project stack
The mindset shift
Evolution CMS is easiest to work with when you stop searching for one giant plugin that does everything. The usual pattern is smaller building blocks combined clearly:
- tree resources for structure
- TVs for extra data
- chunks for markup
- snippets for logic
- DocLister or FormLister for the heavy lifting
Once the team sees those building blocks, the rest of the system becomes much easier to reason about.
Adding Lazy-Loading Image Classes to TinyMCE in Evolution CMS
A small TinyMCE customization that adds a lazy-loading class option directly to the image dialog in Evolution CMS.
Adapting DocLister Display Count to Viewport Changes
How to handle catalog layouts where a fixed DocLister display count leaves the last row visually broken on different screen widths.