Ajaxify for Evolution CMS: HTML5 History API and Smarter Block Reloads
A look at an Evolution plugin that turned the site into a single-page-like experience by reloading only the blocks that actually changed.
Laravel, AI, MCP, APIs, integrations, and external tooling that matters in modern Evolution CMS work.
A look at an Evolution plugin that turned the site into a single-page-like experience by reloading only the blocks that actually changed.
What was possible when developers wanted to extend the resource edit form through code instead of relying only on TVs.
Why this RC mattered: many bundled extras moved into the repository, the Store module became central, and the build pushed further toward a cleaner install base.
A short recap of Revolution 2.2.9 and why it mattered as the final planned release in the 2.2 branch before 2.3.
What changed in the 0.1.1 update of the early Evolution repository and why those changes mattered for package distribution and store reliability.
A look at XForum as an Evolution-native forum concept, where categories, forums, and subforums are modeled directly as CMS resources.
How to think about mass-generating subdirectories with their own context, permissions, and starter structure instead of cloning sites by hand.
What teams hoped to gain from letting the CMS write data into Memcache while Nginx served cached content directly from it.
A practical comparison of the two approaches teams considered most often when planning product options, comparison features, and 1C integration.
A plugin pattern for forcing child documents to inherit a specific template without asking editors to choose it manually every time.
Why storing cart sessions in the database can improve reliability and let visitors return to partially filled carts later.
An early ecosystem discussion about what the Evolution package repository should include first and how priorities shape a healthy extras surface.
A reflection on which manager functions felt unnecessary or overly heavy, and why backend simplification was an important part of long-term Evolution CMS usability.
A cleaner approach to site-specific system variables that avoids writing one-off plugins for every small editable setting.
Why the first dedicated Evolution repository mattered and how it changed the way extras, updates, and package discovery could work.
A release recap of the 1.0.10-d5.4 build and why its SeoStrict fixes, KCFinder refresh, and core cleanup mattered to active projects.
A quick checklist for Mapex v2 installs that succeed as a package but still fail to render inside the manager or TV field.
A preview of the 1.0.10-d5.4RC build, including DBAPI migration work, editor improvements, and the push toward a more modern legacy core.
An early look at bidCAT as a lightweight catalog concept focused on speed, simpler editing, and lower resource demands.
A small utility for creating a local backup, uploading it to cloud storage, and optionally removing the server copy afterward.