- Current primary documentation browsable online or downloadable tarball
- Old documentation for historical reference
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 https://github.com/interchange/xmldocs.git
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 Sagehill.net.
- About Interchange
- Live demo
- Gallery of sites running Interchange
- Downloads & source code
- Community resources (mailing lists etc.)
- Professional support
What Interchange users are saying:
First and foremost, a web application platform really must be a platform — it must play nicely with all the other things that your marketing and logistics and operations and vendor management groups want to bolt onto it. As such, the platform must be flexible, open, pliable, and also somewhat standardized.
Moreover, it needs to perform under screaming loads, as well as hold stable under the day-in-day-out slog of data that come with running a fair-sized web-centric business. Interchange meets all of these requirements.
We built a $100M+ company using Interchange both as a customer-facing web application suite as well as the the back-office web-based logistics platform for our buyers, marketers, and warehouse operations.
The Open Source outlook of Interchange, along with its Perl architecture, brings the needed flexibility and continuity throughout the app. A competent and experienced developer can take Interchange and make it sing.Dave Jenkins, CTO at Backcountry.com