Blog Sections Open
Using Git in an Evolution CMS Workflow
A simple console-first workflow for creating and linking Evolution CMS elements from files so Git becomes part of day-to-day development.
A few days after the original filesystem-sync experiment, its author published a second, more practical iteration. Instead of focusing on a Node.js sync module, this version moved to a smaller PHP helper designed for everyday work from the console.
The result was closer to what many Evolution developers actually wanted: a lightweight helper that behaved a bit like Artisan and made file-based element work less painful.
Why a Second Tool Was Needed
The earlier experiment with a Node.js module worked, but the author considered it awkward in day-to-day use. The replacement idea was more direct: a tiny PHP helper that could create chunks, snippets, and templates from the command line and link them to files immediately.
The Core Benefit
The helper solved a practical workflow problem:
- create an element
- create its file
- link the file to the database record
- keep the real editable source in the filesystem
If an element already existed only in the database, the same tool could move it into the filesystem so it became part of the project source tree.
The Console Experience
D:\www\projectfolder>php modxhelper.php
Hi, i'm ModHelper. Input command
--> help
Available commands:
chunk - create chunk
snippet - create snippet
template - create template
That's all you need to start. let's go!The article made the point clearly: if you have used Artisan or another command-line helper before, this kind of workflow feels natural almost immediately.
Why This Helped Git Adoption
The manager is fine for quick edits, but Git works best when project code lives in files. A console helper like this reduces the friction of that change. Instead of manually creating an element in the manager and then linking a file, a developer can start from the command line and keep the filesystem as the source of truth.
What Still Matters Today
Even though the exact helper belongs to an earlier moment in the ecosystem, the lesson is still current:
- prefer file-backed elements for code review and team work
- make project structure predictable
- lower the friction of repeatable development tasks
- treat CMS elements as project source, not only as database content
That workflow thinking fits perfectly with current Evolution package work as well.
Source project: modxHelper on GitHub.
Investigating Hidden Casino Spam Pages on an Evolution CMS Site
How to approach hidden spam page incidents on an Evolution CMS site when the generated pages are not visible in the manager or normal project files.
Editing Snippets, Chunks, and Templates in an IDE with Git
A practical look at moving Evolution CMS elements out of the manager and into files so they can be edited in an IDE and tracked with Git.