Blog Sections Open
Thinking Beyond DocLister: Eloquent Patterns in Evolution CMS 3
A practical architecture note on why Evo 3 opened the door to Eloquent-style workflows instead of relying only on older listing paradigms.
One of the real shifts in Evolution CMS 3 was not just a new core version number. It was the fact that developers could think in terms closer to modern Laravel applications, including model-driven querying and richer domain logic. That is why the old question, “do we always need DocLister for this?” started becoming more interesting.
This does not make DocLister obsolete. It is still effective for many frontend listings. But the Evo 3 direction made it reasonable to ask where Eloquent-style models are a better fit: custom business rules, application-like backend logic, richer data relationships, and workflows where code readability matters more than snippet-driven assembly.
When the Eloquent direction makes sense
- custom business logic that goes beyond plain listings
- projects with richer model relationships and reusable query scopes
- teams that want their Evo codebase to look more like a Laravel app
Source: Telegram post and the original gist notes.
Stripe for Commerce: Another Payment Option Around Evolution CMS
An ecosystem post about a Stripe payment integration for Commerce-based Evolution CMS projects.
Console-Based Package Installation in Evolution CMS 3.0
An ecosystem post about installing Evolution CMS add-ons through the console with dependency awareness in the Evo 3 era.