Skip to main content.

Interchange documentation

Existing users should refer to the UPGRADE document for information on incompatible changes and upgrade instructions. For an exhaustive list of changes, see the WHATSNEW document from the previous development series.

For upgrades from legacy code (from MiniVend to Interchange 5.0), see the Upgrading document in our documentation set.

Building documentation from source

You can browse the documentation source repository using our GitHub repository. To build the documentation yourself, you need to clone your own local copy, as follows:

git clone

You should then read the README file for build instructions and a list of prerequisites.

Helping with the documentation

There are many ways you can help with the documentation.

You can fork our xmldocs project on GitHub and publish changes in your own fork. For an introduction to our build system and ways to write documentation, see README and WRITING. To get more deeply involved in DocBook XML, see DocBook and

Site Areas

What Interchange users are saying:

When we first got into the web application business, we made an exhaustive look at the available technologies (at the time). It was apparent Interchange had the highest learning curve, but also one of the few with the ability to do just about anything you’d ask of it.

Since our applications can take any form, we needed something extremely flexible, and something that if asked, could handle ecommerce, email, CRM, CMS, and anything else that comes our way. Interchange has never once disappointed.

We’ve always considered ourselves lucky in making that decision some 7 years ago.

Paul Jordan, Gish Network

See other endorsements of Interchange.