Page not found
Uh oh, you've reached a page that does not exist.
It may have gotten lost on the new documentation platform or it was removed because it was no longer relevant. It could also be a really old link from two (or more) documentation systems ago, which is not part of the 2000+ automatic redirects currently in place.
Based on your request, this may be what you're looking for:
-
Contributor's Guide
Development for MODX happens on GitHub. Everyone is invited to improve MODX, and in this guide we explain some of the common processes. Branches¶ Development is focused on 2 branches. 2.x, which contains the latest version of the 2.x series (e.g. 2.7...
-
Git Installation
Installation Process¶ Here are some notes on participating in MODX Revolution testing and/or development. Unlike previous versions of MODX, Revolution will not install directly from Git. Because of the nature of the new packaging and installation sys...
-
Using Git and GitHub
Git is the distributed version control system used by MODX for source code collaboration and version control. Like MODX, it's free and open source. Git's official website is an excellent place to get started if you're new to Git or to version contr...
-
Git basics and the first commit of a component on Github
We finish with preparation for the beginning of active development. Today we need to upload the stub to the server, rename it, create a repository on GitHub and send the first commit to it. And for this you will need to configure PhpStorm to work wit...
-
Setting up Gitify
Gitify brings two-way sync of data typically stored in the MODX database, making it versionable with git. It acts as a CLI tool, like Composer, for working with MODX. While this document may seem intimdating at first, it really is a simple copy/paste...