I’m very excited to introduce RAMP to the WordPress community. RAMP is a new commercial product for WordPress that makes it easy to set up your content in your staging environment, then push those changes to your live site.
At Crowd Favorite we are fortunate to have some really great clients. These clients are running some pretty big web properties on WordPress, and they need to stage their content, review it internally, revise it, etc. before they put it live. It’s a pretty universal need – we just did it on our own site as we were preparing the web page and documentation for RAMP on our own site. This has always been difficult with WordPress, and had often resulted in SQL export/import followed by update scripts and/or manual copy-paste steps. RAMP solves this problem elegantly. You simply:
- Install the RAMP plugin on your staging and production servers, and enter the auth key and URL from production in the settings for your staging server.
- Select the changes you’d like to send and save them as a batch.
- RAMP the batch up to your production server.
RAMP doesn’t just support posts and pages either; it fully supports custom post types, categories, tags, custom taxonomies, users, menus, links and more.
We’re really proud of the underlying architecture of RAMP. We spent a long time working out just the right way to implement this type of functionality for WordPress, and I’m really pleased with the solution. We utilize core WordPress functionality and APIs, the XMLRPC layer for transport between servers, and built everything on top of an wonderfully extensible system (which uses the core WordPress hook and filter system) to allow any WordPress content to participate in a RAMP batch. We’ve already done this to Carrington Build.
This post is part of the project: RAMP. View the project timeline for more context on this post.