modx workflow for professionals

Hi All

We’ve been using modx for a year or so now - we have a mixture of sites running on Evo and Revo, and we’re getting to the stage where we feel like we’re getting pretty competent now. We’ve build one large e-commerce site using Evo which in particular we’re very happy with, and so is the customer.

However, the thing that is worrying me is how do other professional developers out there handle their workflow when using modx?

The main worries here are the ability to code using my IDE of choice, having some sort of version control system (we use SVN but I’m more worried about have *a* version control than getting religious over a particular flavour), and handling releases of the codebase from test to stage to live without impacting on the live site.

I can find no proper answer to this anywhere. I find a lot of clues, but no real answer.

So how do you guys manage it? How do you handle running a proper site in a professional way using modx with multiple developers?

Cheers,

A.

I know some people develop locally, and then move it to the new server.

I’m also working on a versioning addon for MODX which will (initially) track resource content, and some elements (chunks and snippets were planned) at a later stage too. It wouldn’t be too hard to expand that to also include templates, plugins or anything.

Andy
We are going through this right now in my office. We use a separate server (stage.---.com) before going live, and we use SVN. We don’t have a fully developed plan yet so I’m interested in this, as well. The add-on is an interesting idea and I will have my programmer look at it. Hopefully, we can all come up with a good plan that we can develop over time.

You can already fetch alpha3 from the addon through the package manager. It’s called "VersionX". Will be working on beta over the coming weeks, but paying projects are delaying development for it.