Blog Sections Open
DLSiteContent: A Model-Oriented Content Layer for Evolution CMS
A small but meaningful ecosystem post about DLSiteContent and why it became part of the model-oriented story around modern Evolution CMS development.
Packages like DLSiteContent matter because they mark the point where an ecosystem starts thinking in more structured data and model terms instead of only in template snippets. Around Evolution CMS 2.0 and 3.0, that shift was especially important because many teams wanted a cleaner way to work with site content as data.
Keeping this package visible in the archive helps show that Evo was not only accumulating frontend helpers. It was also building a stronger programming surface for developers who wanted richer document interaction and cleaner abstractions.
Why this is worth keeping in the timeline
- it reflects the move toward model-oriented Evo development
- it sits close to the broader Evo 2.0 and Evo 3 architecture story
- it helps explain why later controller and Eloquent-style patterns felt natural
Source: Telegram post and DLSiteContent on GitHub.
Dynamic Filter Configuration in mFilter2 for Auto-Synced Product Options
How to think about dynamic filter generation in mFilter2 when product options are created automatically from external syncs.
evocms-minifier: Early Asset Minification for Evolution CMS 2.0
An ecosystem post about evocms-minifier, one of the early asset-optimization packages built around Evolution CMS 2.0.